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.

Versions published
50Mature · −50% score
First published
Feb 2022
Publisher
sealights

Effective trust discount applied: −50% (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.

Inspect tarballAdd to CI gate
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"}'
Publishersealights
Artifact bytes29,122
Previous version3.0.29
Published2026-04-09T14:06:22.773Z
SHA-256d7df61a61ae1a12a6dae2c0ec3c9cebca0e23f11b4d087b7b63d7d595dd7ae54

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
3.0.30Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts12
  • buildtsc -p .
  • prebuildnode -p "'export const version = ' + JSON.stringify(require('./package.json').version) + ';'" > lib/version.ts
  • testnode test/run-all-tests.js
  • test:allexport TEST_RUN=major && npm run test:v29 && npm run test:v28 && npm run test:v27 && npm run test:v26 && npm run test:v25 && npm run test:v24
  • test:unitmocha --require ts-node/register --no-timeouts test/unit/**/*.spec.ts
  • test:v22export JEST_VERSION=22 && mocha --no-timeouts ./tsOutputs/test
  • test:v23export JEST_VERSION=23 && mocha --no-timeouts ./tsOutputs/test
  • test:v24export JEST_VERSION=24 && mocha --no-timeouts ./tsOutputs/test
  • test:v25export JEST_VERSION=25 && mocha --no-timeouts ./tsOutputs/test
  • test:v26export JEST_VERSION=26 && mocha --no-timeouts ./tsOutputs/test
  • test:v27export JEST_VERSION=27 && mocha --no-timeouts ./tsOutputs/test
  • tests_for_versionmocha --no-timeouts ./tsOutputs/test
Dependencies4
  • @achrinza/node-ipc^10.1.9
  • globby^11.1.0
  • sealights-plugins-common2.0.135
  • ts-morph^25.0.0