Package evidence

@woocommerce/[email protected]

Install-time lifecycle script: postinstall="composer install"

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: 127
Versions published: 8
First published: Apr 2021
Publisher: psealock

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 tarball Add 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":["@woocommerce/[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":["@woocommerce/[email protected]"],"fail_on":"high"}'

Publisherpsealock

Artifact bytes73,805

Previous version2.0.1

Published2022-06-15T22:35:36.339Z

SHA-256281ed2504b8d0599dbc32517243e0eec2fbcff2f60012a104b73a979151b4781

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 2.1.0 vs 2.0.1: "composer install"

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

Availability ledger

available

high

14h agoLast checked

highRisk

45Score

2.1.0Version

Status history (1 event)

new → available14h ago · risk high · score 45 · status changed

Evidence

Static findings

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

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 2.1.0 vs 2.0.1: "composer install"	40

Show all 2 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 2.1.0 vs 2.0.1: "composer install"	40
low	Install-time lifecycle script	package.json	postinstall="composer install"	5

Manifest

Package metadata

Scripts11

buildpnpm run build:js && pnpm run build:css
build:csswebpack
build:jstsc --build ./tsconfig.json ./tsconfig-cjs.json
changelogcomposer exec -- changelogger
cleanpnpm exec rimraf tsconfig.tsbuildinfo build build-*
linteslint src
lint:fixeslint src --fix
postinstallcomposer install
startconcurrently "tsc --build --watch" "webpack --watch"
testjest --config ./jest.config.json
test-stagedjest --bail --config ./jest.config.json --findRelatedTests

Dependencies10

@woocommerce/experimental3.1.0
@wordpress/components^19.5.0
@wordpress/compose^5.1.2
@wordpress/data^6.3.0
@wordpress/element^4.1.1
@wordpress/i18n^4.3.1
@wordpress/notices^3.3.2
classnames^2.3.1
prop-types^15.8.1
react-transition-group^4.4.2