← Home

aftermath-ts-sdk

npm Repository Homepage
7
Versions
—
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

collin-aftermath

Keywords

aftermathaftermath financesuiaftermath sdkaftermath finance sdkaftermath typescript sdkaftermath finance typescript sdk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:node-fetch AI (phantom-deps): node-fetch is a declared runtime dep in an SDK; phantom-dep false positive likely due to indirect/conditional usage across SDK modules. ai
phantom-deps phantom-dep:priority-queue-typescript AI (phantom-deps): priority-queue-typescript is a declared runtime dep; phantom-dep false positive likely due to indirect usage in specific SDK modules. ai
provenance no-provenance AI (provenance): Established SDK with 622 versions; lack of provenance is consistent across all prior versions and is not a disqualifier for this package. ai

Versions (showing 7 of 7)

Version Deps Published
2.1.0 1 / 11
2.0.1 1 / 11
2.0.0 1 / 11
1.3.29 4 / 10
1.3.28 4 / 10
1.3.25 4 / 10
1.3.24 4 / 10

v2.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.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.