@trading-boy/cli
Trading Boy CLI — remote trading intelligence for traders and AI agents.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Minor release with benign script-only diff; missing gitHead is a CI environment change, not a supply-chain indicator for this package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped trading CLI package; name similarity to 'joi' is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:open | AI (phantom-deps): Deps bundled via esbuild into cli.bundle.js; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): Deps bundled via esbuild into cli.bundle.js; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:qrcode-terminal | AI (phantom-deps): Deps bundled via esbuild into cli.bundle.js; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@inquirer/prompts | AI (phantom-deps): Deps bundled via esbuild into cli.bundle.js; phantom-dep heuristic is a stable false positive here. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 7 / 3 | |
| 2.0.1 | 7 / 3 | |
| 2.0.0 | 7 / 3 | |
| 1.12.0 | 7 / 3 | |
| 1.11.0 | 7 / 3 | |
| 1.10.0 | 7 / 3 | |
| 1.9.2 | 7 / 3 | |
| 1.9.0 | 7 / 3 | |
| 1.8.0 | 7 / 3 | |
| 1.7.0 | 7 / 3 | |
| 1.6.1 | 7 / 3 | |
| 1.6.0 | 7 / 3 | |
| 1.5.1 | 7 / 3 | |
| 1.5.0 | 7 / 3 | |
| 1.4.1 | 7 / 3 | |
| 1.4.0 | 7 / 3 | |
| 1.3.0 | 7 / 3 | |
| 1.2.20 | 7 / 3 | |
| 1.2.19 | 7 / 3 | |
| 1.2.18 | 7 / 3 | |
| 1.2.17 | 7 / 3 | |
| 1.2.16 | 7 / 3 | |
| 1.2.15 | 7 / 3 | |
| 1.2.14 | 7 / 3 | |
| 1.2.13 | 7 / 3 | |
| 1.2.12 | 7 / 3 | |
| 1.2.11 | 7 / 3 |
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.