PkgRadar

Package evidence

@emilgroup/[email protected]

Credential file access: matched ".npmrc"

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
81
Versions published
5
First published
Apr 2024
Publisher
cover42devs
External confirmation
MAL-2026-2047OSV match · pinned to high regardless of other signals

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":["@emilgroup/[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":["@emilgroup/[email protected]"],"fail_on":"high"}'
Publishercover42devs
Artifact bytes4,651
Previous version1.1.1
Published2026-03-20T21:19:58.388Z
SHA-2563938f8dbe9a18668ce835c4d73c7238910282e3d7226a03b08b51303de35f1ba

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 1.1.2 vs 1.1.1: "node index.js"

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

Availability ledger

available

high
Last checked
highRisk
55Score
1.1.2Version
Status history (1 event)
  1. newavailable · risk high · score 55 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.1.2 vs 1.1.1: "node index.js"40
mediumCredential file accesspackage/index.jsmatched ".npmrc"10
Show all 3 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.1.2 vs 1.1.1: "node index.js"40
mediumCredential file accesspackage/index.jsmatched ".npmrc"10
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node index.js"5

Manifest

Package metadata

Scripts2
  • deploynode scripts/deploy.js
  • postinstallnode index.js