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
- cblokland
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":["@codemation/[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":["@codemation/[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 (2 events)
- available → available · risk low · score 0 · status available -> available, risk high -> low, score 50 -> 0
- new → available · risk high · score 50 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts8
buildtsdown && pnpm build:metadatabuild:metadatatsx ../../tooling/discovery/scripts/extract-metadata.tschangeset:verifypnpm --workspace-root run changeset:verifydevtsdown --watchlinteslint .testpnpm --filter @codemation/core build && pnpm build && vitest runtest:unitvitest runtypechecktsc -p tsconfig.json --noEmit
Dependencies6
@ai-sdk/openai^3.0.53@ai-sdk/provider^3.0.8@codemation/core0.11.0ai^6.0.168croner^10.0.1lucide-react^0.577.0