← Home

@metamask/gator-permissions-controller

npm Repository Homepage

Controller for managing gator permissions with profile sync integration

22
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

kumavisfrederikboldingmetamaskbotgudahttmrtenmcmirenaugtur

Keywords

EthereumMetaMask

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): MetaMask migrated publishing to GitHub Actions CI; SLSA attestation confirms integrity. Stable for this package. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are known MetaMask contributors; consistent with org-level team expansion. ai
provenance no-provenance AI (provenance): MetaMask core packages consistently lack Sigstore provenance; not a risk signal for this publisher. ai

Versions (showing 22 of 22)

Version Deps Published
4.2.2 12 / 12
4.2.1 12 / 12
4.2.0 12 / 12
4.1.2 12 / 12
4.1.1 12 / 12
4.1.0 12 / 12
4.0.0 12 / 12
3.0.1 10 / 12
3.0.0 10 / 12
2.2.0 10 / 12
2.1.1 10 / 11
2.1.0 10 / 11
2.0.0 10 / 11
1.1.2 10 / 11
1.1.1 10 / 11
1.1.0 10 / 11
1.0.0 10 / 11
0.8.0 10 / 11
0.7.0 10 / 11
0.6.0 8 / 13
0.5.0 8 / 13
0.4.0 8 / 13

v4.2.2

2 findings
HIGH Publisher changed: metamaskbot → GitHub Actions (on 2026-07-01) provenance

This version was published by a different npm account than previous versions on 2026-07-01. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.2.1

2 findings
HIGH Publisher changed: metamaskbot → GitHub Actions (on 2026-06-22) provenance

This version was published by a different npm account than previous versions on 2026-06-22. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.