← Home

@cetusprotocol/cetus-sui-clmm-sdk

npm Repository
21
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

cetusprotocol

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:cors AI (phantom-deps): SDK declares cors as runtime dep; phantom-dep heuristic fires but it's used in the package's network layer. ai
phantom-deps phantom-dep:dotenv AI (phantom-deps): dotenv is in both devDependencies and dependencies; phantom-dep is a false positive here. ai
phantom-deps phantom-dep:js-sha3 AI (phantom-deps): Crypto utility declared as runtime dep; phantom-dep heuristic is a false positive for this SDK. ai
phantom-deps phantom-dep:tweetnacl AI (phantom-deps): Crypto utility declared as runtime dep; phantom-dep heuristic is a false positive for this SDK. ai
phantom-deps phantom-dep:superstruct AI (phantom-deps): Validation library declared as runtime dep; phantom-dep heuristic is a false positive for this SDK. ai
phantom-deps phantom-dep:tiny-invariant AI (phantom-deps): Utility declared as runtime dep; phantom-dep heuristic is a false positive for this SDK. ai
phantom-deps phantom-dep:@suchipi/femver AI (phantom-deps): Version utility declared as runtime dep; phantom-dep heuristic is a false positive for this SDK. ai
phantom-deps phantom-dep:isomorphic-fetch AI (phantom-deps): Fetch polyfill declared as runtime dep; phantom-dep heuristic is a false positive for this SDK. ai
phantom-deps phantom-dep:@types/bn.js AI (phantom-deps): Type package used by bn.js; framework-scoped, stable false positive for this package. ai

Versions (showing 21 of 21)

Version Deps Published
5.4.0 15 / 25
5.3.4 15 / 25
5.3.3 15 / 25
5.3.2 15 / 25
5.3.1 15 / 25
5.3.0 14 / 24
5.2.0 14 / 24
5.1.11 14 / 24
5.1.10 14 / 24
5.1.9 14 / 24
5.1.8 14 / 24
5.1.7 14 / 24
5.1.6 14 / 24
5.1.5 14 / 24
5.1.4 14 / 25
5.1.3 14 / 25
5.1.2 14 / 25
5.1.1 14 / 25
5.1.0 14 / 25
5.0.1 14 / 25
5.0.0 14 / 25

v5.3.4

1 finding
LOW No provenance attestation provenance

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

v5.3.3

1 finding
LOW No provenance attestation provenance

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

v5.3.2

1 finding
LOW No provenance attestation provenance

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

v5.3.1

1 finding
LOW No provenance attestation provenance

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

v5.3.0

1 finding
LOW No provenance attestation provenance

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

v5.2.0

1 finding
LOW No provenance attestation provenance

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

v5.1.11

1 finding
LOW No provenance attestation provenance

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

v5.1.10

1 finding
LOW No provenance attestation provenance

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

v5.1.9

1 finding
LOW No provenance attestation provenance

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

v5.1.8

1 finding
LOW No provenance attestation provenance

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

v5.1.7

1 finding
LOW No provenance attestation provenance

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

v5.1.6

1 finding
LOW No provenance attestation provenance

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

v5.1.5

1 finding
LOW No provenance attestation provenance

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

v5.1.4

1 finding
LOW No provenance attestation provenance

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

v5.1.3

1 finding
LOW No provenance attestation provenance

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

v5.1.2

1 finding
LOW No provenance attestation provenance

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

v5.1.1

1 finding
LOW No provenance attestation provenance

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

v5.1.0

1 finding
LOW No provenance attestation provenance

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

v5.0.1

1 finding
LOW No provenance attestation provenance

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

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