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
- 2
- First published
- Jun 2025
- Publisher
- nicknisi
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":["@workos/[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":["@workos/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Credential file access: matched "GITHUB_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 30 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Credential file access | package/dist/prepare.js | matched "GITHUB_TOKEN" | 30 |
Manifest
Package metadata
Scripts8
buildtsup && npm run prepare-contentbuild:devtsup && npm run prepare-content:localdevtsup --watchformatprettier --write .prepare-contentPREPARE=true node dist/prepare.jsprepare-content:localUSE_LOCAL_DOCS=true PREPARE=true node dist/prepare.jsprettierprettier . --checktype-checktsc --noEmit
Dependencies4
@modelcontextprotocol/sdk^0.5.0fast-glob^3.3.2gray-matter^4.0.3rss-parser^3.13.0