@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 11 of 111)
| Version | Deps | Published |
|---|---|---|
| 4.0.13 | 12 / 11 | |
| 4.0.12 | 12 / 11 | |
| 4.0.11 | 12 / 11 | |
| 4.0.10 | 12 / 11 | |
| 4.0.9 | 12 / 11 | |
| 4.0.8 | 12 / 11 | |
| 4.0.7 | 12 / 11 | |
| 4.0.6 | 12 / 11 | |
| 4.0.5 | 12 / 11 | |
| 4.0.4 | 12 / 11 | |
| 4.0.1 | 12 / 11 |
v4.0.13
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.12
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.11
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.10
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.9
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.8
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.7
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.6
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.5
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.4
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.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.