@metamask/snaps-simulation
A simulation framework for MetaMask Snaps, enabling headless testing of Snaps in a controlled environment
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): MetaMask org package with consistent publish history; gap reflects normal major-version development cycle, not account takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is @metamask/chain-agnostic-permission, a first-party MetaMask package; benign for this org. | ai | |
| phantom-deps | phantom-dep:@metamask/snaps-execution-environments | AI (phantom-deps): Declared as a runtime dependency in package.json; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 21 / 17 | |
| 4.1.4 | 21 / 17 | |
| 4.1.3 | 21 / 17 | |
| 4.1.2 | 21 / 17 | |
| 4.1.1 | 21 / 17 | |
| 4.1.0 | 22 / 17 | |
| 4.0.0 | 22 / 17 | |
| 3.8.0 | 21 / 17 | |
| 3.7.0 | 20 / 17 | |
| 3.6.0 | 20 / 17 |
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.