@keystonehq/metamask-airgapped-keyring

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

keystoneorgsoralitliyanlance

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:tsdx	AI (dependencies): tsdx is a well-known TS build tool, used only as dev/build tooling.	ai	2026/07/22
phantom-deps	phantom-dep:tsdx	AI (phantom-deps): Used via build scripts, not direct import; expected.	ai	2026/07/22
phantom-deps	phantom-dep:@babel/preset-typescript	AI (phantom-deps): Framework-scoped babel preset loaded by convention.	ai	2026/07/22
phantom-deps	phantom-dep:rlp	AI (phantom-deps): rlp is declared as a runtime dep; phantom-dep heuristic fires because it's not directly imported in source but is a transitive/peer need.	ai	2026/04/28
phantom-deps	phantom-dep:@ethereumjs/util	AI (phantom-deps): Same pattern — declared dep used indirectly; stable false positive for this package.	ai	2026/04/28

Versions (showing 41 of 41)

Version	Deps	Published
0.15.2	8 / 3	2025-04-03
0.15.1	8 / 3	2025-04-03
0.15.0	8 / 3	2025-02-25
0.14.1	6 / 3	2024-05-13
0.14.0	6 / 3	2024-05-13
0.13.1	6 / 3	2023-05-31
0.13.0	6 / 3	2023-05-30
0.12.0	6 / 3	2023-05-17
0.11.0	6 / 3	2023-04-25
0.10.0	6 / 3	2023-04-25
0.9.2	6 / 3	2023-03-02
0.9.1	6 / 3	2023-02-22
0.9.0	6 / 3	2023-02-22
0.8.6	6 / 3	2023-02-22
0.8.5	6 / 3	2023-02-13
0.8.4	6 / 3	2023-02-06
0.8.3	6 / 3	2023-02-03
0.8.2	6 / 3	2023-02-03
0.8.1	6 / 3	2023-01-05
0.8.0	6 / 3	2022-12-29
0.7.0	6 / 3	2022-11-01
0.6.1	6 / 3	2022-09-19
0.6.0	6 / 3	2022-07-28
0.5.4	6 / 3	2022-06-20
0.5.3	6 / 3	2022-05-31
0.5.2	6 / 3	2022-05-30
0.5.1	6 / 3	2022-05-30
0.5.0	6 / 3	2022-05-30
0.4.0	6 / 3	2022-04-11
0.3.1	6 / 3	2022-05-20
0.3.0	6 / 3	2022-03-24
0.2.2	6 / 2	2022-02-09
0.2.1	6 / 2	2021-11-10
0.2.0	6 / 2	2021-11-09
0.1.0	6 / 2	2021-10-28
0.0.8	6 / 2	2021-09-27
0.0.7	7 / 2	2021-09-23
0.0.6	9 / 0	2021-09-18
0.0.5	9 / 0	2021-09-18
0.0.4	5 / 0	2021-09-08
0.0.2	2 / 0	2021-08-26

v0.15.1

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.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.

v0.14.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.

v0.13.1

1 finding

LOW No provenance attestation provenance

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

v0.13.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: amalia20220301 → soralit (on 2023-05-30, known maintainer) provenance

This version was published by a different npm account (soralit) than the most recent previously approved version (amalia20220301) on 2023-05-30, but soralit is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.0

1 finding

LOW No provenance attestation provenance

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

v0.10.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: soralit → amalia20220301 (on 2023-04-25, known maintainer) provenance

This version was published by a different npm account (amalia20220301) than the most recent previously approved version (soralit) on 2023-04-25, but amalia20220301 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.9.2

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.6

1 finding

LOW No provenance attestation provenance

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

v0.8.5

1 finding

LOW No provenance attestation provenance

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

v0.8.4

1 finding

LOW No provenance attestation provenance

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

v0.8.3

1 finding

LOW No provenance attestation provenance

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

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: yu_keyst → soralit (on 2022-12-29, known maintainer) provenance

This version was published by a different npm account (soralit) than the most recent previously approved version (yu_keyst) on 2022-12-29, but soralit is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.7.0

2 findings

MEDIUM Publisher changed: soralit → yu_keyst (on 2022-11-01, unremoved on npm for 1359d) provenance

This version was published by a different npm account (yu_keyst) than the most recent previously approved version (soralit) on 2022-11-01. It has since remained available on npm for 1359 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.6.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: amalia20220301 → soralit (on 2022-09-19, known maintainer) provenance

This version was published by a different npm account (soralit) than the most recent previously approved version (amalia20220301) on 2022-09-19, but soralit is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: soralit → amalia20220301 (on 2022-06-20, known maintainer) provenance

This version was published by a different npm account (amalia20220301) than the most recent previously approved version (soralit) on 2022-06-20, but amalia20220301 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.0

1 finding

LOW No provenance attestation provenance

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

v0.0.8

1 finding

LOW No provenance attestation provenance

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

v0.0.7

1 finding

LOW No provenance attestation provenance

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

v0.0.6

1 finding

LOW No provenance attestation provenance

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

v0.0.5

1 finding

LOW No provenance attestation provenance

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

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

v0.0.2

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.