@metamask/name-controller MIT 3 versions

@metamask/name-controller

npm Repository Homepage

Stores and suggests names for values such as Ethereum addresses

Versions

MIT

License

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

danfinlaykumavismetamaskbotgudahtt

Keywords

MetaMaskEthereum

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Established MetaMask org package; provenance absence is consistent across their published packages.	ai	2026/04/28

Versions (showing 3 of 3)

Version	Deps	Published
9.1.1	5 / 10	2026-03-26
9.1.0	5 / 10	2026-03-17
9.0.0	5 / 8	2025-10-27

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

v9.1.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v9.0.0

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.