@suimpp/mpp
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): Publisher has strong track record; missing gitHead is a process change, not a malware indicator for this package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): @suimpp/mpp is a scoped Sui blockchain payment package with no relation to the pg PostgreSQL client; Levenshtein match is a false positive for this namespace. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @suimpp/mpp is a scoped Sui blockchain payment package with no relation to the yup validation library; Levenshtein match is a false positive for this namespace. | ai | |
| dependencies | unvetted-dep:@mysten/sui | AI (dependencies): @mysten/sui is the official Sui blockchain SDK from Mysten Labs; its use is expected and appropriate for a Sui payment integration package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.7.1 | 3 / 6 | |
| 0.7.0 | 3 / 6 | |
| 0.6.0 | 3 / 5 | |
| 0.5.0 | 3 / 5 | |
| 0.4.0 | 3 / 5 | |
| 0.3.1 | 3 / 5 | |
| 0.3.0 | 3 / 5 |
v0.7.1
2 findingsPackage 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: funkii.
v0.7.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: funkii.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
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.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.