@backtest-kit/cli
Zero-boilerplate CLI runner for backtest-kit strategies. Run backtests, paper trading, and live bots with candle cache warming, web dashboard, and Telegram notifications — no setup code required.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:telegraf | AI (dependencies): telegraf is the standard Telegram bot framework; expected for a CLI with Telegram notifications. | ai | |
| phantom-deps | phantom-dep:markdownlint | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:get-moment-stamp | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:ccxt | AI (dependencies): ccxt is the canonical crypto exchange library; expected core dep for a backtesting CLI. | ai | |
| phantom-deps | phantom-dep:di-scoped | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): fetch_docs.mjs is a template script that fetches README docs for listed libraries; not exfiltration. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @backtest-kit/cli is a scoped crypto backtesting CLI; no relation to joi validation library. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 9.8.3 | 16 / 25 | |
| 6.0.0 | 15 / 25 | |
| 5.11.1 | 15 / 25 | |
| 0.0.2 | 15 / 17 |
v9.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.