@darajs/prettier-config
Dara Prettier configuration
Supply chain provenance
Status for the latest visible version.
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 GitHub Actions publisher is a CI/CD automation pattern; SLSA attestation confirms integrity. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Config-only package; prettier is a declared dependency used by consumers, not imported directly. | ai | |
| phantom-deps | phantom-dep:@trivago/prettier-plugin-sort-imports | AI (phantom-deps): Config-only package; plugin is referenced in config JSON, not imported in JS code. | ai |
Versions (showing 57 of 157)
| Version | Deps | Published |
|---|---|---|
| 1.16.16 | 2 / 0 | |
| 1.16.15 | 2 / 0 | |
| 1.16.14 | 2 / 0 | |
| 1.16.13 | 2 / 0 | |
| 1.16.12 | 2 / 0 | |
| 1.16.11 | 2 / 0 | |
| 1.16.10 | 2 / 0 | |
| 1.16.9 | 2 / 0 | |
| 1.16.8 | 2 / 0 | |
| 1.16.7 | 2 / 0 | |
| 1.16.6 | 2 / 0 | |
| 1.16.5 | 2 / 0 | |
| 1.16.4 | 2 / 0 | |
| 1.16.3 | 2 / 0 | |
| 1.16.2 | 2 / 0 | |
| 1.16.1 | 2 / 0 | |
| 1.16.0 | 2 / 0 | |
| 1.15.7 | 2 / 0 | |
| 1.15.6 | 2 / 0 | |
| 1.15.5 | 2 / 0 | |
| 1.15.4 | 2 / 0 | |
| 1.15.3 | 2 / 0 | |
| 1.15.2 | 2 / 0 | |
| 1.15.1 | 2 / 0 | |
| 1.15.0 | 2 / 0 | |
| 1.14.9 | 2 / 0 | |
| 1.14.8 | 2 / 0 | |
| 1.14.7 | 2 / 0 | |
| 1.14.6 | 2 / 0 | |
| 1.14.5 | 2 / 0 | |
| 1.14.4 | 2 / 0 | |
| 1.14.3 | 2 / 0 | |
| 1.14.2 | 2 / 0 | |
| 1.14.1 | 2 / 0 | |
| 1.14.0 | 2 / 0 | |
| 1.13.1 | 2 / 0 | |
| 1.13.0 | 2 / 0 | |
| 1.12.7 | 2 / 0 | |
| 1.12.6 | 2 / 0 | |
| 1.12.5 | 2 / 0 | |
| 1.12.4 | 2 / 0 | |
| 1.12.3 | 2 / 0 | |
| 1.12.2 | 2 / 0 | |
| 1.12.1 | 2 / 0 | |
| 1.11.5 | 2 / 0 | |
| 1.11.4 | 2 / 0 | |
| 1.11.3 | 2 / 0 | |
| 1.11.2 | 2 / 0 | |
| 1.10.3 | 2 / 0 | |
| 1.10.2 | 2 / 0 | |
| 1.10.1 | 2 / 0 | |
| 1.10.0 | 2 / 0 | |
| 1.9.6 | 2 / 0 | |
| 1.9.5 | 2 / 0 | |
| 1.9.4 | 2 / 0 | |
| 1.9.3 | 2 / 0 | |
| 1.9.2 | 2 / 0 |
v1.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.1
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.
v1.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.