@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, 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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): open is a legit browser-launch dep for this CLI's dashboard; benign. | ai | |
| dependencies | unvetted-dep:ccxt | AI (dependencies): ccxt is the canonical crypto exchange library; expected core dep for a backtesting CLI. | ai | |
| 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:di-scoped | AI (phantom-deps): Referenced in config files per finding; stable false positive for this package. | 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 | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @backtest-kit/cli is a scoped crypto backtesting CLI; no relation to joi validation library. | ai | |
| semgrep | semgrep:toplevel-fetch | AI (semgrep): fetch_docs.mjs is a template script that fetches README docs for listed libraries; not exfiltration. | ai |
Versions (showing 72 of 72)
| Version | Deps | Published |
|---|---|---|
| 17.0.0 | 15 / 27 | |
| 16.6.0 | 15 / 27 | |
| 16.5.0 | 15 / 27 | |
| 16.4.0 | 15 / 27 | |
| 16.3.0 | 15 / 27 | |
| 16.2.0 | 15 / 27 | |
| 16.1.0 | 15 / 27 | |
| 16.0.0 | 15 / 27 | |
| 15.5.0 | 15 / 27 | |
| 15.4.0 | 15 / 27 | |
| 15.3.0 | 15 / 27 | |
| 15.2.0 | 15 / 27 | |
| 15.1.0 | 15 / 27 | |
| 15.0.0 | 15 / 27 | |
| 14.1.0 | 15 / 27 | |
| 14.0.0 | 15 / 27 | |
| 13.6.0 | 15 / 27 | |
| 13.5.0 | 15 / 27 | |
| 13.4.0 | 16 / 25 | |
| 13.3.0 | 16 / 25 | |
| 13.2.0 | 16 / 25 | |
| 12.8.0 | 16 / 25 | |
| 12.7.0 | 16 / 25 | |
| 12.6.0 | 16 / 25 | |
| 12.5.0 | 16 / 25 | |
| 12.4.0 | 16 / 25 | |
| 12.3.0 | 16 / 25 | |
| 12.2.0 | 16 / 25 | |
| 12.1.0 | 16 / 25 | |
| 12.0.0 | 16 / 25 | |
| 11.9.0 | 16 / 25 | |
| 11.8.0 | 16 / 25 | |
| 11.7.0 | 16 / 25 | |
| 11.6.0 | 16 / 25 | |
| 11.5.2 | 16 / 25 | |
| 11.5.0 | 16 / 25 | |
| 11.4.0 | 16 / 25 | |
| 11.3.0 | 16 / 25 | |
| 11.2.0 | 16 / 25 | |
| 11.0.0 | 16 / 25 | |
| 10.2.0 | 16 / 25 | |
| 10.1.0 | 16 / 25 | |
| 9.8.4 | 16 / 25 | |
| 9.8.3 | 16 / 25 | |
| 9.8.2 | 16 / 25 | |
| 9.8.1 | 16 / 25 | |
| 9.8.0 | 16 / 25 | |
| 9.7.0 | 16 / 25 | |
| 9.6.0 | 16 / 25 | |
| 9.5.0 | 16 / 25 | |
| 9.4.0 | 16 / 25 | |
| 9.3.0 | 16 / 25 | |
| 9.2.0 | 16 / 25 | |
| 9.1.1 | 16 / 25 | |
| 9.1.0 | 16 / 25 | |
| 8.5.0 | 16 / 25 | |
| 8.4.3 | 16 / 25 | |
| 8.4.1 | 16 / 25 | |
| 8.0.0 | 16 / 25 | |
| 6.0.0 | 15 / 25 | |
| 5.11.1 | 15 / 25 | |
| 3.3.4 | 15 / 19 | |
| 3.3.2 | 15 / 18 | |
| 3.3.0 | 15 / 18 | |
| 3.2.0 | 15 / 18 | |
| 0.0.7 | 15 / 18 | |
| 0.0.6 | 15 / 18 | |
| 0.0.5 | 15 / 18 | |
| 0.0.4 | 15 / 17 | |
| 0.0.3 | 15 / 17 | |
| 0.0.2 | 15 / 17 | |
| 0.0.1 | 15 / 17 |
v17.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.