@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, so a manually published version cannot be tied back to a reviewed commit.
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 100 of 669)
| Version | Deps | Published |
|---|---|---|
| 4.26.9 | 19 / 1 | |
| 4.26.8 | 19 / 1 | |
| 4.26.7 | 19 / 1 | |
| 4.26.6 | 19 / 1 | |
| 4.26.5 | 19 / 1 | |
| 4.26.4 | 19 / 1 | |
| 4.26.3 | 19 / 1 | |
| 4.26.2 | 19 / 1 | |
| 4.26.1 | 19 / 1 | |
| 4.26.0 | 19 / 1 | |
| 4.25.7 | 19 / 1 | |
| 4.25.6 | 19 / 1 | |
| 4.25.5 | 19 / 1 | |
| 4.25.4 | 19 / 1 | |
| 4.25.3 | 19 / 1 | |
| 4.25.2 | 19 / 1 | |
| 4.25.1 | 19 / 1 | |
| 4.25.0 | 19 / 1 | |
| 4.24.12 | 19 / 1 | |
| 4.24.11 | 19 / 1 | |
| 4.24.10 | 19 / 1 | |
| 4.24.9 | 19 / 1 | |
| 4.24.8 | 19 / 1 | |
| 4.24.7 | 19 / 1 | |
| 4.24.6 | 19 / 1 | |
| 4.24.5 | 19 / 1 | |
| 4.24.4 | 19 / 1 | |
| 4.24.3 | 19 / 1 | |
| 4.24.2 | 19 / 1 | |
| 4.24.1 | 19 / 1 | |
| 4.24.0 | 19 / 1 | |
| 4.23.4 | 19 / 1 | |
| 4.23.3 | 19 / 1 | |
| 4.23.2 | 19 / 1 | |
| 4.23.1 | 19 / 1 | |
| 4.23.0 | 19 / 1 | |
| 4.22.15 | 19 / 1 | |
| 4.22.14 | 19 / 1 | |
| 4.22.13 | 19 / 1 | |
| 4.22.12 | 19 / 1 | |
| 4.22.11 | 19 / 1 | |
| 4.22.10 | 19 / 1 | |
| 4.22.9 | 19 / 1 | |
| 4.22.8 | 19 / 1 | |
| 4.22.7 | 19 / 1 | |
| 4.22.6 | 19 / 1 | |
| 4.22.5 | 19 / 1 | |
| 4.22.4 | 19 / 1 | |
| 4.22.3 | 19 / 1 | |
| 4.22.2 | 19 / 1 | |
| 4.22.1 | 19 / 1 | |
| 4.22.0 | 19 / 1 | |
| 4.21.15 | 19 / 1 | |
| 4.21.14 | 19 / 1 | |
| 4.21.13 | 19 / 1 | |
| 4.21.12 | 19 / 1 | |
| 4.21.11 | 19 / 1 | |
| 4.21.10 | 19 / 1 | |
| 4.21.9 | 19 / 1 | |
| 4.21.8 | 19 / 1 | |
| 4.21.7 | 19 / 1 | |
| 4.21.6 | 19 / 1 | |
| 4.21.5 | 19 / 1 | |
| 4.21.4 | 19 / 1 | |
| 4.21.3 | 19 / 1 | |
| 4.21.2 | 19 / 1 | |
| 4.21.1 | 19 / 1 | |
| 4.21.0 | 19 / 1 | |
| 4.20.0 | 19 / 1 | |
| 4.19.8 | 19 / 1 | |
| 4.19.7 | 19 / 1 | |
| 4.19.6 | 19 / 1 | |
| 4.19.5 | 19 / 1 | |
| 4.19.4 | 19 / 1 | |
| 4.19.3 | 19 / 1 | |
| 4.19.2 | 19 / 1 | |
| 4.19.1 | 19 / 1 | |
| 4.19.0 | 19 / 1 | |
| 4.18.1 | 19 / 1 | |
| 4.18.0 | 19 / 1 | |
| 4.17.0 | 19 / 1 | |
| 4.16.4 | 19 / 1 | |
| 4.16.3 | 19 / 1 | |
| 4.16.2 | 19 / 1 | |
| 4.16.1 | 19 / 1 | |
| 4.16.0 | 19 / 1 | |
| 4.15.1 | 19 / 1 | |
| 4.15.0 | 19 / 1 | |
| 4.14.0 | 19 / 1 | |
| 4.13.3 | 19 / 1 | |
| 4.13.2 | 19 / 1 | |
| 4.13.1 | 19 / 1 | |
| 4.13.0 | 19 / 1 | |
| 4.12.0 | 19 / 1 | |
| 4.11.1 | 19 / 1 | |
| 4.11.0 | 19 / 1 | |
| 4.10.8 | 19 / 1 | |
| 4.10.7 | 19 / 1 | |
| 4.10.6 | 19 / 1 | |
| 4.10.5 | 19 / 1 |
v4.26.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.