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.
- Weekly downloads
- 877
- Versions published
- 19
- First published
- Jan 2026
- Publisher
- waron97
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":["@waron97/[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":["@waron97/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Credential file access: matched ".azure"
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/src/commands/autopr.js | matched ".azure" | 30 |
Manifest
Package metadata
Scripts1
testecho "Error: no test specified" && exit 1
Dependencies11
@inquirer/search^2.0.1commander^14.0.2dotenv^17.2.3eslint-plugin-es5^1.5.0inquirer^13.4.2inquirer-search-list^1.2.6node-fetch^3.3.2omelette^0.4.17prettier^3.5.3slugify^1.6.9yaml^2.9.0