@etchteam/eslint-config
Etch's standard eslint config
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Config package; prettier referenced in configs, not direct imports. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): Config package; parser referenced in configs, not direct imports. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): Config package; plugin referenced in configs, not direct imports. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): Config package; eslint referenced in configs, not direct imports. | ai | |
| phantom-deps | phantom-dep:eslint-config-next | AI (phantom-deps): Config package; eslint-config-next referenced in configs, not direct imports. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): ESLint config package references resolvers in config files, not via direct imports — expected pattern. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): ESLint config package references plugins in config files, not via direct imports — expected pattern. | ai |
Versions (showing 35 of 138)
| Version | Deps | Published |
|---|---|---|
| 2.2.195 | 19 / 4 | |
| 2.2.194 | 19 / 4 | |
| 2.2.193 | 19 / 4 | |
| 2.2.192 | 19 / 4 | |
| 2.2.191 | 19 / 4 | |
| 2.2.190 | 19 / 4 | |
| 2.2.189 | 19 / 4 | |
| 2.2.188 | 19 / 4 | |
| 2.2.187 | 19 / 4 | |
| 2.2.186 | 19 / 4 | |
| 2.2.185 | 19 / 4 | |
| 2.2.184 | 19 / 4 | |
| 2.2.183 | 19 / 4 | |
| 2.2.182 | 19 / 4 | |
| 2.2.181 | 19 / 4 | |
| 2.2.180 | 19 / 4 | |
| 2.2.179 | 19 / 4 | |
| 2.2.178 | 19 / 4 | |
| 2.2.177 | 19 / 4 | |
| 2.2.176 | 19 / 4 | |
| 2.2.175 | 19 / 4 | |
| 2.2.174 | 19 / 4 | |
| 2.2.173 | 19 / 4 | |
| 2.2.172 | 19 / 4 | |
| 2.2.171 | 19 / 4 | |
| 2.2.170 | 19 / 4 | |
| 2.2.169 | 19 / 4 | |
| 2.2.168 | 19 / 4 | |
| 2.2.167 | 19 / 4 | |
| 2.2.166 | 19 / 4 | |
| 2.2.165 | 19 / 4 | |
| 2.2.164 | 19 / 4 | |
| 2.2.163 | 19 / 4 | |
| 2.2.162 | 19 / 4 | |
| 2.2.161 | 19 / 4 |
v2.2.195
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.194
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.193
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.192
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.191
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.190
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.189
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.188
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.187
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.186
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.185
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.184
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.183
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.182
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.181
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.180
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.179
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.178
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.177
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.175
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.174
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.173
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.172
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.171
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.170
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.169
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.168
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.167
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.166
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.165
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.164
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.163
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.162
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.161
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.