@ewanc26/malachite
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:csv-parse | AI (phantom-deps): Declared dep used in build/config context; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:multiformats | AI (phantom-deps): Likely used transitively via @ipld packages; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@atproto/common-web | AI (phantom-deps): ATProto ecosystem dep; likely used transitively; phantom-dep heuristic false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.12.1 | 12 / 2 | |
| 0.12.0 | 12 / 2 | |
| 0.11.0 | 10 / 2 | |
| 0.10.5 | 10 / 2 | |
| 0.10.4 | 10 / 2 | |
| 0.10.3 | 10 / 2 |
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.