@metamask/snaps-execution-environments SEE LICENSE IN LICENSE 9 versions

@metamask/snaps-execution-environments

npm Repository Homepage

Snap sandbox environments for executing SES javascript

9

Versions

SEE LICENSE IN LICENSE

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

kumavismetamaskbotgudahtt

Keywords

MetaMaskSnapsEthereum

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	2026/04/28
dependencies	unvetted-dep:@metamask/snaps-sdk	AI (dependencies): First-party MetaMask dependency; expected in this monorepo package.	ai	2026/04/28
dependencies	unvetted-dep:@metamask/snaps-utils	AI (dependencies): First-party MetaMask dependency; expected in this monorepo package.	ai	2026/04/28
dependencies	unvetted-dep:@metamask/json-rpc-engine	AI (dependencies): First-party MetaMask dependency; expected in this monorepo package.	ai	2026/04/28

Versions (showing 9 of 9)

Version	Deps	Published
11.1.1	10 / 39	2026-05-28
11.1.0	10 / 39	2026-04-21
11.0.2	10 / 39	2026-03-26
11.0.1	10 / 39	2026-03-11
11.0.0	10 / 39	2026-02-04
10.4.1	10 / 39	2026-01-27
10.4.0	10 / 39	2026-01-22
10.3.0	10 / 39	2025-12-02
10.2.3	10 / 39	2025-11-06

v11.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v11.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v11.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.