@salesforce/lds-adapters-platform-cdp-machine-learning
machine learning for data cloud
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): lwc-admin is a Salesforce org admin account with 1892 approved packages; publisher change reflects org-level consolidation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): salesforce-admin is a known Salesforce org account; lwc-admin publisher has 1828 approved packages. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Large maintainer removal consistent with Salesforce org-level account consolidation, not a takeover. | ai | |
| phantom-deps | phantom-dep:@salesforce/lds-bindings | AI (phantom-deps): Same org scope; likely used indirectly via build artifacts rather than direct import. | ai |
Versions (showing 79 of 179)
| Version | Deps | Published |
|---|---|---|
| 1.360.1 | 1 / 1 | |
| 1.360.0 | 1 / 1 | |
| 1.359.0 | 1 / 1 | |
| 1.358.0 | 1 / 1 | |
| 1.357.0 | 1 / 1 | |
| 1.356.0 | 1 / 1 | |
| 1.355.0 | 1 / 1 | |
| 1.354.0 | 1 / 1 | |
| 1.353.1 | 1 / 1 | |
| 1.353.0 | 1 / 1 | |
| 1.352.0 | 1 / 1 | |
| 1.351.1 | 1 / 1 | |
| 1.351.0 | 1 / 1 | |
| 1.350.0 | 1 / 1 | |
| 1.349.0 | 1 / 1 | |
| 1.348.1 | 1 / 1 | |
| 1.348.0 | 1 / 1 | |
| 1.347.1 | 1 / 1 | |
| 1.347.0 | 1 / 1 | |
| 1.346.0 | 1 / 1 | |
| 1.345.0 | 1 / 1 | |
| 1.344.0 | 1 / 1 | |
| 1.343.0 | 1 / 1 | |
| 1.342.0 | 1 / 1 | |
| 1.341.0 | 1 / 1 | |
| 1.340.0 | 1 / 1 | |
| 1.339.0 | 1 / 1 | |
| 1.338.0 | 1 / 1 | |
| 1.337.0 | 1 / 1 | |
| 1.336.0 | 1 / 1 | |
| 1.335.0 | 1 / 1 | |
| 1.334.0 | 1 / 1 | |
| 1.333.0 | 1 / 1 | |
| 1.332.0 | 1 / 1 | |
| 1.331.0 | 1 / 1 | |
| 1.330.0 | 1 / 1 | |
| 1.329.1 | 1 / 1 | |
| 1.329.0 | 1 / 1 | |
| 1.328.0 | 1 / 1 | |
| 1.327.0 | 1 / 1 | |
| 1.326.0 | 1 / 1 | |
| 1.325.0 | 1 / 1 | |
| 1.324.0 | 1 / 1 | |
| 1.323.0 | 1 / 1 | |
| 1.322.0 | 1 / 1 | |
| 1.321.0 | 1 / 1 | |
| 1.320.0 | 1 / 1 | |
| 1.319.0 | 1 / 1 | |
| 1.318.0 | 1 / 1 | |
| 1.317.0 | 1 / 1 | |
| 1.316.0 | 1 / 1 | |
| 1.315.0 | 1 / 1 | |
| 1.314.0 | 1 / 1 | |
| 1.313.0 | 1 / 1 | |
| 1.312.1 | 1 / 1 | |
| 1.312.0 | 1 / 1 | |
| 1.311.1 | 1 / 1 | |
| 1.311.0 | 1 / 1 | |
| 1.310.0 | 1 / 1 | |
| 1.309.0 | 1 / 1 | |
| 1.308.0 | 1 / 1 | |
| 1.307.0 | 1 / 1 | |
| 1.306.0 | 1 / 1 | |
| 1.305.0 | 1 / 1 | |
| 1.304.0 | 1 / 1 | |
| 1.303.0 | 1 / 1 | |
| 1.302.0 | 1 / 1 | |
| 1.301.0 | 1 / 1 | |
| 1.300.0 | 1 / 1 | |
| 1.299.0 | 1 / 1 | |
| 1.298.0 | 1 / 1 | |
| 1.297.0 | 1 / 1 | |
| 1.296.1 | 1 / 1 | |
| 1.296.0 | 1 / 1 | |
| 1.295.0 | 1 / 1 | |
| 1.294.0 | 1 / 1 | |
| 1.293.0 | 1 / 1 | |
| 1.292.0 | 1 / 1 | |
| 1.291.0 | 1 / 1 |
v1.359.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.358.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.357.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.356.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.355.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.354.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.353.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.353.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.352.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.351.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.351.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.350.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.349.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.348.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.348.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.347.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.347.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.346.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.345.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.344.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.343.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.342.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.341.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.340.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.339.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.338.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.337.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.336.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.335.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.334.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.333.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.332.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.331.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.330.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.329.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.329.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.328.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.327.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.326.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.325.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.324.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.323.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.322.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.321.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.320.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.319.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.318.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.317.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.316.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.315.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.314.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.313.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.312.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.312.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.311.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.311.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.310.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.309.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.308.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.307.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.306.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.305.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.304.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.303.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.302.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.301.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.300.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.299.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.298.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.297.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.296.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.296.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.295.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.294.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.293.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.292.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.291.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.