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
- 358
- Versions published
- 51
- First published
- May 2026
- Publisher
- armin.burger
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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":["@chimerai/[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":["@chimerai/[email protected]"],"fail_on":"review"}'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
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts6
buildnode -e "const f='package.json',p=JSON.parse(require('fs').readFileSync(f));p.version=p.version.replace(/\d+$/,n=>+n+1);require('fs').writeFileSync(f,JSON.stringify(p,null,2)+'\n');console.log('v'+p.version)" && tscdevtsc --watchlinteslint .testvitest runtest:coveragevitest run --coveragetest:watchvitest
Dependencies7
chalk^5.3.0commander^11.1.0execa^8.0.1fs-extra^11.2.0inquirer^9.2.12jose^6.2.2ora^7.0.1