@orderly.network/trading-rewards
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo sub-package; missing description/repo/keywords is normal for internal packages in this org. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across @orderly.network monorepo packages; not a spam indicator here. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): date-fns is a declared dependency; phantom-dep heuristic fires on config-only references, stable false positive for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 10 / 9 | |
| 3.0.4 | 10 / 9 | |
| 3.0.3 | 10 / 9 | |
| 3.0.2 | 10 / 9 | |
| 3.0.1 | 10 / 9 | |
| 3.0.0 | 10 / 9 | |
| 2.12.4 | 10 / 9 | |
| 2.12.3 | 10 / 9 | |
| 2.12.2 | 10 / 9 | |
| 2.12.1 | 10 / 9 | |
| 2.12.0 | 10 / 9 | |
| 2.11.2 | 10 / 9 | |
| 2.11.1 | 10 / 9 | |
| 2.11.0 | 10 / 9 | |
| 2.10.2 | 10 / 9 | |
| 2.10.1 | 10 / 9 | |
| 2.10.0 | 10 / 9 | |
| 2.9.1 | 10 / 9 | |
| 2.9.0 | 10 / 9 | |
| 2.8.14 | 10 / 9 | |
| 2.8.13 | 10 / 9 | |
| 2.8.12 | 10 / 9 | |
| 2.8.11 | 10 / 9 | |
| 2.8.10 | 10 / 9 | |
| 2.8.9 | 10 / 9 | |
| 2.8.8 | 10 / 9 | |
| 2.8.7 | 10 / 9 | |
| 2.8.6 | 10 / 9 | |
| 2.8.5 | 10 / 9 | |
| 2.8.4 | 10 / 9 | |
| 2.8.3 | 10 / 9 | |
| 2.8.2 | 10 / 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.