PkgRadar

Package evidence

@classytic/[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
83
Versions published
26Established · −30% score
First published
Nov 2025
Publisher
classytic-bot

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.

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"}'
Publisherclassytic-bot
Artifact bytes93,614
Previous version2.3.0
Published2026-06-13T23:25:41.371Z
SHA-2563dc2ea16d6ffbfb255d8f21f16fb6d3b60db3cc1d4e349bf59a74a653756eb5e

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
2.4.0Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts8
  • buildtsdown
  • devtsdown --watch
  • prepublishOnlytsdown
  • releasenpm run release:push && npm run release:tag && npm publish
  • release:pushnode -e "require('child_process').execSync('npm run push -- main',{cwd:require('node:path').resolve('..'),stdio:'inherit'})"
  • release:tagnode -e "const v=require('./package.json').version,p=require('node:path').resolve('..'),{execSync:e}=require('child_process'),r=c=>e(c,{cwd:p,stdio:'inherit'});r('git tag -a revenue-v'+v+' -m revenue-v'+v);r('npm run push -- revenue-v'+v)"
  • testcd .. && vitest run
  • typechecktsc --noEmit