@salesforce/lds-adapters-platform-applications
salesforce applications
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 trusted Salesforce org publisher with 1821 approved packages; transition from dme722 is a known org-level consolidation pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): salesforce-admin addition aligns with Salesforce org-level maintainer consolidation; no malicious indicators. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Mass removal consistent with org-level maintainer consolidation; no code changes accompany the transition. | ai | |
| phantom-deps | phantom-dep:@salesforce/lds-bindings | AI (phantom-deps): Same-org dependency used at runtime in the built dist; phantom-dep heuristic fires on generated artifacts. | ai |
Versions (showing 26 of 126)
| 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 |
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.