@kodiak-finance/orderly-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@kodiak-finance/orderly-ui-scaffold | AI (dependencies): Sibling scoped package in the same monorepo, pinned to matching version; stable pattern across releases. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @kodiak-finance packages; not a per-version risk signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing metadata is expected, not a spam/malware indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all @kodiak-finance/orderly-* packages; not a risk signal. | ai | |
| phantom-deps | phantom-dep:date-fns | AI (phantom-deps): date-fns is declared as a runtime dep; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 2.9.2 | 10 / 9 | |
| 2.9.1 | 10 / 9 | |
| 2.9.0 | 10 / 9 | |
| 2.8.33 | 10 / 9 | |
| 2.8.32 | 10 / 9 | |
| 2.8.31 | 10 / 9 | |
| 2.8.30 | 10 / 9 | |
| 2.8.28 | 10 / 9 | |
| 2.8.27 | 10 / 9 | |
| 2.8.26 | 10 / 9 | |
| 2.8.24 | 10 / 9 | |
| 2.8.23 | 10 / 9 | |
| 2.8.22 | 10 / 9 | |
| 2.8.21 | 10 / 9 | |
| 2.8.20 | 10 / 9 | |
| 2.8.19 | 10 / 9 | |
| 2.8.18 | 10 / 9 | |
| 2.8.17 | 10 / 9 | |
| 2.8.16 | 10 / 9 | |
| 2.8.15 | 10 / 9 | |
| 2.8.14 | 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.3 | 10 / 9 | |
| 2.8.0 | 10 / 9 | |
| 2.7.4 | 10 / 9 |
v2.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.6
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.
v2.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.