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
- 758
- Versions published
- 58
- First published
- Mar 2026
- Publisher
- stevenvo780
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":["@stevenvo780/[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":["@stevenvo780/[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
Scripts22
benchvitest bench --run --config vitest.bench.config.tsbench:comparenode scripts/bench/compare.mjsbench:savevitest bench --run --config vitest.bench.config.ts && cp benchmarks/results.json benchmarks/baselines.jsonbench:v5vitest bench --run --config vitest.bench.v5.config.tsbench:v5:regressionnode scripts/bench/v5-regression.mjsbench:v5:updatenode scripts/bench/v5-regression.mjs --updatebuildtsc && chmod +x dist/cli/index.jscleanrm -rf distdevtsc --watchexamples:runbash ./scripts/run-all-examples.shformatprettier --write "src/**/*.ts"linteslint src --ext .tspackage./scripts/package.shprepacknpm run buildprepublishOnlynpm run clean && npm run build && npm run teststartnode dist/cli/index.jstestvitest runtest:allbash ./scripts/run-exhaustive-validation.shtest:coveragevitest run --coveragetest:stressvitest run src/tests/stress-hardware.test.tstest:watchvitesttypechecktsc --noEmit
Dependencies4
@stevenvo780/st-lang^4.6.0chalk^5.6.2commander^14.0.3z3-solver^4.16.0