@salesforce/plugin-data
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Package has 348 versions and 2008-day history; publisher salesforce-releases is continuously active. Dormancy signal is a false positive for this well-maintained Salesforce CLI plugin. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Salesforce consolidating individual developer accounts under centralized salesforce-admin/salesforce-releases service accounts; consistent with org-wide publishing policy change, not a takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): salesforce-admin is a Salesforce organizational account; addition is consistent with centralized publishing consolidation, not a suspicious new actor. | ai | |
| phantom-deps | phantom-dep:change-case | AI (phantom-deps): change-case is explicitly declared as a runtime dependency in package.json; the phantom-dep finding is a false positive for this package's usage pattern. | ai | |
| provenance | no-provenance | AI (provenance): Salesforce uses their own signing infrastructure (sfdx.publicKeyUrl/signatureUrl) rather than Sigstore; absence of npm provenance is expected and stable for this publisher. | ai |
Versions (showing 100 of 111)
| Version | Deps | Published |
|---|---|---|
| 4.0.114 | 14 / 11 | |
| 4.0.113 | 14 / 11 | |
| 4.0.112 | 14 / 11 | |
| 4.0.111 | 14 / 11 | |
| 4.0.110 | 14 / 11 | |
| 4.0.109 | 14 / 11 | |
| 4.0.108 | 14 / 11 | |
| 4.0.107 | 14 / 11 | |
| 4.0.106 | 14 / 11 | |
| 4.0.105 | 14 / 11 | |
| 4.0.104 | 14 / 11 | |
| 4.0.103 | 14 / 11 | |
| 4.0.102 | 14 / 11 | |
| 4.0.101 | 14 / 11 | |
| 4.0.100 | 14 / 11 | |
| 4.0.99 | 14 / 11 | |
| 4.0.98 | 14 / 11 | |
| 4.0.97 | 14 / 11 | |
| 4.0.96 | 14 / 11 | |
| 4.0.95 | 14 / 11 | |
| 4.0.94 | 14 / 11 | |
| 4.0.93 | 14 / 11 | |
| 4.0.92 | 14 / 11 | |
| 4.0.91 | 14 / 11 | |
| 4.0.90 | 14 / 11 | |
| 4.0.89 | 14 / 11 | |
| 4.0.88 | 14 / 11 | |
| 4.0.87 | 14 / 11 | |
| 4.0.86 | 14 / 11 | |
| 4.0.85 | 14 / 11 | |
| 4.0.84 | 14 / 11 | |
| 4.0.83 | 14 / 11 | |
| 4.0.82 | 14 / 11 | |
| 4.0.81 | 14 / 11 | |
| 4.0.80 | 14 / 11 | |
| 4.0.79 | 14 / 11 | |
| 4.0.78 | 14 / 11 | |
| 4.0.77 | 14 / 11 | |
| 4.0.75 | 13 / 12 | |
| 4.0.74 | 13 / 12 | |
| 4.0.73 | 13 / 11 | |
| 4.0.72 | 13 / 11 | |
| 4.0.71 | 13 / 11 | |
| 4.0.70 | 13 / 11 | |
| 4.0.69 | 13 / 11 | |
| 4.0.68 | 13 / 11 | |
| 4.0.67 | 13 / 11 | |
| 4.0.66 | 12 / 11 | |
| 4.0.65 | 12 / 11 | |
| 4.0.64 | 12 / 11 | |
| 4.0.63 | 12 / 11 | |
| 4.0.62 | 12 / 11 | |
| 4.0.61 | 12 / 11 | |
| 4.0.60 | 12 / 11 | |
| 4.0.59 | 12 / 11 | |
| 4.0.58 | 12 / 11 | |
| 4.0.57 | 12 / 11 | |
| 4.0.56 | 12 / 11 | |
| 4.0.55 | 12 / 11 | |
| 4.0.54 | 12 / 11 | |
| 4.0.53 | 12 / 11 | |
| 4.0.52 | 12 / 11 | |
| 4.0.51 | 12 / 11 | |
| 4.0.50 | 12 / 11 | |
| 4.0.49 | 12 / 11 | |
| 4.0.48 | 12 / 11 | |
| 4.0.47 | 12 / 11 | |
| 4.0.46 | 12 / 11 | |
| 4.0.45 | 12 / 11 | |
| 4.0.44 | 12 / 11 | |
| 4.0.43 | 12 / 11 | |
| 4.0.42 | 12 / 11 | |
| 4.0.41 | 12 / 11 | |
| 4.0.40 | 12 / 11 | |
| 4.0.39 | 12 / 11 | |
| 4.0.38 | 12 / 11 | |
| 4.0.37 | 12 / 11 | |
| 4.0.36 | 12 / 11 | |
| 4.0.35 | 12 / 11 | |
| 4.0.34 | 12 / 11 | |
| 4.0.33 | 12 / 11 | |
| 4.0.32 | 12 / 11 | |
| 4.0.31 | 12 / 11 | |
| 4.0.30 | 12 / 11 | |
| 4.0.29 | 12 / 11 | |
| 4.0.28 | 12 / 11 | |
| 4.0.27 | 12 / 11 | |
| 4.0.26 | 12 / 11 | |
| 4.0.25 | 12 / 11 | |
| 4.0.24 | 12 / 11 | |
| 4.0.23 | 12 / 11 | |
| 4.0.22 | 12 / 11 | |
| 4.0.21 | 12 / 11 | |
| 4.0.20 | 12 / 11 | |
| 4.0.19 | 12 / 11 | |
| 4.0.18 | 12 / 11 | |
| 4.0.17 | 12 / 11 | |
| 4.0.16 | 12 / 11 | |
| 4.0.15 | 12 / 11 | |
| 4.0.14 | 12 / 11 |
v4.0.114
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.113
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.112
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.111
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.