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
102Mature · −50% score
First published
Apr 2019
Publisher
7c

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"}'
Publisher7c
Artifact bytes47,378
Previous version1.2.3
Published2026-06-04T18:58:28.206Z
SHA-256644f6a9922b35dd7aca860bd05e159fe4c907ca2aad9f878e6910659b670c6d2

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
2.0.0Version
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

Scripts5
  • buildtsc -p tsconfig.json
  • cleanrm -rf dist
  • prepublishOnlynpm run clean && npm run build
  • testjest --forceExit --verbose
  • test:exhaustivejest --forceExit --runInBand --verbose tests/ --testPathIgnorePatterns /node_modules/
Dependencies21
  • @7c/validurl0.0.3
  • @maxmind/geoip2-node^6.3.4
  • @types/debug^4.1.12
  • @types/ip6addr^0.2.6
  • @types/mysql^2.15.25
  • @types/node^20.11.5
  • @types/request^2.48.12
  • @types/validator^13.11.8
  • aes-js^3.1.2
  • chalk^3.0.0
  • debug^4.3.4
  • ip-range-check^0.2.0
  • ip6=0.2.7
  • js-sha512^0.8.0
  • knex^3.1.0
  • mysql^2.18.1
  • mysql2^3.9.1
  • node-vault^0.12.0
  • psl^1.9.0
  • punycode^2.1.1
  • validator^13.7.0