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 2021
- Publisher
- gandevops
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":["@ganintegrity/[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":["@ganintegrity/[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
Scripts2
check-configeslint --print-config .eslintrc.json | eslint-config-prettier-checktestecho "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