@tradejs/cli
Official CLI for the TradeJS open-source framework: infra setup, backtests, signals, bots, and ML workflows.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/scripts/aiTrain.js | AI (source-diff): esbuild/tsup bundle output with node_modules path comments; not obfuscated. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @tradejs/cli is a scoped CLI package in its own org; Levenshtein proximity to 'joi' is coincidental. | ai | |
| phantom-deps | phantom-dep:@tradejs/base | AI (phantom-deps): Same-org scoped dep; CLI may re-export or use at runtime without direct top-level import. | ai | |
| phantom-deps | phantom-dep:@tradejs/types | AI (phantom-deps): Same-org types package; likely used transitively or via type-only imports not detected by heuristic. | ai | |
| phantom-deps | phantom-dep:@tradejs/indicators | AI (phantom-deps): Same-org scoped dep; CLI orchestrates multiple packages and may use at runtime without direct import. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.0.9 | 16 / 6 | |
| 1.0.8 | 16 / 6 | |
| 1.0.6 | 16 / 6 | |
| 1.0.5 | 16 / 6 | |
| 1.0.4 | 16 / 6 | |
| 1.0.3 | 16 / 6 | |
| 1.0.2 | 16 / 6 | |
| 1.0.1 | 16 / 6 | |
| 1.0.0 | 16 / 6 |
v1.0.9
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.