@tsonic/js
Native Tsonic implementation of JavaScript runtime globals
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @tsonic/js package is a JS runtime globals impl, not a typosquat of 'qs'. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Unrelated to jest; part of the tsonic ecosystem. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Unrelated to pg; part of the tsonic ecosystem. | ai | |
| typosquat | typosquat.levenshtein:rxjs | AI (typosquat): Unrelated to rxjs; part of the tsonic ecosystem. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Unrelated to joi; part of the tsonic ecosystem. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Unrelated to ajv; part of the tsonic ecosystem. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 10.0.54 | 2 / 0 | |
| 10.0.53 | 2 / 0 | |
| 10.0.52 | 2 / 0 | |
| 10.0.51 | 2 / 0 | |
| 10.0.50 | 2 / 0 | |
| 10.0.49 | 2 / 0 | |
| 10.0.48 | 2 / 0 | |
| 10.0.47 | 2 / 0 | |
| 10.0.46 | 2 / 0 | |
| 10.0.45 | 2 / 0 | |
| 10.0.44 | 2 / 0 | |
| 10.0.43 | 2 / 0 | |
| 10.0.42 | 2 / 0 | |
| 10.0.41 | 2 / 0 | |
| 10.0.40 | 2 / 0 | |
| 10.0.39 | 0 / 0 | |
| 10.0.38 | 0 / 0 | |
| 10.0.37 | 0 / 0 | |
| 10.0.35 | 0 / 0 | |
| 10.0.34 | 0 / 0 | |
| 10.0.33 | 0 / 0 | |
| 10.0.32 | 0 / 0 | |
| 10.0.31 | 0 / 0 | |
| 10.0.27 | 0 / 0 | |
| 10.0.26 | 0 / 0 | |
| 10.0.25 | 0 / 0 | |
| 10.0.21 | 0 / 0 | |
| 10.0.20 | 0 / 0 | |
| 10.0.16 | 0 / 0 | |
| 10.0.13 | 0 / 0 | |
| 10.0.12 | 0 / 0 | |
| 10.0.11 | 0 / 0 | |
| 10.0.8 | 0 / 0 | |
| 10.0.7 | 0 / 0 | |
| 10.0.6 | 0 / 0 | |
| 10.0.5 | 0 / 0 | |
| 10.0.1 | 0 / 0 | |
| 0.1.3 | 0 / 0 | |
| 0.1.2 | 0 / 0 |
v10.0.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.49
2 findingsPackage name '@tsonic/js' is 1 edit(s) away from popular package 'qs'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.