@backtest-kit/signals
Technical analysis and trading signal generation library for AI-powered trading systems. Computes 50+ indicators across 4 timeframes and generates markdown reports for LLM consumption.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:di-kit | AI (phantom-deps): Declared dependency; used in config-driven context, not direct imports. | ai | |
| phantom-deps | phantom-dep:functools-kit | AI (phantom-deps): Declared dependency; used in config-driven context, not direct imports. | ai | |
| phantom-deps | phantom-dep:trading-signals | AI (phantom-deps): Declared dependency; used in config-driven context, not direct imports. | ai | |
| phantom-deps | phantom-dep:di-scoped | AI (phantom-deps): Declared dep used via config/re-export pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:get-moment-stamp | AI (phantom-deps): Declared dep used via config/re-export pattern; stable false positive for this package. | ai |
Versions (showing 51 of 98)
| Version | Deps | Published |
|---|---|---|
| 11.6.0 | 6 / 12 | |
| 11.5.2 | 6 / 12 | |
| 11.5.0 | 6 / 12 | |
| 11.4.0 | 6 / 12 | |
| 11.3.0 | 6 / 12 | |
| 11.2.0 | 6 / 12 | |
| 11.0.0 | 6 / 12 | |
| 10.2.0 | 6 / 12 | |
| 10.1.0 | 6 / 12 | |
| 9.8.4 | 6 / 12 | |
| 9.8.3 | 6 / 12 | |
| 9.8.2 | 6 / 12 | |
| 9.8.1 | 6 / 12 | |
| 9.8.0 | 6 / 12 | |
| 9.7.0 | 6 / 12 | |
| 9.6.0 | 6 / 12 | |
| 9.5.0 | 6 / 12 | |
| 9.4.0 | 6 / 12 | |
| 9.3.0 | 6 / 12 | |
| 9.2.0 | 6 / 12 | |
| 9.1.0 | 6 / 12 | |
| 9.0.0 | 6 / 12 | |
| 8.5.0 | 6 / 12 | |
| 8.4.0 | 6 / 12 | |
| 8.3.0 | 6 / 12 | |
| 8.2.0 | 6 / 12 | |
| 8.1.0 | 6 / 12 | |
| 8.0.0 | 6 / 12 | |
| 7.8.0 | 6 / 12 | |
| 7.7.0 | 6 / 12 | |
| 7.6.0 | 6 / 12 | |
| 7.5.0 | 6 / 12 | |
| 7.4.0 | 6 / 12 | |
| 7.3.0 | 6 / 12 | |
| 7.2.0 | 6 / 12 | |
| 7.1.0 | 6 / 12 | |
| 7.0.0 | 6 / 12 | |
| 6.16.0 | 6 / 12 | |
| 6.15.0 | 6 / 12 | |
| 6.14.0 | 6 / 12 | |
| 6.13.0 | 6 / 12 | |
| 6.12.0 | 6 / 12 | |
| 6.11.0 | 6 / 12 | |
| 6.10.0 | 6 / 12 | |
| 6.9.0 | 6 / 12 | |
| 6.8.1 | 6 / 12 | |
| 6.7.0 | 6 / 12 | |
| 6.5.0 | 6 / 12 | |
| 6.4.0 | 6 / 12 | |
| 6.2.0 | 6 / 12 | |
| 6.1.1 | 6 / 12 |
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.3
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
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.
v7.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.