@metamask/execution-environments
Snap sandbox environments for executing SES javascript
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/webpack/iframe/bundle.js | AI (source-diff): Bundled webpack output implementing MetaMask's SES iframe sandbox; not a dropper. | ai | |
| source-diff | net-exec-file:dist/webpack/webworker/bundle.js | AI (source-diff): Bundled webpack output implementing MetaMask's SES webworker sandbox; not a dropper. | ai | |
| phantom-deps | phantom-dep:ses | AI (phantom-deps): ses is a webpack-bundled dependency used via config alias, not a direct import — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:stream-browserify | AI (phantom-deps): stream-browserify is a webpack polyfill alias, not directly imported — stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate MetaMask monorepo package; sparse README and no keywords are cosmetic issues, not spam indicators. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.23.0 | 11 / 32 | |
| 0.16.0 | 9 / 28 | |
| 0.15.0 | 9 / 27 | |
| 0.14.0 | 8 / 15 | |
| 0.13.0 | 8 / 15 | |
| 0.12.0 | 8 / 15 | |
| 0.11.1 | 8 / 15 | |
| 0.11.0 | 8 / 15 |
v0.16.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
3 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
4 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rekmarks) than the most recent previously approved version (gudahtt) on 2022-05-13, 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.12.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (rekmarks) than the most recent previously approved version (gudahtt) on 2022-05-09, 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.11.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (gudahtt) than the most recent previously approved version (rekmarks) on 2022-04-27, 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.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.