PkgRadar

Package evidence

@emilgroup/[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
98Mature · −50% score
First published
Jun 2022
Publisher
cover42devs
External confirmation
MAL-2026-2035OSV 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.

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":["@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 bytes190,446
Previous version1.17.0
Published2025-12-10T16:05:41.300Z
SHA-2562ec9c02df1e43817077581d6284ae975c6765f67870fa038d3f746ba2cb1b992

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

high
Last checked
highRisk
0Score
1.17.1Version
Status history (1 event)
  1. new → available · risk high · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts7
  • buildtsc
  • formatprettier . --write
  • linteslint 'lib/**/*.ts'
  • lint-fixeslint --fix 'lib/**/*.ts'
  • preparehusky
  • prepublishOnlynpm run lint && npm run build
  • testecho "Error: no test specified" && exit 1
Dependencies7
  • @emilgroup/core^9.69.1
  • @nestjs/common10.4.20
  • @nestjs/core10.4.20
  • @nestjs/swagger7.4.2
  • dayjs^1.11.19
  • lodash^4.17.21
  • rxjs7.8.2