google-proto-files
All of the Google API's protocol buffer files
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-wombot is a trusted Google automation publisher; missing gitHead is a minor CI environment signal, not a malware indicator, for this well-established proto-files package. | ai | |
| dependencies | unvetted-dep:protobufjs | AI (dependencies): protobufjs is the canonical protobuf library for Node.js and is the appropriate dependency for a package that provides Google API proto files. | ai | |
| provenance | no-provenance | AI (provenance): google-wombot is a Google automation account with a strong approval track record; lack of Sigstore provenance is a hygiene gap but not a security risk for this package. | ai |
Versions (showing 62 of 62)
| Version | Deps | Published |
|---|---|---|
| 5.0.1 | 2 / 17 | |
| 5.0.0 | 2 / 17 | |
| 4.2.0 | 2 / 15 | |
| 4.1.0 | 2 / 15 | |
| 4.0.0 | 2 / 15 | |
| 3.0.3 | 2 / 15 | |
| 3.0.2 | 2 / 15 | |
| 3.0.1 | 2 / 15 | |
| 3.0.0 | 2 / 15 | |
| 2.5.2 | 2 / 15 | |
| 2.5.0 | 2 / 15 | |
| 2.4.1 | 2 / 15 | |
| 2.4.0 | 2 / 17 | |
| 2.3.0 | 2 / 17 | |
| 2.2.0 | 2 / 15 | |
| 2.1.0 | 2 / 14 | |
| 2.0.0 | 2 / 16 | |
| 1.1.2 | 2 / 23 | |
| 1.1.1 | 2 / 23 | |
| 1.1.0 | 2 / 23 | |
| 1.0.3 | 2 / 23 | |
| 1.0.2 | 2 / 23 | |
| 1.0.1 | 2 / 23 | |
| 1.0.0 | 3 / 23 | |
| 0.20.0 | 3 / 25 | |
| 0.19.0 | 3 / 25 | |
| 0.18.0 | 2 / 24 | |
| 0.17.0 | 2 / 16 | |
| 0.16.1 | 3 / 17 | |
| 0.16.0 | 3 / 17 | |
| 0.15.1 | 3 / 17 | |
| 0.15.0 | 4 / 16 | |
| 0.14.2 | 4 / 16 | |
| 0.14.1 | 2 / 7 | |
| 0.14.0 | 2 / 7 | |
| 0.13.1 | 0 / 7 | |
| 0.13.0 | 0 / 7 | |
| 0.12.1 | 0 / 7 | |
| 0.12.0 | 0 / 7 | |
| 0.11.1 | 0 / 7 | |
| 0.11.0 | 0 / 7 | |
| 0.10.0 | 0 / 7 | |
| 0.9.1 | 0 / 6 | |
| 0.8.6 | 0 / 6 | |
| 0.8.5 | 0 / 6 | |
| 0.8.4 | 0 / 6 | |
| 0.8.3 | 0 / 6 | |
| 0.8.2 | 0 / 6 | |
| 0.8.1 | 0 / 6 | |
| 0.8.0 | 0 / 6 | |
| 0.7.0 | 0 / 6 | |
| 0.6.0 | 0 / 6 | |
| 0.5.0 | 0 / 6 | |
| 0.4.0 | 0 / 3 | |
| 0.3.0 | 0 / 3 | |
| 0.2.4 | 0 / 3 | |
| 0.2.3 | 0 / 3 | |
| 0.2.2 | 0 / 3 | |
| 0.2.1 | 0 / 3 | |
| 0.2.0 | 0 / 3 | |
| 0.1.1 | 0 / 3 | |
| 0.1.0 | 0 / 3 |
v5.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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This 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.
v4.1.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.