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
- 44
- First published
- Jan 2026
- Publisher
- chicagodave
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":["@sharpee/[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":["@sharpee/[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
Dependencies20
@sharpee/channel-service^1.0.0@sharpee/character^1.0.0@sharpee/core^1.0.0@sharpee/engine^1.0.0@sharpee/event-processor^1.0.0@sharpee/ext-testing^1.0.0@sharpee/if-domain^1.0.0@sharpee/if-services^1.0.0@sharpee/lang-en-us^1.0.0@sharpee/media^1.0.0@sharpee/parser-en-us^1.0.0@sharpee/platform-browser^1.0.0@sharpee/plugin-npc^1.0.0@sharpee/plugin-scheduler^1.0.0@sharpee/plugin-state-machine^1.0.0@sharpee/plugins^1.0.0@sharpee/stdlib^1.0.0@sharpee/story-runtime-baseline^1.0.0@sharpee/text-blocks^1.0.0@sharpee/world-model^1.0.0