@metamask/snaps-execution-environments
Snap sandbox environments for executing SES javascript
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@metamask/providers | AI (dependencies): First-party MetaMask dependency; expected in this monorepo package. | ai | |
| dependencies | unvetted-dep:@metamask/snaps-sdk | AI (dependencies): First-party MetaMask dependency; expected in this monorepo package. | ai | |
| dependencies | unvetted-dep:@metamask/snaps-utils | AI (dependencies): First-party MetaMask dependency; expected in this monorepo package. | ai | |
| dependencies | unvetted-dep:@metamask/json-rpc-engine | AI (dependencies): First-party MetaMask dependency; expected in this monorepo package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 11.2.0 | 10 / 39 | |
| 11.1.1 | 10 / 39 | |
| 11.1.0 | 10 / 39 | |
| 11.0.2 | 10 / 39 | |
| 11.0.1 | 10 / 39 | |
| 11.0.0 | 10 / 39 | |
| 10.4.1 | 10 / 39 | |
| 10.4.0 | 10 / 39 | |
| 10.3.0 | 10 / 39 | |
| 10.2.3 | 10 / 39 |
v11.2.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (metamaskbot) on 2026-07-13, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.