@salesforce/lds-adapters-uiapi
Wire adapters for record related UI API endpoints
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@salesforce/lds-adapters-onestore-graphql | AI (dependencies): Same @salesforce org scope, version-locked sibling dependency; consistent pattern across this package family. | ai | |
| phantom-deps | phantom-dep:@salesforce/lds-adapters-onestore-graphql | AI (phantom-deps): Same org scope sibling dep; declared as runtime dependency, phantom-dep heuristic is a false positive here. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.437.0 | 4 / 3 | |
| 1.436.0 | 4 / 3 | |
| 1.435.0 | 4 / 3 | |
| 1.434.0 | 4 / 3 | |
| 1.433.0 | 4 / 3 | |
| 1.431.0 | 4 / 3 | |
| 1.430.0 | 4 / 3 | |
| 1.429.0 | 4 / 3 | |
| 1.428.0 | 4 / 3 |
v1.437.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.436.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.435.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.434.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.433.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.431.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.430.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.429.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.428.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.