@orderly.network/ui-order-entry
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ramda | AI (phantom-deps): ramda is a declared runtime dep; phantom-dep heuristic fires but it's used in the build/bundle. | ai | |
| phantom-deps | phantom-dep:@orderly.network/ui-scaffold | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic is a stable false positive for this monorepo package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established monorepo component; missing metadata is a known pattern for @orderly.network packages, not a spam indicator. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 12 / 9 | |
| 3.0.4 | 12 / 9 | |
| 3.0.3 | 12 / 9 | |
| 3.0.2 | 12 / 9 | |
| 3.0.1 | 12 / 9 | |
| 3.0.0 | 12 / 9 | |
| 2.12.4 | 12 / 9 | |
| 2.12.3 | 12 / 9 | |
| 2.12.2 | 12 / 9 | |
| 2.12.1 | 12 / 9 | |
| 2.12.0 | 12 / 9 | |
| 2.11.2 | 12 / 9 | |
| 2.11.1 | 12 / 9 | |
| 2.11.0 | 12 / 9 | |
| 2.10.2 | 12 / 9 | |
| 2.10.1 | 12 / 9 | |
| 2.10.0 | 12 / 9 | |
| 2.9.1 | 12 / 9 | |
| 2.9.0 | 12 / 9 | |
| 2.8.14 | 12 / 9 | |
| 2.8.13 | 12 / 9 | |
| 2.8.12 | 12 / 9 | |
| 2.8.11 | 12 / 9 | |
| 2.8.10 | 12 / 9 | |
| 2.8.9 | 12 / 9 | |
| 2.8.8 | 12 / 9 | |
| 2.8.7 | 12 / 9 | |
| 2.8.6 | 12 / 9 | |
| 2.8.5 | 12 / 9 | |
| 2.8.4 | 12 / 9 | |
| 2.8.3 | 12 / 9 | |
| 2.8.2 | 12 / 9 |
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.