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
- 1,017Niche · −30% score
- Versions published
- 96
- First published
- Apr 2026
- Publisher
- cainen
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 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":["@specverse/[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":["@specverse/[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
Scripts12
buildnpm run validate && npm run realizecleanrm -rf generated/code specs/inferred.speclydev:backendnpm --prefix generated/code run dev:backenddev:frontendnpm --prefix generated/code run dev:frontendgen:diagramsspecverse gen diagram specs/main.specly -o docs/diagrams/gen:docsspecverse gen docs specs/main.specly -o docs/inferspecverse infer specs/main.specly -o specs/inferred.specly --verboserealizespecverse realize all specs/main.specly -m manifests/implementation.yaml -o generated/codesetupnpm install && npx playwright install chromium && npm run build && npm --prefix generated/code install && npm --prefix generated/code run db:generate && npm --prefix generated/code run db:pushstartnpm --prefix generated/code starttest:e2eplaywright test --config=playwright.config.tsvalidatespecverse validate specs/main.specly