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
- 2,307Niche · −30% score
- Versions published
- 33
- First published
- May 2026
- Publisher
- ironclawdevs27
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":["[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 "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 21 · 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/utils/github-reporter.js | matched "GITHUB_TOKEN" | 30 |
Manifest
Package metadata
Scripts17
chromenode src/cli/chrome-launcher.jscomparenode src/orchestration/env-comparison.jscrawlnode src/orchestration/crawl-and-report.jsdoctornode src/cli/doctor.jsharnessnode test-harness/server.jsharness:stagingnode test-harness/server.js --port=3101 --staginginitnode src/cli/init.jsmcp-servernode src/mcp-server.jsreport:htmlnode src/utils/html-reporter.jsreport:pdfnode src/utils/pdf-exporter.jsservernode src/server/index.jssetupnode -e "import('fs').then(fs => fs.default.mkdirSync('./reports', { recursive: true }))"testnpm run test:unit && npm run test:harnesstest:harnessnode --env-file=test-harness/.env.harness test-harness/validate.jstest:harness:lognode test-harness/run-with-log.mjstest:unitvitest run test/unitwatchnode src/orchestration/watch-mode.js
Dependencies12
@modelcontextprotocol/sdk^1.29.0@opentelemetry/api^1.9.1@opentelemetry/sdk-node^0.218.0@slack/web-api^7.16.0axe-core^4.12.0dotenv^17.4.2express^5.2.1pino^10.3.1pino-pretty^13.1.3pixelmatch^7.2.0pngjs^7.0.0zod^4.4.3