← Home

@cetusprotocol/aggregator-sdk

npm
31
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

cetusprotocol

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@babel/preset-typescript AI (phantom-deps): Babel preset; loaded by convention in build config. ai
phantom-deps phantom-dep:@jest/globals AI (phantom-deps): Jest globals; loaded by convention in test config. ai
phantom-deps phantom-dep:@babel/preset-env AI (phantom-deps): Babel preset; loaded by convention in build config. ai
phantom-deps phantom-dep:jest AI (phantom-deps): Test framework; loaded by convention in test scripts. ai
phantom-deps phantom-dep:ts-jest AI (phantom-deps): Jest TypeScript preset; loaded by convention in test config. ai
phantom-deps phantom-dep:babel-jest AI (phantom-deps): Jest Babel preset; loaded by convention in test config. ai
phantom-deps phantom-dep:typescript AI (phantom-deps): Peer dependency; loaded by convention in build/test. ai
phantom-deps phantom-dep:@babel/core AI (phantom-deps): Framework-scoped; loaded by convention in build config. ai
phantom-deps phantom-dep:@types/jest AI (phantom-deps): Type definitions; loaded by convention in test config. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): Type definitions; loaded by convention in build. ai
phantom-deps phantom-dep:bip39 AI (phantom-deps): bip39 is declared in dependencies and legitimately used; phantom-dep finding is a false positive for this SDK package. ai
phantom-deps phantom-dep:dotenv AI (phantom-deps): dotenv is declared in dependencies and legitimately used; phantom-dep finding is a false positive for this SDK package. ai
phantom-deps phantom-dep:node-fetch AI (phantom-deps): node-fetch is declared in dependencies and legitimately used; phantom-dep finding is a false positive for this SDK package. ai
dependencies unvetted-dep:@pythnetwork/hermes-client AI (dependencies): @pythnetwork/hermes-client is the official Pyth Network price oracle client; expected dependency for a DeFi aggregator needing price feeds. ai
dependencies unvetted-dep:@mysten/sui AI (dependencies): @mysten/sui is the official Sui blockchain SDK from Mysten Labs; expected and legitimate dependency for a Sui DeFi aggregator SDK. ai

Versions (showing 31 of 31)

Version Deps Published
1.5.6 6 / 9
1.5.5 6 / 9
1.5.4 6 / 9
1.5.3 6 / 9
1.5.2 6 / 9
1.5.1 6 / 9
1.5.0 6 / 9
1.4.9 6 / 9
1.4.8 6 / 9
1.4.7 6 / 9
1.4.6 6 / 9
1.4.5 6 / 9
1.4.4 6 / 16
1.4.3 6 / 16
1.4.2 6 / 16
1.4.1 6 / 16
1.4.0 6 / 16
1.3.0 6 / 16
1.2.1 6 / 16
1.2.0 6 / 16
1.1.6 6 / 16
1.1.5 16 / 6
1.1.4 16 / 6
1.1.3 16 / 6
1.1.2 16 / 6
1.1.1 16 / 6
1.1.0 16 / 6
1.0.3 16 / 6
1.0.2 16 / 6
1.0.1 16 / 6
1.0.0 16 / 6

v1.5.6

1 finding
LOW No provenance attestation provenance

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

v1.5.5

1 finding
LOW No provenance attestation provenance

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

v1.5.4

1 finding
LOW No provenance attestation provenance

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

v1.5.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.5.1

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

v1.4.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.4.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.4.7

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.4.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.4.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.4.1

1 finding
LOW No provenance attestation provenance

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

v1.4.0

1 finding
LOW No provenance attestation provenance

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

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.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.

v1.1.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.1.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.1.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.1.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.1.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.1.1

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

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

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.