@jayree/sfdx-plugin-org
A Salesforce CLI plugin containing commands to configure State and Country/Territory Picklists and other org settings.
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): Package consistently published via GitHub Actions CI with SLSA attestation; jayree→GitHub Actions is expected automation pattern. | ai | |
| dependencies | unvetted-dep:tabletojson | AI (dependencies): Legitimate HTML-table parsing dep used by this Salesforce CLI plugin; stable across versions. | ai | |
| dependencies | unvetted-dep:@jayree/changelog | AI (dependencies): First-party changelog dep from same author; stable across versions. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:enquirer | AI (phantom-deps): enquirer is referenced via @listr2/prompt-adapter-enquirer and config files; stable false positive. | ai |
Versions (showing 34 of 134)
| Version | Deps | Published |
|---|---|---|
| 1.2.82 | 22 / 19 | |
| 1.2.81 | 22 / 19 | |
| 1.2.80 | 22 / 19 | |
| 1.2.79 | 22 / 19 | |
| 1.2.78 | 22 / 19 | |
| 1.2.77 | 22 / 19 | |
| 1.2.76 | 22 / 19 | |
| 1.2.75 | 22 / 19 | |
| 1.2.74 | 22 / 19 | |
| 1.2.73 | 22 / 19 | |
| 1.2.72 | 22 / 19 | |
| 1.2.71 | 22 / 19 | |
| 1.2.70 | 22 / 19 | |
| 1.2.69 | 22 / 19 | |
| 1.2.68 | 22 / 19 | |
| 1.2.67 | 22 / 19 | |
| 1.2.66 | 22 / 19 | |
| 1.2.65 | 22 / 19 | |
| 1.2.64 | 22 / 19 | |
| 1.2.63 | 22 / 19 | |
| 1.2.62 | 22 / 19 | |
| 1.2.61 | 22 / 19 | |
| 1.2.60 | 21 / 18 | |
| 1.2.59 | 21 / 18 | |
| 1.2.58 | 21 / 18 | |
| 1.2.57 | 21 / 18 | |
| 1.2.56 | 21 / 18 | |
| 1.2.55 | 21 / 18 | |
| 1.2.54 | 21 / 18 | |
| 1.2.53 | 21 / 18 | |
| 1.2.52 | 21 / 18 | |
| 1.2.51 | 21 / 18 | |
| 1.2.50 | 21 / 18 | |
| 1.2.49 | 21 / 18 |
v1.2.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.80
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.78
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.63
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.