PkgRadar

Package evidence

[email protected]

Credential file access: matched "AWS_ACCESS_KEY"

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
36
First published
Jan 2026
Publisher
vitorlourenco

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.

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"}'
Publishervitorlourenco
Artifact bytes1,246,415
Previous version1.5.12
Published2026-05-06T13:39:45.663Z
SHA-25625f0d15b4979e99a66e98b9f2cb45a7b14b76b8cffa4c58cee49ac3a291f36ef

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 1.6.0 vs 1.5.12: "node postinstall.js"

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

Availability ledger

available

high
Last checked
highRisk
60Score
1.6.0Version
Status history (2 events)
  1. availableavailable · risk high · score 60 · status available -> available, risk high -> high, score 100 -> 60
  2. newavailable · risk high · score 100 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.6.0 vs 1.5.12: "node postinstall.js"40
Show all 6 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.6.0 vs 1.5.12: "node postinstall.js"40
lowCredential file accesspackage/dist/src/lib/analyzers/java/security-checks/hardcoded-credentials.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/dist/src/lib/analyzers/java/security-checks/injection-attacks.jsmatched ".ssh/"5
lowCredential file accesspackage/dist/src/lib/analyzers/python/security-checks/security-misconfiguration.jsmatched "aws_access_key"5
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node postinstall.js"5
lowLarge Javascript Payloadpackage/dist/codeslick-bundle.cjs2249297 bytes0

Manifest

Package metadata

Scripts6
  • buildnode build.mjs
  • build:typechecktsc --noEmit
  • devtsc --watch
  • postinstallnode postinstall.js
  • prepublishOnlynpm run build
  • testvitest
Dependencies6
  • chalk^4.1.2
  • cli-table3^0.6.3
  • glob^13.0.1
  • ora^5.4.1
  • typescript^5.3.3
  • yargs^17.7.2