A simple common HTTP client specifically for Google APIs and services.
88%
Total Score
healthy
Active, well-supported project with strong maintenance signals, but the linked repository does not clearly identify gaxios.
No build attestation or trusted-publisher provenance is present, leaving publication origin less transparent. This is a supply-chain transparency gap, though the active organization-backed project provides compensating maintenance evidence.
The package has a prepare lifecycle script, which adds install-time behavior and merits awareness, but this signal alone does not show unsafe or excessive installation activity.
The linked repository name does not match gaxios and its README does not mention gaxios. Although a monorepo mismatch can be normal, the absence of any package mention leaves the package-to-source relationship less transparent.
All 71 analyzed action references are pinned, and 17 workflows use read-only permissions. The audit is incomplete because one of 19 workflows failed analysis, and two high-confidence low-severity adhoc-package findings show packages installed outside lockfiles; the pull_request_target workflow has broad write permissions but no detected untrusted checkout or script injection.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
extend Version ^3.0.2 | — | — |
node-fetch Version ^3.3.2 | — | — |
https-proxy-agent Version ^7.0.1 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.