← Home

@tonconnect/ui

npm Repository Homepage
20
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

thekibait-tonstudio-io

Keywords

TONWalletton-connecttonconnectConnectTonkeepersdkUI

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Established publisher with clean history; missing gitHead alone is insufficient to block a minor patch release with no other risk signals. ai
typosquat typosquat.levenshtein:uuid AI (typosquat): Scoped package @tonconnect/ui; Levenshtein match to uuid is a false positive. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Scoped package @tonconnect/ui; Levenshtein match to pg is a false positive. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @tonconnect/ui; Levenshtein match to qs is a false positive. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped package @tonconnect/ui; Levenshtein match to joi is a false positive. ai
typosquat typosquat.levenshtein:yup AI (typosquat): Scoped package @tonconnect/ui; Levenshtein match to yup is a false positive. ai

Versions (showing 20 of 20)

Version Deps Published
3.0.0 5 / 19
2.4.4 5 / 19
2.4.3 5 / 19
2.4.2 5 / 19
2.4.1 5 / 19
2.4.0 5 / 19
2.3.1 5 / 17
2.3.0 5 / 17
2.2.0 5 / 18
2.1.0 5 / 18
2.0.12 5 / 18
2.0.11 5 / 18
2.0.10 5 / 18
2.0.9 4 / 19
2.0.8 4 / 19
2.0.7 4 / 19
2.0.6 4 / 19
2.0.5 4 / 19
2.0.4 4 / 19
2.0.3 4 / 19

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

1 finding
LOW No provenance attestation provenance

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

v2.0.11

1 finding
LOW No provenance attestation provenance

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

v2.0.10

1 finding
LOW No provenance attestation provenance

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

v2.0.9

1 finding
LOW No provenance attestation provenance

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

v2.0.8

1 finding
LOW No provenance attestation provenance

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

v2.0.7

1 finding
LOW No provenance attestation provenance

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

v2.0.6

1 finding
LOW No provenance attestation provenance

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

v2.0.5

1 finding
LOW No provenance attestation provenance

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

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

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