@metamask/iframe-execution-environment-service No license 21 versions

@metamask/iframe-execution-environment-service

npm Repository Homepage

An iframe execution environment for MetaMask Snaps.

21

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

danfinlaykumavisrekmarksmetamaskbotgudahttbrad.deckersethkfman

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Internal MetaMask monorepo package; sparse README and no keywords are expected for org-internal tooling.	ai	2026/04/28
phantom-deps	phantom-dep:eth-rpc-errors	AI (phantom-deps): Declared dep used transitively via snap-controllers; phantom-dep heuristic fires but not a real risk here.	ai	2026/04/28
phantom-deps	phantom-dep:@metamask/object-multiplex	AI (phantom-deps): Same-org dep; phantom-dep heuristic is a false positive for this package.	ai	2026/04/28

Versions (showing 21 of 21)

Version	Deps	Published
0.11.1	11 / 7	2022-04-27
0.11.0	11 / 7	2022-04-25
0.10.7	12 / 5	2022-04-01
0.10.6	12 / 4	2022-03-21
0.10.5	12 / 4	2022-03-21
0.10.3	12 / 4	2022-03-18
0.10.2	12 / 4	2022-03-11
0.10.0	12 / 4	2022-03-10
0.9.0	12 / 4	2022-01-31
0.8.0	12 / 4	2022-01-21
0.7.0	12 / 4	2022-01-13
0.6.3	12 / 4	2021-12-21
0.6.2	12 / 4	2021-12-18
0.6.1	12 / 4	2021-12-17
0.6.0	12 / 4	2021-12-16
0.5.0	12 / 4	2021-12-07
0.4.0	13 / 4	2021-11-25
0.3.1	13 / 4	2021-11-08
0.3.0	13 / 4	2021-11-05
0.2.2	12 / 4	2021-10-01
0.2.0	12 / 4	2021-09-29

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.7

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gudahtt → rekmarks (on 2022-04-01, known maintainer) provenance

This version was published by a different npm account (rekmarks) than the most recent previously approved version (gudahtt) on 2022-04-01, but rekmarks is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.10.6

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: gudahtt → rekmarks (on 2022-03-21, known maintainer) provenance

This version was published by a different npm account (rekmarks) than the most recent previously approved version (gudahtt) on 2022-03-21, but rekmarks is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.10.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: rekmarks → gudahtt (on 2022-03-21, known maintainer) provenance

This version was published by a different npm account (gudahtt) than the most recent previously approved version (rekmarks) on 2022-03-21, but gudahtt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.10.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: rekmarks → gudahtt (on 2022-03-18, known maintainer) provenance

This version was published by a different npm account (gudahtt) than the most recent previously approved version (rekmarks) on 2022-03-18, but gudahtt is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.10.2

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.2

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.

v0.2.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.