PkgRadar

Package evidence

@ladybugdb/[email protected]

Install-time lifecycle script: install="node install.js"

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
78,380Mainstream · −50% score
Versions published
56
First published
Mar 2026
Publisher
adsharma

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

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

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":["@ladybugdb/[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":["@ladybugdb/[email protected]"],"fail_on":"review"}'
Publisheradsharma
Artifact bytes494,226,631
Previous version0.15.0
Published2026-03-01T11:33:53.294Z
SHA-256

Why flagged

What the scanner saw

Install-time lifecycle script: install="node install.js"

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

Availability ledger

available

review
Last checked
reviewRisk
2Score
0.15.1-dev.1Version
Status history (2 events)
  1. scan_error → available · risk review · score 2 · status scan_error -> available, risk none -> review, score none -> 2
  2. new → scan_error · risk none · score — · refusing to fetch https://registry.npmjs.org/@ladybugdb/core/-/core-0.15.1-dev.1.tgz: content-length 167089893 exceeds 50000000

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowInstall-time lifecycle scriptpackage.jsoninstall="node install.js"5
lowOversized Unscannedmanifesttarball exceeds the 50MB fetch cap; scanned registry metadata (install scripts + dependencies) only0

Manifest

Package metadata

Scripts6
  • buildnode build.js
  • cleannode clean.js
  • clean-allnode clean.js all
  • installnode install.js
  • prepublishOnlynpm run build
  • testmocha test --timeout 20000
Dependencies2
  • cmake-js^8.0.0
  • node-addon-api^6.0.0