@kodiak-finance/orderly-eslint-config
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Publisher bards has clean track record; no material changes from prior approved version; consistent with routine maintainer handoff. | ai | |
| dependencies | unvetted-dep:eslint-config-eslint | AI (dependencies): eslint-config-eslint is a legitimate ESLint project config; stable false positive for an ESLint config package. | ai | |
| dependencies | unvetted-dep:eslint-plugin-monorepo-cop | AI (dependencies): eslint-plugin-monorepo-cop is a known ESLint plugin; expected dependency for a monorepo ESLint config. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped ESLint config under known org; 97 versions published; sparse metadata is typical for internal tooling packages. | ai | |
| phantom-deps | phantom-dep:eslint-config-turbo | AI (phantom-deps): ESLint config re-exports; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:eslint-config-eslint | AI (phantom-deps): ESLint config re-exports; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@eslint/js | AI (phantom-deps): ESLint flat config packages reference plugins by convention, not direct import. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 2.9.3 | 13 / 0 | |
| 2.9.2 | 13 / 0 | |
| 2.9.1 | 13 / 0 | |
| 2.8.33 | 13 / 0 | |
| 2.8.32 | 13 / 0 | |
| 2.8.30 | 13 / 0 | |
| 2.8.29 | 13 / 1 | |
| 2.8.27 | 13 / 1 | |
| 2.8.26 | 13 / 1 | |
| 2.8.24 | 13 / 1 | |
| 2.8.22 | 13 / 1 | |
| 2.8.20 | 13 / 1 | |
| 2.8.18 | 13 / 1 | |
| 2.8.16 | 13 / 1 | |
| 2.8.14 | 13 / 1 | |
| 2.8.13 | 13 / 1 | |
| 2.8.12 | 13 / 1 | |
| 2.8.11 | 13 / 1 | |
| 2.8.10 | 13 / 1 | |
| 2.8.9 | 13 / 1 | |
| 2.8.8 | 13 / 1 | |
| 2.8.7 | 13 / 1 | |
| 2.8.6 | 13 / 1 | |
| 2.8.4 | 13 / 1 | |
| 2.8.2 | 13 / 1 | |
| 2.8.1 | 13 / 1 | |
| 2.8.0 | 13 / 1 | |
| 2.7.4 | 13 / 1 |
v2.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.2
1 findingPackage 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.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.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.29
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.22
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.18
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.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.13
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.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
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.