@metamask/json-rpc-engine No license 10 versions

@metamask/json-rpc-engine

npm Repository Homepage

10

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.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): @metamask/messenger is a first-party MetaMask package; not a suspicious third-party injection.	ai	2026/05/02
publish-pattern	dormant-publish	AI (publish-pattern): MetaMask monorepo consolidation explains inactivity gap; publisher account is long-standing and trusted.	ai	2026/05/02
phantom-deps	phantom-dep:@types/deep-freeze-strict	AI (phantom-deps): @types packages are type-only and not directly imported at runtime; stable false positive for this package.	ai	2026/04/28

Versions (showing 10 of 10)

Version	Deps	Published
10.5.0	7 / 11	2026-05-11
10.4.0	7 / 11	2026-05-08
10.3.0	7 / 11	2026-05-01
10.2.4	6 / 11	2026-03-26
10.2.3	6 / 11	2026-03-02
10.2.2	6 / 11	2026-02-06
10.2.1	6 / 11	2026-01-15
10.2.0	6 / 11	2025-11-20
10.1.1	3 / 10	2025-10-09
10.1.0	3 / 10	2025-09-22

v10.5.0

1 finding

LOW No provenance attestation provenance

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

v10.4.0

1 finding

LOW No provenance attestation provenance

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

v10.3.0

1 finding

LOW No provenance attestation provenance

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

v10.2.4

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

1 finding

LOW No provenance attestation provenance

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

v10.2.2

1 finding

LOW No provenance attestation provenance

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

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

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

1 finding

LOW No provenance attestation provenance

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

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