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.

Versions published
8
First published
May 2026
Publisher
tuantitan

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":["[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"}'
Publishertuantitan
Artifact bytes236,843
Previous version0.4.0
Published2026-05-29T01:27:53.113Z
SHA-256cac4e410c3f8a885769ddfa0b7715e6cb9e6d7677c5102e3bb9fd8c2e8933365

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

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts42
  • 9pp:generatenode scripts/specs-to-9pp-utc.mjs
  • a11y:reportnode scripts/a11y-report.mjs
  • a11y:scenariosnode scripts/scenarios-from-a11y.mjs
  • batch:parsenode scripts/parse-test-scenarios.mjs
  • batch:reportnode scripts/batch-report.mjs
  • batch:runnode scripts/run-playwright-batch.mjs
  • coverage:matrixnode scripts/coverage-matrix.mjs
  • crud:extract-apinode scripts/extract-api-methods.mjs
  • crud:extract-api:zendnode scripts/extract-api-methods-zend.mjs
  • crud:extract-sqlnode scripts/extract-crud-sql.mjs
  • crud:extract-sql:zendnode scripts/extract-crud-sql-zend.mjs
  • crud:generatenode scripts/generate-c2-c10.mjs
  • crud:pairnode scripts/pair-crud.mjs
  • db:introspectnode scripts/db-schema-introspect.mjs
  • deliverablesnode scripts/specs-to-markdown.mjs --specs tests --out deliverables
  • filter:extractnode scripts/extract-filter-signals.mjs
  • filter:generatenode scripts/generate-filter-specs.mjs
  • generatenpm run locators:refresh && npm run deliverables
  • generate:forcenpm run locators:force && npm run deliverables
  • i18n:scenariosnode scripts/scenarios-from-i18n.mjs
  • jp:generatenode scripts/specs-to-japanese.mjs
  • locators:forcenode scripts/refresh-locators.mjs --force
  • locators:refreshnode scripts/refresh-locators.mjs
  • migratenode scripts/migrate.mjs
  • migrate:coveragespeclab migrate coverage migrate.config.json
  • migrate:gap-hintspeclab migrate gap-hint migrate.config.json
  • perf:scenariosnode scripts/scenarios-from-perf.mjs
  • rbac:api-scenariosnode scripts/scenarios-from-rbac-api.mjs
  • rbac:matrixnode scripts/rbac-matrix.mjs
  • rbac:probenode scripts/probe-rbac.mjs
  • …and 12 more.
Dependencies1
  • @ast-grep/napi^0.42.2