@metamask/snap-types No license 39 versions

@metamask/snap-types

npm Repository Homepage

39

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
phantom-deps	phantom-dep:@metamask/snap-utils	AI (phantom-deps): Types-only package; same-org dep declared but re-exported via type definitions, not directly imported in JS.	ai	2026/04/28
bogus-package	bogus-package	AI (bogus-package): Intentionally minimal TypeScript types package; sparse README and empty main entry are expected for this package type.	ai	2026/04/28

Versions (showing 39 of 39)

Version	Deps	Published
0.23.0	3 / 19	2022-11-07
0.22.3	3 / 19	2022-10-25
0.22.2	3 / 19	2022-10-11
0.22.1	3 / 19	2022-10-08
0.22.0	3 / 19	2022-10-04
0.21.0	3 / 17	2022-09-20
0.20.0	2 / 19	2022-08-25
0.19.1	1 / 19	2022-08-19
0.19.0	1 / 19	2022-08-17
0.18.1	1 / 19	2022-07-18
0.18.0	1 / 19	2022-07-14
0.17.0	1 / 19	2022-07-14
0.16.0	1 / 18	2022-06-14
0.15.0	1 / 2	2022-05-24
0.14.0	1 / 1	2022-05-14
0.13.0	1 / 1	2022-05-13
0.12.0	1 / 1	2022-05-09
0.11.1	1 / 1	2022-04-27
0.11.0	1 / 1	2022-04-25
0.10.7	1 / 1	2022-04-01
0.10.6	1 / 1	2022-03-21
0.10.5	1 / 1	2022-03-21
0.10.3	1 / 1	2022-03-18
0.10.1	1 / 1	2022-03-11
0.10.0	1 / 1	2022-03-10
0.9.0	1 / 1	2022-01-31
0.8.0	1 / 1	2022-01-21
0.7.0	1 / 1	2022-01-13
0.6.3	1 / 1	2021-12-21
0.6.2	1 / 1	2021-12-18
0.6.1	1 / 1	2021-12-17
0.6.0	1 / 1	2021-12-16
0.5.0	1 / 1	2021-12-07
0.4.0	1 / 1	2021-11-25
0.3.1	1 / 1	2021-11-08
0.3.0	1 / 1	2021-11-05
0.2.2	0 / 1	2021-10-01
0.2.0	0 / 1	2021-09-29
0.1.0	0 / 1	2021-09-09

v0.22.3

1 finding

LOW No provenance attestation provenance

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

v0.22.2

1 finding

LOW No provenance attestation provenance

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

v0.22.1

1 finding

LOW No provenance attestation provenance

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

v0.22.0

1 finding

LOW No provenance attestation provenance

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

v0.21.0

1 finding

LOW No provenance attestation provenance

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

v0.20.0

1 finding

LOW No provenance attestation provenance

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

v0.19.1

1 finding

LOW No provenance attestation provenance

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

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: gudahtt → 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 (gudahtt) 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.18.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 → gudahtt (on 2022-07-18, known maintainer) provenance

This version was published by a different npm account (gudahtt) than the most recent previously approved version (rekmarks) on 2022-07-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.18.0

1 finding

LOW No provenance attestation provenance

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

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.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 → gudahtt (on 2022-04-27, known maintainer) provenance

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

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