Trust signals
Why this verdict
PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.
- Versions published
- 1
- First published
- May 2026
- Publisher
- guorunjie
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
Block this release in CIcurl · GitHub Actions
Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer $PKGRADAR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"specs":["[email protected]"],"fail_on":"review"}'GitHub Actions step:
- name: PkgRadar gate
run: |
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
-H "Content-Type: application/json" \
-d '{"specs":["[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Credential file access: matched "NPM_TOKEN"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk review · score 18 · status changed
Evidence
Static findings
4 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 4 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/src/releasePublish.js | matched "NPM_TOKEN" | 5 |
| low | Credential file access | package/src/releaseStatus.js | matched "NPM_TOKEN" | 5 |
| low | Credential file access | package/src/skillpack.js | matched "NPM_TOKEN" | 5 |
| low | Credential file access | package/skillpack.yaml | matched "NPM_TOKEN" | 3 |
Manifest
Package metadata
Scripts25
agentsnode ./bin/agentic-workflow-guard.js agentsbenchmarknode ./bin/agentic-workflow-guard.js benchmarkbenchmark:corpusnode ./bin/agentic-workflow-guard.js benchmark corpus --format jsonbenchmark:reportnode ./bin/agentic-workflow-guard.js benchmark --format jsondocs:buildnode ./scripts/build-pages.jsdoctornode ./bin/agentic-workflow-guard.js doctor .marketplacenode ./bin/agentic-workflow-guard.js rules --format markdownmcp:resourcesnode ./bin/agentic-workflow-guard.js mcp resources --format jsonrelease:checknode ./bin/agentic-workflow-guard.js release checkrelease:preparenode ./scripts/prepare-release.jsrelease:publishnode ./scripts/publish-release.jsrelease:statusnode ./scripts/release-status.jsrelease:syncnode ./scripts/sync-static.jsrelease:sync:checknode ./scripts/sync-static.js --checkrelease:verifynode ./scripts/verify-release.jsscannode ./bin/agentic-workflow-guard.js scan .scan:strictnode ./bin/agentic-workflow-guard.js scan . --profile strictschema:benchmark-corpusnode ./bin/agentic-workflow-guard.js schema benchmark-corpusschema:benchmark-reportnode ./bin/agentic-workflow-guard.js schema benchmark-reportschema:confignode ./bin/agentic-workflow-guard.js schema configschema:fixnode ./bin/agentic-workflow-guard.js schema fixschema:reportnode ./bin/agentic-workflow-guard.js schema reportschema:rule-packnode ./bin/agentic-workflow-guard.js schema rule-packsmoke:packagenode ./scripts/smoke-package.jstestnode --test