← Home

@turnkey/crypto

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:bcrypt AI (typosquat): Scoped @turnkey org package; no relation to bcrypt. Levenshtein match is coincidental. ai

Versions (showing 19 of 19)

Version Deps Published
2.10.1 8 / 3
2.10.0 8 / 3
2.9.0 8 / 3
2.8.14 8 / 3
2.8.13 8 / 3
2.8.12 8 / 3
2.8.11 8 / 3
2.8.10 8 / 3
2.8.9 8 / 3
2.8.8 8 / 5
2.8.7 8 / 5
2.8.6 8 / 5
2.8.5 8 / 5
2.4.1 5 / 4
2.4.0 5 / 4
2.3.1 6 / 4
2.3.0 6 / 5
2.2.0 6 / 5
2.1.0 6 / 5

v2.10.1

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.

v2.3.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 2025-02-12, known maintainer) provenance

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

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

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