@knapsack/eslint-config-starter
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:eslint-plugin-jsdoc | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): ESLint config packages reference configs in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-jsx-a11y | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-prettier | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-hooks | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-unused-imports | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:typescript-eslint | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-ava | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-config-airbnb | AI (phantom-deps): ESLint config packages reference configs in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-promise | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-unicorn | AI (phantom-deps): ESLint config packages reference plugins in config files, not code imports. | ai | |
| phantom-deps | phantom-dep:@eslint/compat | AI (phantom-deps): Framework-scoped ESLint package loaded by convention in config files. | ai | |
| phantom-deps | phantom-dep:@eslint/eslintrc | AI (phantom-deps): Framework-scoped ESLint package loaded by convention in config files. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): Referenced in ESLint config files by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): Referenced in ESLint config files by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): Referenced in ESLint config files by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): ESLint config packages reference typescript in config files by convention, not direct import. | ai |
Versions (showing 17 of 118)
| Version | Deps | Published |
|---|---|---|
| 4.80.13 | 21 / 1 | |
| 4.80.12 | 21 / 1 | |
| 4.80.11 | 21 / 1 | |
| 4.80.10 | 21 / 1 | |
| 4.80.9 | 21 / 1 | |
| 4.80.8 | 21 / 1 | |
| 4.80.7 | 21 / 1 | |
| 4.80.6 | 21 / 1 | |
| 4.80.5 | 21 / 1 | |
| 4.80.4 | 21 / 1 | |
| 4.80.3 | 21 / 1 | |
| 4.80.2 | 21 / 1 | |
| 4.80.1 | 21 / 1 | |
| 4.80.0 | 21 / 1 | |
| 4.79.2 | 21 / 1 | |
| 4.79.1 | 21 / 1 | |
| 4.79.0 | 21 / 1 |
v4.80.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.80.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.79.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.79.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.