← Home

@tradejs/base

npm Repository

Default preset for the TradeJS open-source framework, wiring the built-in strategies, indicators, and connectors.

8
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

tradejs-dev

Keywords

tradejstradingbacktestingpresetstarterplugins

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@tradejs/connectors AI (phantom-deps): Preset package re-exports connectors; stable false positive. ai
phantom-deps phantom-dep:@tradejs/indicators AI (phantom-deps): Preset package re-exports indicators; stable false positive. ai
phantom-deps phantom-dep:@tradejs/strategies AI (phantom-deps): Preset package re-exports strategies; stable false positive. ai

Versions (showing 8 of 8)

Version Deps Published
1.0.9 5 / 2
1.0.8 5 / 2
1.0.6 4 / 2
1.0.5 4 / 2
1.0.4 4 / 2
1.0.3 4 / 2
1.0.2 4 / 2
1.0.0 4 / 2

v1.0.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.