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
- 1
- First published
- Jun 2026
- Publisher
- nastechai
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":["@nastechai/[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":["@nastechai/[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
Scripts1
buildesbuild src/entry-exports.ts --bundle --platform=node --format=esm --packages=external --outdir=dist
Dependencies20
@alcalzone/ansi-tokenize^0.1.0auto-bind^5.0.0bidi-js^1.0.0chalk^5.4.0cli-boxes^3.0.0code-excerpt^4.0.0emoji-regex^10.4.0get-east-asian-width^1.3.0indent-string^5.0.0lodash-es^4.17.0react>=19.0.0react-reconciler0.33.0semver^7.6.0signal-exit^4.1.0stack-utils^2.0.0strip-ansi^7.1.0supports-hyperlinks^3.1.0type-fest^4.30.0usehooks-ts^3.1.0wrap-ansi^9.0.0