Package evidence
@ganintegrity/[email protected]
Install Lifecycle Remote Or Exec: postinstall="node -e \"String(process.env.GITLAB_CI).toLowerCase().includes('true') || require('husky').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
- 9
- Versions published
- 4
- First published
- Oct 2021
- Publisher
- gandevops
Recommended action
Block this updateStatic evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.
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":["@ganintegrity/[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":["@ganintegrity/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
New Lifecycle Script Vs Previous: postinstall added in 1.3.1 vs 1.3.0: "node -e \"String(process.env.GITLAB_CI).toLowerCase().includes('true') || require('husky').install();\""
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 high · score 75 · status changed
Evidence
Static findings
2 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 1.3.1 vs 1.3.0: "node -e \"String(process.env.GITLAB_CI).toLowerCase().includes('true') || require('husky').install();\"" | 40 |
| high | Install Lifecycle Remote Or Exec | package.json | postinstall="node -e \"String(process.env.GITLAB_CI).toLowerCase().includes('true') || require('husky').install();\"" | 30 |
Show all 3 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 1.3.1 vs 1.3.0: "node -e \"String(process.env.GITLAB_CI).toLowerCase().includes('true') || require('husky').install();\"" | 40 |
| high | Install Lifecycle Remote Or Exec | package.json | postinstall="node -e \"String(process.env.GITLAB_CI).toLowerCase().includes('true') || require('husky').install();\"" | 30 |
| low | Install-time lifecycle script | package.json | postinstall="node -e \"String(process.env.GITLAB_CI).toLowerCase().includes('true') || require('husky').install();\"" | 5 |
Manifest
Package metadata
Scripts3
check-configeslint --print-config .eslintrc.json | eslint-config-prettier-checkpostinstallnode -e "String(process.env.GITLAB_CI).toLowerCase().includes('true') || require('husky').install();"testecho "Error: no test specified" && exit 1
Dependencies13
@typescript-eslint/eslint-plugin5.0.0@typescript-eslint/parser5.0.0eslint-config-prettier6.0.0eslint-config-standard13.0.1eslint-import-resolver-typescript2.5.0eslint-plugin-import2.23.3eslint-plugin-jsdoc33.1.1eslint-plugin-mocha8.1.0eslint-plugin-node11.1.0eslint-plugin-prettier3.1.0eslint-plugin-promise4.2.1eslint-plugin-standard4.0.0typescript4.4.3