@metamask/earn-controller MIT 11 versions

@metamask/earn-controller

npm Repository Homepage

Manages state for earning features and coordinates interactions between staking services, SDK integrations, and other controllers to enable users to participate in various earning opportunities

11

Versions

MIT

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.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@metamask/messenger	AI (dependencies): First-party MetaMask monorepo dependency; same org as this package.	ai	2026/04/28
dependencies	unvetted-dep:@metamask/stake-sdk	AI (dependencies): First-party MetaMask SDK dependency; same org as this package.	ai	2026/04/28
dependencies	unvetted-dep:@metamask/keyring-api	AI (dependencies): First-party MetaMask dependency; same org as this package.	ai	2026/04/28
dependencies	unvetted-dep:@metamask/controller-utils	AI (dependencies): First-party MetaMask monorepo dependency; same org as this package.	ai	2026/04/28
dependencies	unvetted-dep:@metamask/network-controller	AI (dependencies): First-party MetaMask monorepo dependency; same org as this package.	ai	2026/04/28

Versions (showing 11 of 11)

Version	Deps	Published
12.1.2	10 / 11	2026-05-12
12.1.1	10 / 11	2026-05-11
12.1.0	10 / 11	2026-05-01
12.0.0	10 / 11	2026-04-13
11.2.1	10 / 11	2026-03-27
11.2.0	10 / 11	2026-03-26
11.1.2	10 / 10	2026-03-09
11.1.1	10 / 10	2026-02-19
11.1.0	10 / 10	2026-01-15
11.0.0	8 / 12	2025-11-20
10.0.0	8 / 12	2025-11-10

v12.1.2

1 finding

LOW No provenance attestation provenance

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

v12.1.1

1 finding

LOW No provenance attestation provenance

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

v12.1.0

1 finding

LOW No provenance attestation provenance

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

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

v11.2.1

1 finding

LOW No provenance attestation provenance

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

v11.2.0

1 finding

LOW No provenance attestation provenance

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

v11.1.2

1 finding

LOW No provenance attestation provenance

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

v11.1.1

1 finding

LOW No provenance attestation provenance

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

v11.1.0

1 finding

LOW No provenance attestation provenance

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

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

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