← Home

@turnkey/iframe-stamper

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

Turnkeyhttpstamper

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Turnkey SDK migrated to GitHub Actions CI publishing with SLSA attestation; publisher change is intentional. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with org-wide shift to automated CI publishing; not indicative of takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by CI-automated publish with SLSA provenance; low-risk pattern for this package. ai

Versions (showing 14 of 14)

Version Deps Published
2.11.1 0 / 0
2.11.0 0 / 0
2.10.0 0 / 0
2.9.0 0 / 0
2.8.0 0 / 0
2.7.1 0 / 0
2.7.0 0 / 0
2.6.0 0 / 0
2.5.0 0 / 0
2.4.0 0 / 0
2.3.0 0 / 0
2.2.0 0 / 0
2.1.0 0 / 0
2.0.0 0 / 0

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

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

v2.3.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: andrewtk → moe-dev (on 2025-03-14, known maintainer) provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.0

1 finding
LOW No provenance attestation provenance

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

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