← Home

@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.

100
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

jayree

Keywords

sfdx-pluginprettierhook

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
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 100 of 119)

Version Deps Published
1.3.178 14 / 21
1.3.177 14 / 21
1.3.176 14 / 21
1.3.175 14 / 21
1.3.174 14 / 21
1.3.173 14 / 21
1.3.172 14 / 21
1.3.171 14 / 21
1.3.170 14 / 21
1.3.169 14 / 21
1.3.168 14 / 21
1.3.167 14 / 21
1.3.166 14 / 21
1.3.165 14 / 21
1.3.164 14 / 21
1.3.163 14 / 21
1.3.162 14 / 21
1.3.161 14 / 21
1.3.160 14 / 21
1.3.159 14 / 21
1.3.158 14 / 21
1.3.157 14 / 21
1.3.156 14 / 21
1.3.155 14 / 21
1.3.154 14 / 21
1.3.153 14 / 21
1.3.152 14 / 21
1.3.151 14 / 21
1.3.150 14 / 21
1.3.149 14 / 21
1.3.148 14 / 21
1.3.147 14 / 21
1.3.146 14 / 21
1.3.145 14 / 21
1.3.144 14 / 21
1.3.143 14 / 21
1.3.142 14 / 21
1.3.141 14 / 21
1.3.140 14 / 21
1.3.139 14 / 21
1.3.138 14 / 21
1.3.137 14 / 21
1.3.136 14 / 21
1.3.135 14 / 20
1.3.134 14 / 20
1.3.133 14 / 20
1.3.132 14 / 20
1.3.131 14 / 20
1.3.130 14 / 20
1.3.129 14 / 20
1.3.128 14 / 20
1.3.127 14 / 20
1.3.126 14 / 20
1.3.125 14 / 20
1.3.124 14 / 20
1.3.123 14 / 20
1.3.122 14 / 20
1.3.121 14 / 20
1.3.120 14 / 20
1.3.119 14 / 20
1.3.118 14 / 20
1.3.117 14 / 20
1.3.116 14 / 20
1.3.115 14 / 20
1.3.114 14 / 20
1.3.113 14 / 20
1.3.112 14 / 20
1.3.111 14 / 20
1.3.110 14 / 20
1.3.109 14 / 20
1.3.108 14 / 20
1.3.107 14 / 20
1.3.106 14 / 20
1.3.105 14 / 20
1.3.104 14 / 20
1.3.103 14 / 20
1.3.102 14 / 20
1.3.101 14 / 20
1.3.100 14 / 20
1.3.99 14 / 20
1.3.98 14 / 20
1.3.97 14 / 20
1.3.96 14 / 20
1.3.95 14 / 20
1.3.94 14 / 20
1.3.93 14 / 20
1.3.92 14 / 20
1.3.91 14 / 20
1.3.90 14 / 20
1.3.89 14 / 20
1.3.88 14 / 20
1.3.87 14 / 20
1.3.86 14 / 20
1.3.85 14 / 20
1.3.84 14 / 20
1.3.83 14 / 20
1.3.82 14 / 20
1.3.81 14 / 20
1.3.80 14 / 20
1.3.79 14 / 20
Showing 100 of 119 Next page →

v1.3.178

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.177

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.176

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.175

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.3.113

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.112

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.111

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.110

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.109

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.108

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.107

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.106

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.105

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.104

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.103

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.102

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.101

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.100

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.99

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.98

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.97

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.96

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.95

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.94

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.93

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.92

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.91

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.90

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.89

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.88

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.87

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.86

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.85

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.84

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.83

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.82

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.81

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.80

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.3.79

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.