PkgRadar

Package evidence

@mixmaxhq/[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
4
First published
Oct 2022
Publisher
mixmax-codeship

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

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":"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":["@mixmaxhq/[email protected]"],"fail_on":"review"}'
Artifact bytes114,082
Previous versionnone
Published2022-10-28T11:53:34.409Z
SHA-256dd77eb782d9d4f76d21e6e0b3e80bd4c545bb36d34da5c86e4c0100429111bc5

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
1.0.0Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts9
  • buildwebpack
  • cinpm run lint && npm test
  • ci:commitlintcommitlint-jenkins --pr-only
  • examplewebpack --config example/webpack.config.babel.js
  • linteslint .
  • 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