@buildeross/ipfs-service
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-tlds | AI (semgrep): flk-ipfs.xyz is a legitimate public IPFS gateway; .xyz TLD flag is a stable false positive for this IPFS service package. | ai | |
| phantom-deps | phantom-dep:it-last | AI (phantom-deps): Declared dep used transitively or in config/type references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:url-join | AI (phantom-deps): Declared dep used transitively or in config/type references; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:ipfs-core-types | AI (phantom-deps): Type-only dependency; phantom-dep heuristic fires on type imports; stable false positive. | ai | |
| phantom-deps | phantom-dep:ipfs-http-client | AI (phantom-deps): Core IPFS client dep; phantom-dep heuristic likely misses indirect/re-exported usage; stable false positive. | ai | |
| phantom-deps | phantom-dep:@brokerloop/ttlcache | AI (phantom-deps): TTL cache dep; phantom-dep heuristic fires on config references; stable false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.3.2 | 1 / 8 | |
| 0.3.1 | 1 / 8 | |
| 0.3.0 | 1 / 8 | |
| 0.2.2 | 1 / 8 | |
| 0.2.1 | 1 / 8 | |
| 0.2.0 | 1 / 8 | |
| 0.1.2 | 7 / 7 | |
| 0.1.0 | 7 / 6 |
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.