PkgRadar

Package evidence

[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.

Weekly downloads
289
Versions published
10Established · −30% score
First published
Jun 2022
Publisher
stevelemon

Effective trust discount applied: 30% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

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":["[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"}'
Publisherstevelemon
Artifact bytes10,119
Previous version1.1.0
Published2025-12-26T05:21:46.572Z
SHA-256981cb3daa879395e73018b082d05fc0c429d63de1a0c3e423ecfbc215df92e3a

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
1.1.1Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts14
  • !publish------- publish into repository -----
  • !test------- run self-test with jest -----
  • buildnpm run build-ts
  • build-tstsc -v && tsc
  • docnpm run doc:html && open dist/docs/index.html
  • doc:htmltypedoc src/ --exclude **/*.spec.ts --target ES6 --mode file --out dist/docs
  • doc:publishnpm run doc:html && gh-pages -m "docs(gh-pages): publish gh-pages via typedoc" -d dist/docs
  • formatprettier --write "src/**/*.ts"
  • linttsc --noEmit && eslint '*/**/*.{js,ts,jsx,tsx}' --fix
  • preparenpm run build
  • prepublishOnlynpm test && npm run lint && npm run format
  • testjest --config=jest.config.json
  • test:watchjest --config=jest.config.json --watchAll
  • watch-tstsc -w