@jayree/sfdx-plugin-prettier
A Salesforce CLI plugin containing a hook that uses prettier to format Salesforce metadata source files retrieved or pulled from Salesforce orgs.
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): Publisher is GitHub Actions with SLSA provenance attestation; CI/CD publishing is the documented release mechanism for this package. | ai | |
| dependencies | unvetted-dep:@jayree/changelog | AI (dependencies): First-party dep from same author; consistent across all versions of this package. | ai | |
| dependencies | unvetted-dep:prettier-plugin-apex | AI (dependencies): Well-known Salesforce Apex prettier plugin; core to this package's formatting purpose. | ai | |
| provenance | no-provenance | AI (provenance): Established package with long publish history; lack of provenance is consistent across all versions. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit TypeScript runtime dependency; stable false positive. | ai | |
| phantom-deps | phantom-dep:@prettier/plugin-xml | AI (phantom-deps): Referenced in prettier config files, not direct imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:prettier-plugin-apex | AI (phantom-deps): Referenced in prettier config files, not direct imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@salesforce/sf-plugins-core | AI (phantom-deps): Referenced in config files; stable false positive for this Salesforce CLI plugin. | ai |
Versions (showing 19 of 119)
| Version | Deps | Published |
|---|---|---|
| 1.3.78 | 14 / 20 | |
| 1.3.77 | 14 / 20 | |
| 1.3.76 | 14 / 20 | |
| 1.3.75 | 14 / 20 | |
| 1.3.74 | 14 / 20 | |
| 1.3.73 | 14 / 20 | |
| 1.3.72 | 14 / 20 | |
| 1.3.71 | 14 / 20 | |
| 1.3.70 | 14 / 20 | |
| 1.3.69 | 14 / 20 | |
| 1.3.68 | 14 / 20 | |
| 1.3.67 | 14 / 20 | |
| 1.3.66 | 14 / 20 | |
| 1.3.65 | 14 / 20 | |
| 1.3.64 | 14 / 20 | |
| 1.3.63 | 14 / 20 | |
| 1.3.62 | 14 / 20 | |
| 1.3.61 | 14 / 20 | |
| 1.3.60 | 14 / 20 |
v1.3.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.