gaxios
A simple common HTTP client specifically for Google APIs and services.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Google-maintained package published by google-wombot; missing gitHead is a benign publish-environment change, not a security signal. | ai | |
| provenance | no-provenance | AI (provenance): Google-maintained package; no-provenance is informational and not a risk signal for this well-established publisher. | ai |
Versions (showing 51 of 82)
| Version | Deps | Published |
|---|---|---|
| 7.1.4 | 3 / 45 | |
| 7.1.3 | 4 / 45 | |
| 7.1.2 | 3 / 45 | |
| 7.1.1 | 3 / 45 | |
| 7.1.0 | 3 / 45 | |
| 7.0.0 | 3 / 45 | |
| 6.7.1 | 5 / 48 | |
| 6.7.0 | 5 / 47 | |
| 6.6.0 | 5 / 47 | |
| 6.5.0 | 5 / 47 | |
| 6.4.0 | 5 / 47 | |
| 6.3.0 | 4 / 48 | |
| 6.2.0 | 4 / 48 | |
| 6.1.1 | 4 / 48 | |
| 6.1.0 | 4 / 48 | |
| 6.0.4 | 4 / 48 | |
| 6.0.3 | 4 / 48 | |
| 6.0.2 | 4 / 48 | |
| 6.0.1 | 4 / 48 | |
| 6.0.0 | 4 / 48 | |
| 5.1.3 | 4 / 48 | |
| 5.1.2 | 4 / 48 | |
| 5.1.1 | 4 / 48 | |
| 5.1.0 | 4 / 47 | |
| 5.0.2 | 4 / 48 | |
| 5.0.1 | 4 / 48 | |
| 5.0.0 | 5 / 47 | |
| 4.3.3 | 5 / 47 | |
| 4.3.2 | 5 / 46 | |
| 4.3.1 | 5 / 46 | |
| 4.3.0 | 5 / 48 | |
| 4.2.1 | 5 / 45 | |
| 4.2.0 | 5 / 45 | |
| 4.1.0 | 5 / 45 | |
| 4.0.1 | 5 / 48 | |
| 4.0.0 | 5 / 48 | |
| 3.2.0 | 5 / 48 | |
| 3.1.0 | 5 / 48 | |
| 3.0.4 | 5 / 45 | |
| 3.0.3 | 5 / 39 | |
| 3.0.2 | 5 / 40 | |
| 3.0.1 | 5 / 40 | |
| 3.0.0 | 5 / 40 | |
| 2.3.4 | 5 / 40 | |
| 2.3.3 | 5 / 40 | |
| 2.3.2 | 5 / 40 | |
| 2.3.1 | 5 / 40 | |
| 2.3.0 | 5 / 41 | |
| 2.2.2 | 5 / 41 | |
| 2.2.0 | 5 / 41 | |
| 2.1.0 | 5 / 41 |
v7.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: google-wombot.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.