@metamask/gator-permissions-snap (MIT-0 OR Apache-2.0) 13 versions

@metamask/gator-permissions-snap

npm Repository Homepage

Grants 7715 permissions from a DeleGator smart account

13

Versions

(MIT-0 OR Apache-2.0)

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:dist/bundle.js	AI (source-diff): mm-snap bundles legitimate hex/bytes utility code that triggers long-string heuristics; stable false positive for this package.	ai	2026/05/02
phantom-deps	phantom-dep:@metamask/utils	AI (phantom-deps): Same org scope; used transitively in snap bundle context.	ai	2026/04/28
phantom-deps	phantom-dep:@metamask/abi-utils	AI (phantom-deps): Same org scope; used transitively in snap bundle context.	ai	2026/04/28
phantom-deps	phantom-dep:zod	AI (phantom-deps): Snap bundle; zod likely bundled at build time, not directly imported in source.	ai	2026/04/28
phantom-deps	phantom-dep:@metamask/delegation-core	AI (phantom-deps): Same org scope; used transitively in snap bundle context.	ai	2026/04/28
phantom-deps	phantom-dep:@metamask/profile-sync-controller	AI (phantom-deps): Same org scope; used transitively in snap bundle context.	ai	2026/04/28
phantom-deps	phantom-dep:@metamask/snaps-sdk	AI (phantom-deps): Same org scope; used transitively in snap bundle context.	ai	2026/04/28

Versions (showing 13 of 13)

Version	Deps	Published
2.2.0	6 / 27	2026-05-20
2.1.0	6 / 27	2026-05-12
2.0.0	6 / 27	2026-05-06
1.3.1	6 / 27	2026-03-23
1.3.0	6 / 27	2026-03-16
1.2.0	6 / 27	2026-03-11
1.1.1	6 / 27	2026-01-26
1.1.0	6 / 27	2026-01-21
1.0.0	6 / 25	2026-01-15
0.7.0	6 / 25	2025-11-12
0.6.1	6 / 25	2025-11-10
0.6.0	6 / 25	2025-11-06
0.5.0	6 / 25	2025-11-05

v2.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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

v1.3.1

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.

v1.3.0

2 findings

HIGH Long encoded string in modified file: dist/bundle.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.2.0

2 findings

HIGH Long encoded string in modified file: dist/bundle.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.1.1

2 findings

HIGH Long encoded string in modified file: dist/bundle.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.1.0

2 findings

HIGH Long encoded string in modified file: dist/bundle.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v1.0.0

2 findings

HIGH Long encoded string in modified file: dist/bundle.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.7.0

2 findings

HIGH Long encoded string in modified file: dist/bundle.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.6.1

2 findings

HIGH Long encoded string in modified file: dist/bundle.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v0.6.0

2 findings

HIGH Long encoded string in modified file: dist/bundle.js source-diff

Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

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. Only ~12% of npm packages have provenance, so this is common but not ideal.