@ton/walletkit
5
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
tsivarevtruecarryklpxdanil42russiatolk-vmton-ciit-tonstudio-ioalblanccg3co
Keywords
tonwalletconnecttonconnect
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:@tonconnect/bridge-sdk | AI (npm-metadata): Points to a pinned versioned release tarball from the official ton-connect GitHub org; not a mutable URL. | ai | |
| dependencies | unvetted-dep:@tonconnect/bridge-sdk | AI (dependencies): @tonconnect/bridge-sdk is a first-party TON Connect ecosystem dependency; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 7 / 23 | |
| 0.0.11 | 7 / 24 | |
| 0.0.8 | 7 / 24 | |
| 0.0.5 | 7 / 27 | |
| 0.0.1 | 12 / 19 |
v0.0.5
2 findings
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.
INFO
Publisher changed: ikardanov → GitHub Actions (on 2026-01-19, now via trusted publisher with provenance)
provenance
This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (ikardanov) on 2026-01-19, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.