← Home

@turnkey/solana

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

TurnkeySolanaweb3jsweb3

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): @turnkey/core is a first-party Turnkey SDK package from the same monorepo; not a suspicious third-party dep. ai
maintainer-change maintainer-removed AI (maintainer-change): Maintainer list change reflects org-level CI migration, not a takeover. ai
provenance publisher-changed AI (provenance): Publisher changed to GitHub Actions with SLSA provenance; consistent with CI/CD automation for the tkhq/sdk monorepo. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy reflects SDK versioning cadence; SLSA attestation and org continuity confirm legitimate publish. ai

Versions (showing 77 of 77)

Version Deps Published
1.1.32 5 / 3
1.1.31 5 / 3
1.1.30 5 / 3
1.1.29 5 / 3
1.1.28 5 / 3
1.1.27 5 / 3
1.1.26 5 / 3
1.1.25 5 / 3
1.1.24 5 / 3
1.1.23 5 / 3
1.1.22 5 / 3
1.1.21 5 / 3
1.1.20 5 / 3
1.1.19 5 / 3
1.1.18 5 / 3
1.1.17 5 / 3
1.1.16 5 / 3
1.1.15 5 / 3
1.1.14 5 / 3
1.1.13 5 / 3
1.1.12 5 / 3
1.1.11 5 / 3
1.1.10 5 / 3
1.1.9 5 / 3
1.1.8 5 / 3
1.1.7 5 / 3
1.1.6 5 / 3
1.1.5 5 / 3
1.1.4 5 / 3
1.1.3 5 / 3
1.1.2 5 / 3
1.1.1 5 / 3
1.1.0 5 / 3
1.0.43 4 / 3
1.0.42 4 / 3
1.0.41 4 / 3
1.0.40 4 / 3
1.0.39 4 / 3
1.0.38 4 / 3
1.0.37 4 / 3
1.0.36 4 / 3
1.0.35 4 / 3
1.0.34 4 / 3
1.0.33 4 / 3
1.0.32 4 / 3
1.0.31 4 / 3
1.0.30 4 / 3
1.0.29 4 / 3
1.0.28 4 / 3
1.0.27 4 / 3
1.0.26 4 / 3
1.0.25 4 / 3
1.0.24 4 / 3
1.0.23 4 / 3
1.0.22 4 / 3
1.0.21 4 / 3
1.0.20 4 / 3
1.0.19 4 / 3
1.0.18 4 / 3
1.0.17 4 / 3
1.0.16 4 / 3
1.0.15 4 / 3
1.0.14 4 / 3
1.0.13 4 / 3
1.0.12 4 / 3
1.0.11 4 / 3
1.0.10 4 / 3
1.0.9 4 / 3
1.0.8 4 / 3
1.0.7 4 / 3
1.0.6 4 / 3
1.0.5 4 / 3
1.0.4 4 / 3
1.0.3 4 / 3
1.0.2 4 / 3
1.0.1 4 / 3
1.0.0 4 / 3

v1.1.32

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

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.

v1.0.22

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.

v1.0.21

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.

v1.0.20

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.

v1.0.19

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.

v1.0.18

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.

v1.0.17

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.

v1.0.16

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.

v1.0.15

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.

v1.0.14

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.

v1.0.13

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.

v1.0.12

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.

v1.0.11

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.

v1.0.10

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.

v1.0.9

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.

v1.0.8

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.

v1.0.7

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.

v1.0.6

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.

v1.0.5

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.

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

v1.0.3

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.

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

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

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.