← Home

@turnkey/wallet-stamper

npm Repository Homepage
31
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

andrewtkr-n-ojack-kearney-tkhq

Keywords

Turnkeyhttpstamperwallet authentication

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Turnkey migrated to GitHub Actions CI/CD publishing with SLSA attestation; expected for this org's monorepo. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer list change reflects org-wide shift to automated publishing; consistent with SLSA-attested CI/CD workflow. ai

Versions (showing 31 of 31)

Version Deps Published
1.1.20 2 / 7
1.1.19 2 / 7
1.1.18 2 / 7
1.1.17 2 / 7
1.1.16 2 / 7
1.1.15 2 / 7
1.1.14 2 / 7
1.1.13 2 / 7
1.1.12 2 / 7
1.1.11 2 / 7
1.1.10 2 / 7
1.1.9 2 / 7
1.1.8 2 / 7
1.1.7 2 / 7
1.1.6 2 / 7
1.1.5 3 / 7
1.1.4 3 / 7
1.1.3 3 / 7
1.1.2 3 / 7
1.1.1 3 / 7
1.1.0 2 / 7
1.0.9 3 / 7
1.0.8 3 / 7
1.0.7 3 / 7
1.0.6 3 / 7
1.0.5 3 / 7
1.0.4 3 / 7
1.0.3 3 / 7
1.0.2 3 / 6
1.0.1 3 / 6
1.0.0 2 / 6

v1.1.20

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

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: tdawson → moe-dev (on 2024-12-17, known maintainer) provenance

This version was published by a different npm account (moe-dev) than the most recent previously approved version (tdawson) on 2024-12-17, but moe-dev 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.

v1.0.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: tdawson → moe-dev (on 2024-12-09, known maintainer) provenance

This version was published by a different npm account (moe-dev) than the most recent previously approved version (tdawson) on 2024-12-09, but moe-dev 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.

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