eslint-plugin-prettier
Runs prettier as an eslint rule
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): Transition from human publisher (jounqin) to GitHub Actions CI/CD publishing with SLSA provenance; legitimate automation of the prettier org's release pipeline. | ai | |
| provenance | missing-githead | AI (provenance): Expected side-effect of switching to GitHub Actions publishing; gitHead is not populated by CI-based npm publish flows. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 5.5.6 | 2 / 0 | |
| 5.5.5 | 2 / 0 | |
| 5.5.4 | 2 / 0 | |
| 5.5.3 | 2 / 0 | |
| 5.5.2 | 2 / 0 | |
| 5.5.1 | 2 / 0 | |
| 5.5.0 | 2 / 0 | |
| 5.4.1 | 2 / 0 | |
| 5.4.0 | 2 / 0 | |
| 5.3.1 | 2 / 0 | |
| 5.3.0 | 2 / 0 | |
| 5.2.6 | 2 / 0 | |
| 5.2.5 | 2 / 0 | |
| 5.2.4 | 2 / 0 | |
| 5.2.3 | 2 / 32 | |
| 5.2.2 | 2 / 32 | |
| 5.2.1 | 2 / 32 | |
| 5.1.3 | 2 / 31 | |
| 5.1.2 | 2 / 30 | |
| 5.1.1 | 2 / 30 | |
| 5.1.0 | 2 / 28 | |
| 5.0.1 | 2 / 27 | |
| 5.0.0 | 2 / 27 | |
| 4.2.1 | 1 / 18 | |
| 4.2.0 | 1 / 19 | |
| 4.1.0 | 1 / 16 | |
| 4.0.0 | 1 / 12 | |
| 3.4.1 | 1 / 10 | |
| 3.4.0 | 1 / 10 | |
| 3.3.1 | 1 / 10 | |
| 3.3.0 | 1 / 10 | |
| 3.2.0 | 1 / 10 | |
| 3.1.4 | 1 / 10 | |
| 3.1.3 | 1 / 10 | |
| 3.1.2 | 1 / 10 | |
| 3.1.1 | 1 / 10 | |
| 3.1.0 | 1 / 10 | |
| 3.0.1 | 1 / 10 | |
| 3.0.0 | 1 / 10 | |
| 2.7.0 | 2 / 12 | |
| 2.6.2 | 2 / 11 | |
| 2.6.1 | 2 / 11 | |
| 2.6.0 | 2 / 11 | |
| 2.5.0 | 2 / 10 | |
| 2.4.0 | 2 / 10 | |
| 2.3.1 | 2 / 10 | |
| 2.3.0 | 2 / 10 | |
| 2.2.0 | 2 / 9 | |
| 2.1.2 | 2 / 9 | |
| 2.1.1 | 2 / 7 | |
| 2.1.0 | 2 / 7 | |
| 2.0.1 | 1 / 7 | |
| 2.0.0 | 1 / 6 | |
| 1.0.0 | 2 / 5 |
v5.5.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.5
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-01-14. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.4
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jounqin.
v5.5.3
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jounqin.
v5.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jounqin.
v5.1.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jounqin.
v5.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jounqin.
v5.1.1
3 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jounqin.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-12-21. This could indicate a legitimate maintainer transition or an account compromise.
v5.1.0
3 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bpscott.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-12-19. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jounqin.
v4.2.1
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
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-27. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bpscott.