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
- 513
- Versions published
- 55
- First published
- Dec 2025
- Publisher
- altamont
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":["@occam-scaly/[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":["@occam-scaly/[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
Scripts8
buildtscdevtsx src/index.tsprepublishOnlyrm -rf dist && npm run buildstartnode dist/index.jstestvitesttest:runvitest runtypechecktsc --noEmitvendor:app-readinessnode ../../scripts/vendor-app-readiness.mjs
Dependencies8
@modelcontextprotocol/sdk^1.24.1@occam-scaly/app-readinessfile:vendor/occam-scaly-app-readiness-0.1.5.tgz@occam-scaly/scaly-cli^0.2.29graphql^16.8.1graphql-request^6.1.0pg^8.13.1ws^8.18.3zod^3.22.0