Package evidence
g-gremlin==0.1.31
Credential file access: matched "GOOGLE_APPLICATION_CREDENTIALS"
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
- 23
- First published
- Feb 2026
- Publisher
- g-gremlin authors
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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":["g-gremlin==0.1.31"],"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":["g-gremlin==0.1.31"],"fail_on":"review"}'Why flagged
What the scanner saw
Credential file access: matched "GOOGLE_APPLICATION_CREDENTIALS"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (2 events)
- available → available · risk review · score 10 · status available -> available, risk high -> review, score 314 -> 10
- new → available · risk high · score 314 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Credential file access | g_gremlin-0.1.31/src/g_gremlin/pubsub.py | matched "GOOGLE_APPLICATION_CREDENTIALS" | 10 |