PkgRadar

Package evidence

@mixmaxhq/[email protected]

Install-time lifecycle script: postinstall="patch-package"

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
69
Versions published
4
First published
Oct 2022
Publisher
jsalvata

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":["@mixmaxhq/[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":["@mixmaxhq/[email protected]"],"fail_on":"high"}'
Publisherjsalvata
Artifact bytes115,322
Previous version1.1.1
Published2024-05-28T18:28:30.524Z
SHA-25645c21ab19df6aa81e75d4fd41c7c5d64de36639fd2358170fc9963bb85853712

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 1.2.8 vs 1.1.1: "patch-package"

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

Availability ledger

available

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

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.2.8 vs 1.1.1: "patch-package"40
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.2.8 vs 1.1.1: "patch-package"40
lowInstall-time lifecycle scriptpackage.jsonpostinstall="patch-package"5

Manifest

Package metadata

Scripts10
  • buildNODE_OPTIONS=--openssl-legacy-provider webpack
  • cinpm run lint && npm test
  • ci:commitlintcommitlint-jenkins --pr-only
  • examplewebpack --config example/webpack.config.babel.js
  • linteslint .
  • postinstallpatch-package
  • preparenpm run build
  • prepublishOnlynpm run build && if [ "$CI" = '' ] && [ "$npm_config_dry_run" != true ]; then node -p 'JSON.parse(process.env.npm_package_config_manualPublishMessage)'; exit 1; fi
  • semantic-releaseSEMANTIC_COMMITLINT_SKIP=4febd2d,9d72d63,2e81149 semantic-release
  • testjest --coverage