eslint-config-prettier
Turns off all rules that are unnecessary or might conflict with Prettier.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition from lydell to jounqin within the prettier org; jounqin is a well-established publisher with strong track record. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jounqin added as maintainer of prettier/eslint-config-prettier; consistent with org-level maintainer transition. | ai |
Versions (showing 83 of 83)
| Version | Deps | Published |
|---|---|---|
| 10.1.8 | 0 / 0 | |
| 10.1.5 | 0 / 0 | |
| 10.1.4 | 0 / 0 | |
| 10.1.3 | 0 / 0 | |
| 10.1.2 | 0 / 0 | |
| 10.1.1 | 0 / 0 | |
| 10.1.0 | 0 / 0 | |
| 10.0.3 | 0 / 0 | |
| 10.0.2 | 0 / 0 | |
| 10.0.1 | 0 / 0 | |
| 10.0.0 | 0 / 0 | |
| 9.1.0 | 0 / 0 | |
| 9.0.0 | 0 / 0 | |
| 8.10.0 | 0 / 0 | |
| 8.9.0 | 0 / 0 | |
| 8.8.0 | 0 / 0 | |
| 8.7.0 | 0 / 0 | |
| 8.6.0 | 0 / 0 | |
| 8.5.0 | 0 / 0 | |
| 8.4.0 | 0 / 0 | |
| 8.3.0 | 0 / 0 | |
| 8.2.0 | 0 / 0 | |
| 8.1.0 | 0 / 0 | |
| 8.0.0 | 0 / 0 | |
| 7.2.0 | 0 / 0 | |
| 7.1.0 | 0 / 0 | |
| 7.0.0 | 0 / 0 | |
| 6.15.0 | 1 / 20 | |
| 6.14.0 | 1 / 20 | |
| 6.13.0 | 1 / 20 | |
| 6.12.0 | 1 / 20 | |
| 6.11.0 | 1 / 20 | |
| 6.10.1 | 1 / 20 | |
| 6.10.0 | 1 / 20 | |
| 6.9.0 | 1 / 20 | |
| 6.8.0 | 1 / 20 | |
| 6.7.0 | 1 / 20 | |
| 6.6.0 | 1 / 20 | |
| 6.5.0 | 1 / 20 | |
| 6.4.0 | 1 / 19 | |
| 6.3.0 | 1 / 19 | |
| 6.2.0 | 1 / 19 | |
| 6.1.0 | 1 / 19 | |
| 6.0.0 | 1 / 19 | |
| 5.1.0 | 1 / 19 | |
| 5.0.0 | 1 / 19 | |
| 4.3.0 | 1 / 19 | |
| 4.2.0 | 1 / 19 | |
| 4.1.0 | 1 / 19 | |
| 4.0.0 | 1 / 19 | |
| 3.6.0 | 1 / 18 | |
| 3.5.0 | 1 / 17 | |
| 3.4.0 | 1 / 17 | |
| 3.3.0 | 1 / 15 | |
| 3.2.0 | 1 / 15 | |
| 3.1.0 | 1 / 12 | |
| 3.0.1 | 1 / 11 | |
| 3.0.0 | 1 / 11 | |
| 2.10.0 | 1 / 12 | |
| 2.9.0 | 1 / 12 | |
| 2.8.0 | 1 / 12 | |
| 2.7.0 | 1 / 11 | |
| 2.6.0 | 1 / 11 | |
| 2.5.0 | 1 / 11 | |
| 2.4.0 | 1 / 10 | |
| 2.3.0 | 1 / 10 | |
| 2.2.0 | 1 / 10 | |
| 2.1.1 | 1 / 10 | |
| 2.1.0 | 1 / 10 | |
| 2.0.0 | 1 / 10 | |
| 1.7.0 | 1 / 10 | |
| 1.6.0 | 1 / 10 | |
| 1.5.0 | 1 / 10 | |
| 1.4.1 | 1 / 10 | |
| 1.4.0 | 1 / 10 | |
| 1.3.0 | 1 / 10 | |
| 1.2.0 | 1 / 10 | |
| 1.1.1 | 1 / 10 | |
| 1.1.0 | 1 / 10 | |
| 1.0.3 | 1 / 5 | |
| 1.0.2 | 1 / 5 | |
| 1.0.1 | 1 / 5 | |
| 1.0.0 | 1 / 5 |
v10.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v10.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
2 findingsThis version was published by a different npm account than previous versions on 2025-01-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.