@eslint-community/eslint-plugin-eslint-comments
Additional ESLint rules for ESLint directive comments.
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used to load the user's installed ESLint version by resolved path — a standard, legitimate pattern for ESLint plugins. Not a security risk for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver reflects intentional version continuity from the original fork; mass-production flag reflects eslint-community org's automated bot, not spam. Both signals are false positives for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.7.2 | 2 / 29 | |
| 4.7.1 | 2 / 28 | |
| 4.7.0 | 2 / 28 | |
| 4.6.0 | 2 / 24 | |
| 4.5.0 | 2 / 19 | |
| 4.4.1 | 2 / 17 | |
| 4.4.0 | 2 / 17 | |
| 4.3.0 | 2 / 17 | |
| 4.2.0 | 2 / 17 | |
| 4.1.0 | 2 / 17 | |
| 4.0.0 | 2 / 16 | |
| 3.2.1 | 2 / 16 | |
| 3.2.0 | 2 / 17 | |
| 5.0.0-alpha.1 | 2 / 19 |
v4.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.