@standard-config/prettier
TypeScript-first Prettier config
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:prettier-plugin-sh | AI (phantom-deps): Prettier config package; plugins are referenced in config files, not imported directly — stable false positive. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-pkg | AI (phantom-deps): Same pattern: plugin referenced in config, not imported directly. | ai | |
| phantom-deps | phantom-dep:@prettier/plugin-oxc | AI (phantom-deps): Same pattern: plugin referenced in config, not imported directly. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-yaml | AI (phantom-deps): Same pattern: plugin referenced in config, not imported directly. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-sort-json | AI (phantom-deps): Same pattern: plugin referenced in config, not imported directly. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-expand-json | AI (phantom-deps): Same pattern: plugin referenced in config, not imported directly. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-markdown-html | AI (phantom-deps): Same pattern: plugin referenced in config, not imported directly. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 1.13.3 | 7 / 11 | |
| 1.13.2 | 7 / 11 | |
| 1.13.0 | 7 / 11 | |
| 1.12.1 | 7 / 11 | |
| 1.12.0 | 7 / 11 | |
| 1.11.3 | 7 / 11 | |
| 1.11.2 | 7 / 11 | |
| 1.11.1 | 7 / 14 | |
| 1.11.0 | 7 / 14 | |
| 1.10.0 | 9 / 15 | |
| 1.9.1 | 9 / 15 | |
| 1.9.0 | 9 / 15 | |
| 1.8.1 | 9 / 14 | |
| 1.6.0 | 6 / 13 | |
| 1.5.0 | 6 / 16 | |
| 1.4.0 | 6 / 10 | |
| 1.3.0 | 5 / 10 | |
| 1.2.1 | 5 / 10 | |
| 1.2.0 | 5 / 10 | |
| 1.1.0 | 5 / 10 | |
| 1.0.2 | 4 / 9 | |
| 1.0.1 | 4 / 9 | |
| 1.0.0 | 4 / 7 |
v1.13.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.13.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.