@kitschpatrol/eslint-config
ESLint configuration for @kitschpatrol/shared-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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established publisher with clean track record; no provenance is acceptable here. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): ESLint config package declares plugins/tools as deps for consumers; phantom-dep heuristic is a structural FP here. | ai | |
| phantom-deps | phantom-dep:yargs | AI (phantom-deps): Same structural FP — CLI tool dependency declared for consumer use. | ai | |
| phantom-deps | phantom-dep:globals | AI (phantom-deps): Stable FP for this ESLint config package pattern. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Stable FP for this ESLint config package pattern. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-unicorn | AI (phantom-deps): Stable FP — eslint plugins declared as deps for consumer use. | ai | |
| phantom-deps | phantom-dep:@vitest/eslint-plugin | AI (phantom-deps): Stable FP — framework-scoped plugin declared as dep for consumer use. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-perfectionist | AI (phantom-deps): Stable FP for this ESLint config package pattern. | ai | |
| phantom-deps | phantom-dep:to-valid-identifier | AI (phantom-deps): to-valid-identifier is explicitly declared in dependencies; phantom-dep heuristic misfires here. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 7.6.1 | 54 / 8 | |
| 7.5.3 | 54 / 8 | |
| 7.5.2 | 54 / 8 | |
| 7.2.0 | 53 / 8 | |
| 7.0.1 | 53 / 8 | |
| 7.0.0 | 53 / 8 | |
| 6.2.0 | 51 / 8 | |
| 6.0.1 | 51 / 8 | |
| 6.0.0 | 51 / 8 | |
| 5.9.0 | 43 / 10 | |
| 5.8.1 | 43 / 9 | |
| 5.8.0 | 43 / 9 |
v7.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.