@metamask/superstruct
Supply chain provenance
Status for the latest visible version.
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): Transition from metamaskbot to GitHub Actions CI/CD is an improvement, not a risk. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): MetaMask org package; dormancy followed by CI/CD-attested publish is normal maintenance. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 3.4.1 | 0 / 32 | |
| 3.4.0 | 0 / 32 | |
| 3.3.0 | 0 / 32 | |
| 3.2.1 | 0 / 32 | |
| 3.2.0 | 0 / 32 | |
| 3.1.0 | 0 / 32 | |
| 3.0.0 | 0 / 32 |
v3.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-02. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.