@ilbrando/eslint-plugin
ES lint rules
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@types/eslint__js | AI (dependencies): Type-declaration package for ESLint JS config; expected dependency for an ESLint plugin, no runtime risk. | ai | |
| phantom-deps | phantom-dep:@types/eslint__js | AI (phantom-deps): Framework-scoped type package; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/types | AI (phantom-deps): ESLint plugin loads typescript-eslint packages by convention; not directly imported but legitimately used. | ai | |
| phantom-deps | phantom-dep:@types/eslint-config-prettier | AI (phantom-deps): Type-only package loaded by framework convention; phantom-dep false positive for this package. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/visitor-keys | AI (phantom-deps): ESLint plugin dependency loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/scope-manager | AI (phantom-deps): ESLint plugin dependency loaded by convention; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 13 / 5 | |
| 1.0.8 | 8 / 4 | |
| 1.0.7 | 8 / 5 | |
| 1.0.6 | 8 / 5 | |
| 1.0.5 | 8 / 5 | |
| 1.0.4 | 9 / 5 | |
| 1.0.3 | 9 / 4 |
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.