← Home

@orderly.network/vaults

npm

This package provides a robust and feature-rich HTTP client for making API requests. The optimized request module includes advanced features like retry logic, timeout handling, request/response interceptors, and comprehensive error handling.

32
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

orderly.productkai.jiangstognievleo_orderlygoogolev

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:date-fns AI (phantom-deps): date-fns is a declared runtime dep used transitively; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:@orderly.network/react-app AI (phantom-deps): Same-org scope dependency; phantom-dep heuristic unreliable for monorepo re-exports. ai

Versions (showing 32 of 32)

Version Deps Published
3.1.0 11 / 12
3.0.4 11 / 12
3.0.3 11 / 12
3.0.2 11 / 12
3.0.1 11 / 12
3.0.0 11 / 12
2.12.4 11 / 12
2.12.3 11 / 12
2.12.2 11 / 12
2.12.1 11 / 12
2.12.0 11 / 12
2.11.2 11 / 12
2.11.1 11 / 12
2.11.0 11 / 12
2.10.2 11 / 12
2.10.1 11 / 12
2.10.0 11 / 12
2.9.1 11 / 12
2.9.0 11 / 12
2.8.14 11 / 12
2.8.13 11 / 12
2.8.12 11 / 12
2.8.11 11 / 12
2.8.10 11 / 12
2.8.9 11 / 12
2.8.8 11 / 12
2.8.7 11 / 12
2.8.6 11 / 12
2.8.5 11 / 12
2.8.4 11 / 12
2.8.3 11 / 12
2.8.2 11 / 12

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.4

1 finding
LOW No provenance attestation provenance

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

v3.0.3

1 finding
LOW No provenance attestation provenance

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

v3.0.2

1 finding
LOW No provenance attestation provenance

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

v2.12.4

1 finding
LOW No provenance attestation provenance

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

v2.12.3

1 finding
LOW No provenance attestation provenance

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

v2.12.2

1 finding
LOW No provenance attestation provenance

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

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

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

v2.11.0

1 finding
LOW No provenance attestation provenance

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

v2.8.13

1 finding
LOW No provenance attestation provenance

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

v2.8.12

1 finding
LOW No provenance attestation provenance

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

v2.8.11

1 finding
LOW No provenance attestation provenance

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

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