← Home

@orderly.network/net

npm
32
Versions
ISC
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
typosquat typosquat.levenshtein:next AI (typosquat): Scoped package @orderly.network/net; 'net' is a legitimate sub-package name, not a typosquat of 'next'. ai
typosquat typosquat.levenshtein:nuxt AI (typosquat): Same reasoning; scoped org package, not impersonating nuxt. ai
typosquat typosquat.levenshtein:jest AI (typosquat): Same reasoning; scoped org package, not impersonating jest. ai
typosquat typosquat.levenshtein:got AI (typosquat): Same reasoning; scoped org package, not impersonating got. ai
typosquat typosquat.levenshtein:knex AI (typosquat): Same reasoning; scoped org package, not impersonating knex. ai
bogus-package bogus-package AI (bogus-package): Monorepo sub-package; sparse metadata is common in internal org packages with 418 published versions. ai

Versions (showing 32 of 32)

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

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. Consider requesting the maintainer enable provenance via CI/CD.

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.