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
- 14
- First published
- Apr 2026
- Publisher
- oscarcorona
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":["@hex-core/[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":["@hex-core/[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
Scripts10
buildtsup && pnpm build:readmebuild:readmenode scripts/build-readme.mjscleanrm -rf dist registrydevtsx src/index.tsprebuildrm -rf dist registry && cp -R ../../registry ./registrystartnode dist/index.jstestpnpm test:resolver && pnpm test:app-context && pnpm test:contracttest:app-contexttsx src/tools/app-context.test.tstest:contractnode dist/contract-test.jstest:resolvertsx src/tools/resolver.test.ts
Dependencies3
@hex-core/registry^0.2.1@modelcontextprotocol/sdk^1.12.0zod^4.3.6