@voiceflow/prettier-config
Shared configuration for [`prettier`](https://prettier.io/).
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to vf-serviceaccount org CI publisher; consistent with Voiceflow's publishing pattern across 82 approved packages. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-toml | AI (phantom-deps): Config-only package; plugins are referenced in config, not imported directly — stable false positive. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-packagejson | AI (phantom-deps): Config-only package; plugins are referenced in config, not imported directly — stable false positive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal shared config package; tiny payload, no repo URL, and no keywords are expected for this package type. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.13.0 | 1 / 0 | |
| 1.12.2 | 1 / 0 | |
| 1.12.1 | 2 / 0 | |
| 1.12.0 | 2 / 0 | |
| 1.11.0 | 2 / 0 | |
| 1.10.3 | 2 / 0 | |
| 1.10.0 | 2 / 0 |
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
2 findingsThis version was published by a different npm account than previous versions on 2025-12-12. 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.
v1.11.0
2 findingsThis version was published by a different npm account than previous versions on 2025-11-25. 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.
v1.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.