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
- 6
- Versions published
- 2
- First published
- Dec 2021
- Publisher
- zhongruige
Recommended action
Looks clean — keep monitoringNo 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":["@woocommerce/[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":["@woocommerce/[email protected]"],"fail_on":"review"}'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
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts7
e2ejeste2e:apijest --group=apie2e:hellojest --group=hellolinteslint data endpoints tests utils --ext=js,ts,tsxlint:fixeslint data endpoints tests utils --ext=js,ts,tsx --fixmake:collectionnode utils/api-collection/build-collection.jsreportallure generate --clean && allure serve
Dependencies7
allure-commandline^2.17.2dotenv^10.0.0jest^27.5.1jest-allure^0.1.3jest-runner-groups^2.1.0postman-collection^4.1.0supertest^6.1.4