← Home

@orderly.network/perp

npm
32
Versions
MIT
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
bogus-package bogus-package AI (bogus-package): Sparse metadata is a consistent pattern across @orderly.network packages, not a malware indicator. ai
npm-metadata no-description AI (npm-metadata): No-description is a stable pattern for this org's packages. ai
dependencies unvetted-dep:@orderly.network/types AI (dependencies): Same-org scoped dependency; low risk for this package family. ai
dependencies unvetted-dep:@orderly.network/utils AI (dependencies): Same-org scoped dependency; low risk for this package family. ai

Versions (showing 32 of 32)

Version Deps Published
5.1.0 2 / 11
5.0.4 2 / 11
5.0.3 2 / 11
5.0.2 2 / 11
5.0.1 2 / 11
5.0.0 2 / 11
4.12.4 2 / 11
4.12.3 2 / 11
4.12.2 2 / 11
4.12.1 2 / 11
4.12.0 2 / 11
4.11.2 2 / 11
4.11.1 2 / 11
4.11.0 2 / 11
4.10.2 2 / 11
4.10.1 2 / 11
4.10.0 2 / 11
4.9.1 2 / 11
4.9.0 2 / 11
4.8.14 2 / 11
4.8.13 2 / 11
4.8.12 2 / 11
4.8.11 2 / 11
4.8.10 2 / 11
4.8.9 2 / 11
4.8.8 2 / 11
4.8.7 2 / 11
4.8.6 2 / 11
4.8.5 2 / 11
4.8.4 2 / 11
4.8.3 2 / 11
4.8.2 2 / 11

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

1 finding
LOW No provenance attestation provenance

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

v5.0.3

1 finding
LOW No provenance attestation provenance

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

v5.0.2

1 finding
LOW No provenance attestation provenance

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

v4.12.4

1 finding
LOW No provenance attestation provenance

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

v4.12.3

1 finding
LOW No provenance attestation provenance

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

v4.12.2

1 finding
LOW No provenance attestation provenance

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

v4.12.1

1 finding
LOW No provenance attestation provenance

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

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