PkgRadar

Package evidence

[email protected]

no findings

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
1,411Niche · −30% score
Versions published
21
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

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
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"}'
Publisherironclawdevs27
Artifact bytes149,456
Previous version9.5.0
Published2026-05-31T11:36:39.276Z
SHA-256efd73c66f8db624b07826f837f80772ed3434ea50bdaecf4cca2a45bedd839c9

Why flagged

What the scanner saw

No high-signal static finding in the saved report.

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

low
Last checked
lowRisk
0Score
9.5.1Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts13
  • comparenode src/orchestration/env-comparison.js
  • crawlnode src/orchestration/crawl-and-report.js
  • harnessnode test-harness/server.js
  • harness:stagingPORT=3101 node test-harness/server.js
  • initnode src/cli/init.js
  • mcp-servernode src/mcp-server.js
  • report:htmlnode src/utils/html-reporter.js
  • servernode src/server/index.js
  • setupnode -e "import('fs').then(fs => fs.default.mkdirSync('./reports', { recursive: true }))"
  • testnpm run test:unit && npm run test:harness
  • test:harnessnode test-harness/validate.js
  • test:unitvitest run test/unit
  • watchnode src/orchestration/watch-mode.js
Dependencies11
  • @modelcontextprotocol/sdk^1.29.0
  • @opentelemetry/api^1.9.1
  • @opentelemetry/sdk-node^0.218.0
  • @slack/web-api^7.16.0
  • dotenv^16.4.5
  • express^5.2.1
  • pino^10.3.1
  • pino-pretty^13.1.3
  • pixelmatch^7.2.0
  • pngjs^7.0.0
  • zod^4.4.3