← Home

@turnkey/api-key-stamper

npm Repository Homepage
21
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

Turnkeyhttpstamperapi key

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@turnkey/crypto AI (dependencies): Internal sibling dependency within the Turnkey SDK monorepo; expected and benign. ai
dependencies unvetted-dep:@turnkey/encoding AI (dependencies): Internal sibling dependency within the Turnkey SDK monorepo; expected and benign. ai

Versions (showing 21 of 21)

Version Deps Published
0.6.8 4 / 0
0.6.7 4 / 0
0.6.6 4 / 0
0.6.5 4 / 0
0.6.4 4 / 0
0.6.3 4 / 0
0.6.2 4 / 0
0.6.1 4 / 0
0.6.0 4 / 0
0.5.0 3 / 0
0.4.5 3 / 0
0.4.4 3 / 0
0.4.3 3 / 0
0.4.2 3 / 0
0.4.1 3 / 0
0.4.0 3 / 0
0.3.1 0 / 0
0.3.0 0 / 0
0.2.0 0 / 0
0.1.1 0 / 0
0.1.0 0 / 0

v0.6.8

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.

v0.4.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: moe-dev → andrewtk (on 2025-01-16, known maintainer) provenance

This version was published by a different npm account (andrewtk) than the most recent previously approved version (moe-dev) on 2025-01-16, but andrewtk 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.4.3

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: moe-dev → andrewtk (on 2024-10-03, known maintainer) provenance

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

v0.4.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.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.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.1

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. Only ~12% of npm packages have provenance, so this is common but not ideal.