ipfs-grpc-protocol
Protobuf definitions for the IPFS gRPC API
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 | publisher-changed | AI (provenance): IPFS project migrated to npm-service-account-ipfs org service account; this is a documented org-level transition, not a compromise. Stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): npm-service-account-ipfs is the IPFS org service account with 135 approved packages and strong track record; addition reflects org migration, not a takeover. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): 0.0.0 is a namespace placeholder by a trusted IPFS ecosystem maintainer (achingbrain); not indicative of malicious intent. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Placeholder stub by a well-established publisher; sparse metadata is expected for a namespace reservation in the IPFS ecosystem. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.8.1 | 0 / 4 | |
| 0.8.0 | 0 / 4 | |
| 0.7.0 | 0 / 4 | |
| 0.6.0 | 0 / 3 | |
| 0.5.5 | 0 / 4 | |
| 0.5.4 | 0 / 4 | |
| 0.5.3 | 0 / 4 | |
| 0.5.2 | 0 / 4 | |
| 0.5.1 | 0 / 4 | |
| 0.5.0 | 0 / 4 | |
| 0.4.1 | 0 / 3 | |
| 0.4.0 | 0 / 3 | |
| 0.3.0 | 0 / 3 | |
| 0.2.0 | 0 / 3 | |
| 0.1.0 | 0 / 3 | |
| 0.0.0 | 0 / 0 |
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
2 findingsThis version was published by a different npm account than previous versions on 2022-09-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.