@kodiak-finance/orderly-markets
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): Monorepo scoped package; missing metadata is typical for internal packages in a multi-package workspace. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across @kodiak-finance scoped packages; not a spam indicator here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.9.2 | 7 / 12 | |
| 2.9.0 | 7 / 12 | |
| 2.8.32 | 7 / 12 | |
| 2.8.27 | 7 / 12 | |
| 2.8.26 | 7 / 12 | |
| 2.8.22 | 7 / 12 | |
| 2.8.19 | 7 / 12 | |
| 2.8.15 | 7 / 12 | |
| 2.8.10 | 7 / 12 | |
| 2.7.4 | 7 / 12 |
v2.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.32
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.22
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.15
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.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.