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
- 34
- First published
- Mar 2026
- Publisher
- nervmor
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":["@nervmor/[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":["@nervmor/[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
Scripts10
appserver:schema:checknode scripts/sync-app-server-schemas.mjsappserver:schema:updatenode scripts/sync-app-server-schemas.mjs --writebuildnpm run build:frontend && npm run build:clibuild:clitsupbuild:frontendvue-tsc --noEmit && vite builddevvitedev:opennpm run build:cli && sh -c 'npm run dev & VPID=$!; node dist-cli/index.js --open-project "${1:-.}"; wait $VPID' --prepublishOnlynpm run buildpreviewvite previewtestvitest run
Dependencies7
commander^13.1.0cron-parser^5.5.0express^5.1.0firebase^12.2.1highlight.js^11.11.1qrcode-terminal^0.12.0ws^8.18.3