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
- 169
- First published
- Apr 2026
- Publisher
- cainen
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
Scripts2
buildtsc && node scripts/compile-libs.mjscleanrm -rf dist
Dependencies20
@ai-sdk/anthropic^3.0.71@ai-sdk/openai-compatible^2.0.41@ai-sdk/provider^3.0.8@specverse/assets^1.25.0@specverse/entities^5.7.0@specverse/runtime^5.11.1@specverse/types^5.3.1ai^6.0.168ajv^8.17.0ajv-formats^2.1.0esbuild^0.25.0glob^10.0.0graphology^0.26.0graphology-communities-louvain^2.0.2handlebars^4.7.9js-yaml^4.1.0semver^7.0.0typescript^5.4.0yaml^2.8.1zod^4.3.6