@balancy/cli
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped gamedev package @balancy/cli; Levenshtein match to 'joi' is coincidental, not a squatting attempt. | ai |
Versions (showing 85 of 85)
| Version | Deps | Published |
|---|---|---|
| 1.6.11 | 4 / 3 | |
| 1.6.10 | 4 / 3 | |
| 1.6.9 | 4 / 3 | |
| 1.6.8 | 4 / 3 | |
| 1.6.7 | 4 / 3 | |
| 1.6.6 | 4 / 3 | |
| 1.6.5 | 4 / 3 | |
| 1.4.5 | 4 / 3 | |
| 1.4.4 | 4 / 3 | |
| 1.4.3 | 4 / 3 | |
| 1.3.6 | 4 / 3 | |
| 1.3.5 | 4 / 3 | |
| 1.3.4 | 4 / 3 | |
| 1.3.3 | 4 / 3 | |
| 1.3.2 | 4 / 3 | |
| 1.2.6 | 4 / 3 | |
| 1.2.5 | 4 / 3 | |
| 1.2.4 | 4 / 3 | |
| 1.2.3 | 4 / 3 | |
| 1.2.2 | 4 / 3 | |
| 1.2.1 | 4 / 3 | |
| 1.2.0 | 4 / 3 | |
| 1.1.47 | 4 / 3 | |
| 1.1.37 | 4 / 3 | |
| 1.1.36 | 4 / 3 | |
| 1.1.34 | 4 / 3 | |
| 1.1.33 | 4 / 3 | |
| 1.1.31 | 4 / 3 | |
| 1.1.29 | 4 / 3 | |
| 1.1.28 | 4 / 3 | |
| 1.1.27 | 4 / 3 | |
| 1.1.22 | 4 / 3 | |
| 1.1.20 | 4 / 3 | |
| 1.1.19 | 4 / 3 | |
| 1.1.18 | 4 / 3 | |
| 1.1.17 | 4 / 3 | |
| 1.1.16 | 4 / 3 | |
| 1.1.15 | 4 / 3 | |
| 1.1.12 | 4 / 3 | |
| 1.1.11 | 4 / 3 | |
| 1.1.10 | 4 / 3 | |
| 1.1.8 | 4 / 3 | |
| 1.1.7 | 4 / 3 | |
| 1.1.6 | 4 / 3 | |
| 1.1.5 | 4 / 3 | |
| 1.0.46 | 4 / 3 | |
| 1.0.45 | 4 / 3 | |
| 1.0.44 | 4 / 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.30 | 4 / 3 | |
| 1.0.29 | 4 / 3 | |
| 1.0.28 | 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.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.8 | 4 / 3 | |
| 1.0.7 | 4 / 3 | |
| 1.0.6 | 4 / 3 | |
| 1.0.5 | 4 / 3 | |
| 1.0.3 | 4 / 3 | |
| 1.0.2 | 4 / 3 | |
| 1.0.1 | 4 / 3 | |
| 1.0.0 | 4 / 3 |
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.