@metamask/snap-controllers No license 13 versions

@metamask/snap-controllers

npm Repository Homepage

13

Versions

—

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

ritavedanfinlaykumavisrekmarksmetamaskbotgudahttbrad.deckersethkfman

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	large-new-source-files	AI (source-diff): New PermissionController module, legitimate feature growth.	ai	2026/07/22
source-diff	source-size-tripled	AI (source-diff): Size increase from added legitimate source files, not bundled payload.	ai	2026/07/22
publish-pattern	new-deps-added	AI (publish-pattern): Deps are well-known utility libs (deep-freeze-strict, fast-deep-equal).	ai	2026/07/22
phantom-deps	phantom-dep:@types/deep-freeze-strict	AI (phantom-deps): Types package, not directly imported by convention.	ai	2026/07/22
phantom-deps	phantom-dep:cron-parser	AI (phantom-deps): Declared runtime dep in a monorepo; may be used indirectly or in config — stable false positive.	ai	2026/04/28
bogus-package	bogus-package	AI (bogus-package): Legitimate MetaMask Snaps controller package; sparse README is typical for internal monorepo packages.	ai	2026/04/28
phantom-deps	phantom-dep:@metamask/snap-types	AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic unreliable for type-only deps in TS monorepos.	ai	2026/04/28

Versions (showing 13 of 13)

Version	Deps	Published
0.23.0	21 / 33	2022-11-07
0.21.0	19 / 33	2022-09-20
0.20.0	19 / 33	2022-08-25
0.19.1	22 / 33	2022-08-19
0.19.0	22 / 33	2022-08-17
0.5.0	15 / 9	2021-12-07
0.4.0	15 / 9	2021-11-25
0.3.1	12 / 9	2021-11-08
0.3.0	12 / 9	2021-11-05
0.2.2	12 / 9	2021-10-01
0.2.0	12 / 9	2021-09-29
0.1.2	12 / 9	2021-09-28
0.1.0	12 / 9	2021-09-09

v0.21.0

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 → metamaskbot (on 2022-09-20, known maintainer) provenance

This version was published by a different npm account (metamaskbot) than the most recent previously approved version (rekmarks) on 2022-09-20, but metamaskbot 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.20.0

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 → metamaskbot (on 2022-08-25, known maintainer) provenance

This version was published by a different npm account (metamaskbot) than the most recent previously approved version (rekmarks) on 2022-08-25, but metamaskbot 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.19.1

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 → metamaskbot (on 2022-08-19, known maintainer) provenance

This version was published by a different npm account (metamaskbot) than the most recent previously approved version (rekmarks) on 2022-08-19, but metamaskbot 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.19.0

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 → metamaskbot (on 2022-08-17, known maintainer) provenance

This version was published by a different npm account (metamaskbot) than the most recent previously approved version (rekmarks) on 2022-08-17, but metamaskbot 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.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. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

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

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