@trystero-p2p/ipfs
IPFS strategy for Trystero
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Sub-package of known trystero project; missing repo URL and README quirks are benign. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.25.1 | 2 / 0 | |
| 0.25.0 | 2 / 0 | |
| 0.24.0 | 2 / 0 | |
| 0.23.1 | 2 / 0 | |
| 0.23.0 | 2 / 0 |
v0.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.