Package evidence

[email protected]

Credential file access: matched "NPM_TOKEN"

Recommended action

Block this update

Static evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.

Inspect tarball Add 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":"high"}'

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":"high"}'

Publisherpicker_express

Artifact bytes22,416

Previous version5.0.10

Published2026-05-15T04:07:02.415Z

SHA-25677ab859290aaef890bf38022d7688eebb80e9c65e7b0c12b5474063e9f8c4a39

Why flagged

What the scanner saw

Credential file access: matched "NPM_TOKEN"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

high

23d agoLast checked

highRisk

30Score

5.0.11Version

Status history (1 event)

new → available23d ago · risk high · score 30 · status changed

Related candidates

Linked campaigns and clusters

Publisher / release actor burststale

picker_express

2 members · evidence strength 50

Evidence

Static findings

1 static · 0 from release diff · showing high-signal first.

Severity	Kind	Path	Detail	Points
high	Credential file access	package/bitbucket-pipelines.yml	matched "NPM_TOKEN"	30

Manifest

Package metadata

Scripts1

testecho "Error: no test specified" && exit 1

Dependencies3

lodash^4.17.20
mongoose^8.0.4
winston^3.3.3