← Home

@metamask/gas-fee-controller

npm Repository Homepage
9
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

kumavismetamaskbotgudahtt

Keywords

EthereumMetaMask

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@types/uuid AI (phantom-deps): Type-only package in dependencies is a known MetaMask monorepo pattern; not a real phantom dep risk. ai
phantom-deps phantom-dep:@types/bn.js AI (phantom-deps): Type-only package in dependencies is a known MetaMask monorepo pattern; not a real phantom dep risk. ai
phantom-deps phantom-dep:@metamask/ethjs-unit AI (phantom-deps): Same-org sibling dep; may be used transitively or indirectly. Stable false positive for this package. ai

Versions (showing 9 of 9)

Version Deps Published
26.2.2 12 / 14
26.2.1 12 / 14
26.2.0 12 / 14
26.1.1 11 / 14
26.1.0 11 / 14
26.0.3 11 / 13
26.0.2 11 / 14
26.0.1 11 / 14
26.0.0 10 / 15

v26.2.2

1 finding
LOW No provenance attestation provenance

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

v26.2.1

1 finding
LOW No provenance attestation provenance

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

v26.2.0

1 finding
LOW No provenance attestation provenance

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

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

v26.1.0

1 finding
LOW No provenance attestation provenance

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

v26.0.3

1 finding
LOW No provenance attestation provenance

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

v26.0.2

1 finding
LOW No provenance attestation provenance

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

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

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