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
- 6
- First published
- May 2026
- Publisher
- temaus91
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
Scripts9
buildtscfirsttracetsx src/cli.tsoci:sync-secretstsx src/oci/sync-secrets.tsprepacknpm run buildstart:httpnode dist/src/runtime/http-server.jsstart:workernode dist/src/runtime/worker-loop.jstestvitest runtypechecktsc --noEmitvercel-buildnpm run typecheck
Dependencies14
@octokit/auth-app^8.2.0@supabase/supabase-js^2.106.1@vercel/functions^3.6.0dotenv^17.4.2oci-common^2.132.0oci-generativeaiinference^2.132.0oci-objectstorage^2.132.0oci-queue^2.132.0oci-secrets^2.132.0oci-vault^2.132.0openai^6.39.0tar^7.5.15yaml^2.8.1zod^4.4.3