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
- 1
- First published
- May 2026
- Publisher
- gepheum
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":["[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":["[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
buildtscformatprettier --write "**/*.ts" && npm run format-skirformat-skircd e2e-tests && ../node_modules/.bin/skir format && cd ..format-skir:checkcd e2e-tests && ../node_modules/.bin/skir format --ci && cd ..format:checkprettier --check "**/*.ts" && npm run format-skir:checklinteslint src/**/*.tslint:fixeslint src/**/*.ts --fixtestnpm run build && cd e2e-tests && rm -rf skirout && ../node_modules/.bin/skir gen && for p in $(find skirout -name moon.pkg -exec dirname {} +); do moon check ./$p || exit 1; done && moon test ./goldens-tests && cd ..
Dependencies2
skir-internal^0.2.19zod^4.2.1