@homer0/eslint-plugin
My custom configurations for ESLint.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived personal package with 53 versions; dormancy followed by a legitimate major update is plausible. | ai | |
| dependencies | unvetted-dep:@types/confusing-browser-globals | AI (dependencies): Type-definition package for already-present confusing-browser-globals dep; no executable code risk. | ai | |
| phantom-deps | phantom-dep:@eslint/js | AI (phantom-deps): Framework-scoped ESLint package loaded by convention, not direct import; stable false positive for this plugin. | ai | |
| phantom-deps | phantom-dep:@types/confusing-browser-globals | AI (phantom-deps): Type definitions used at build/type-check time, not imported directly; stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 14.2.4 | 13 / 8 | |
| 14.1.2 | 13 / 8 | |
| 14.1.1 | 13 / 8 | |
| 14.1.0 | 13 / 8 | |
| 14.0.1 | 13 / 5 | |
| 14.0.0 | 12 / 6 |
v14.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v14.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.