PkgRadar

Package evidence

@mpen/[email protected]

no findings

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
10
First published
May 2026
Publisher
mnpenner

Recommended action

Looks clean — keep monitoring

No 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":["@mpen/[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":["@mpen/[email protected]"],"fail_on":"review"}'
Publishermnpenner
Artifact bytes6,152
Previous version0.1.17
Published2026-06-17T05:15:20.507Z
SHA-256e3cd15e8222975a98cbcb43a56db9571bd017d9eeaf051d8e5211cd521fc547b

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

low
Last checked
lowRisk
0Score
0.1.18Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts4
  • buildtsdown
  • devbun run --hot src/dev.ts
  • patchnpm version patch && VER=$(jq -r '.version' package.json) && hg ci -m "Publish v$VER" && hg tag "v$VER"
  • releasebun run build && bun run patch && npm publish && hg push
Dependencies1
  • jtilz0.5.0