PkgRadar

Package evidence

@specverse/[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.

Weekly downloads
1,017Niche · −30% score
Versions published
99
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 monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd to CI gate
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"}'
Publishercainen
Artifact bytes218,261
Previous version5.21.9
Published2026-06-07T10:39:39.039Z
SHA-256e65a4ba69252cec703aa30865fdc3177b2495479c821a33315f9bda2b87d0c19

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
5.21.10Version
Status history (1 event)
  1. 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 realize
  • cleanrm -rf generated/code specs/inferred.specly
  • dev:backendnpm --prefix generated/code run dev:backend
  • dev:frontendnpm --prefix generated/code run dev:frontend
  • gen: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 --verbose
  • realizespecverse realize all specs/main.specly -m manifests/implementation.yaml -o generated/code
  • setupnpm 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:push
  • startnpm --prefix generated/code start
  • test:e2eplaywright test --config=playwright.config.ts
  • validatespecverse validate specs/main.specly