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
- 54
- Versions published
- 43Established · −30% score
- First published
- Jun 2025
- Publisher
- shriyanss
Effective trust discount applied: −30% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
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":["@shriyanss/[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":["@shriyanss/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Credential file access: matched "AWS_ACCESS_KEY"
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 10 · status changed
Evidence
Static findings
3 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 3 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/build/api_gateway/index.js | matched "AWS_ACCESS_KEY" | 5 |
| low | Credential file access | package/build/index.js | matched "AWS_ACCESS_KEY" | 5 |
| low | Messenger Bot Endpoint | package/build/strings/secrets.js | matched "hooks.slack.com/services/" — messenger-bot URL without exfil context (likely a notification handler) | 5 |
Manifest
Package metadata
Scripts4
buildrm -rf build/ && tsccleanuprm -rf build output .resp_cache.json endpoints.json extracted_urls{.txt,.json,-openapi.json} strings.json mapped{-openapi.json,.json,-openapi.postman_collection.json} analyze.json test{.yaml,.js} shriyanss-js-recon-*.tgz js-recon.db report.{html,md} js_recon_run_output *_test.js extracted/ research.json results* out.* && tscstartnode --max-old-space-size=8192 build/index.jstestnode build/index.js -h
Dependencies35
@anthropic-ai/sdk^0.102.0@aws-sdk/client-api-gateway^3.958.0@babel/parser^7.27.4@babel/traverse^7.27.4@babel/types^7.27.6@modelcontextprotocol/sdk^1.29.0@types/chalk^0.4.31@types/cli-progress^3.11.6better-sqlite3^12.5.0blessed^0.1.81chalk^5.4.1cheerio^1.0.0cli-highlight^2.1.11cli-progress^3.12.0commander^14.0.0datatables.net^2.3.2datatables.net-dt^2.3.2esquery^1.6.0fs^0.0.2graphql^16.14.1highlight.js^11.11.1inquirer^12.6.3marked^16.1.2md5^2.3.0ollama^0.6.3openai^5.8.2path^0.12.7prettier^3.7.4puppeteer^24.43.1puppeteer-extra^3.3.6- …and 5 more.