@torba/cli
Command-line interface for building and launching Minecraft client installations from declarative manifests.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@torba/minecraft | AI (phantom-deps): @torba/minecraft is declared as a runtime dependency in package.json; phantom-dep false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @torba/cli is a scoped Minecraft tooling CLI, not a typosquat of joi; Levenshtein match is coincidental. | ai | |
| phantom-deps | phantom-dep:@torba/rules | AI (phantom-deps): @torba/rules is a same-org dependency; likely used transitively or at runtime via CLI dispatch, not a phantom dep concern. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.14 | 5 / 0 | |
| 1.0.9 | 7 / 1 | |
| 1.0.8 | 7 / 1 | |
| 1.0.7 | 7 / 1 | |
| 1.0.5 | 7 / 1 | |
| 1.0.3 | 7 / 1 | |
| 1.0.2 | 7 / 1 | |
| 1.0.0 | 5 / 0 |
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.