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.
- Versions published
- 7
- First published
- Apr 2026
- Publisher
- classytic-bot
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":["@classytic/[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":["@classytic/[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
Scripts17
buildtsdowncheckbiome check --write --unsafe src/ tests/devtsdown --watchformatbiome format --write src/ tests/lintbiome check src/ tests/lint:fixbiome check --write src/ tests/prepublishOnlynpm run lint && npm run typecheck && npm run test:unit && npm run buildpushclassytic-pushreleasenpm run push -- main && npm run release:tag && npm publishrelease:tagnode -e "require('child_process').execSync('npm run push -- v'+require('./package.json').version,{stdio:'inherit'})"testvitest run --project unit --project integrationtest:allvitest runtest:coveragevitest run --coveragetest:integrationvitest run --project integrationtest:unitvitest run --project unittest:watchvitest --project unit --project integrationtypechecktsc --noEmit