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
93Mature · −50% score
First published
Jan 2015
Publisher
ljharb

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"}'
Publisherljharb
Artifact bytes235,561
Previous version1.24.0
Published2025-12-13T07:06:24.832Z
SHA-256cf9582b4a5e376b2b5a9add185d546820d854fe644c7f1d70b0f55f8979f8cb2

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.24.1Version
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

Scripts14
  • eccheckeclint check $(git ls-files | xargs find 2> /dev/null | grep -vE 'node_modules|\.git')
  • linteslint .
  • postspacklegit ls-files | xargs git check-attr spackled | grep -v 'unspecified$' | cut -d: -f1 | xargs git add
  • posttestnpx npm@'>= 10.2' audit --production
  • prepacknpmignore --auto --commentLines=autogenerated
  • prepublishnot-in-publish || npm run prepublishOnly
  • prepublishOnlysafe-publish-latest && npm run spackle
  • prespacklenpm run --silent spackled | xargs rm || true
  • pretestnpm run lint
  • spacklenode operations/spackle 1 && node operations/build-unicode.mjs
  • spackledgit ls-files | xargs git check-attr spackled | grep -v 'unspecified$' | cut -d: -f1
  • testnpm run tests-only && npm run test:ses
  • test:sesnode --stack-size=5120 test/ses-compat
  • tests-onlynyc node --stack-size=5120 test
Dependencies54
  • array-buffer-byte-length^1.0.2
  • arraybuffer.prototype.slice^1.0.4
  • available-typed-arrays^1.0.7
  • call-bind^1.0.8
  • call-bound^1.0.4
  • data-view-buffer^1.0.2
  • data-view-byte-length^1.0.2
  • data-view-byte-offset^1.0.1
  • es-define-property^1.0.1
  • es-errors^1.3.0
  • es-object-atoms^1.1.1
  • es-set-tostringtag^2.1.0
  • es-to-primitive^1.3.0
  • function.prototype.name^1.1.8
  • get-intrinsic^1.3.0
  • get-proto^1.0.1
  • get-symbol-description^1.1.0
  • globalthis^1.0.4
  • gopd^1.2.0
  • has-property-descriptors^1.0.2
  • has-proto^1.2.0
  • has-symbols^1.1.0
  • hasown^2.0.2
  • internal-slot^1.1.0
  • is-array-buffer^3.0.5
  • is-callable^1.2.7
  • is-data-view^1.0.2
  • is-negative-zero^2.0.3
  • is-regex^1.2.1
  • is-set^2.0.3
  • …and 24 more.