@salesforce/lds-instrumentation
Instrumentation utils for Lightning Data Service
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@salesforce/lds-bindings | AI (phantom-deps): Same org scope; likely a peer/platform dep resolved outside npm graph in Salesforce's build system. | ai | |
| phantom-deps | phantom-dep:@salesforce/lds-default-luvio | AI (phantom-deps): Same org scope; same rationale as lds-bindings — platform-resolved dep. | ai |
Versions (showing 100 of 157)
| Version | Deps | Published |
|---|---|---|
| 1.450.0 | 5 / 3 | |
| 1.449.0 | 5 / 3 | |
| 1.448.0 | 5 / 3 | |
| 1.447.1 | 5 / 3 | |
| 1.447.0 | 5 / 3 | |
| 1.446.0 | 5 / 3 | |
| 1.445.0 | 5 / 3 | |
| 1.444.0 | 5 / 3 | |
| 1.443.0 | 5 / 3 | |
| 1.442.0 | 5 / 3 | |
| 1.441.0 | 5 / 3 | |
| 1.440.0 | 5 / 3 | |
| 1.439.0 | 5 / 3 | |
| 1.438.1 | 5 / 3 | |
| 1.438.0 | 5 / 3 | |
| 1.437.0 | 5 / 3 | |
| 1.436.0 | 5 / 3 | |
| 1.435.1 | 5 / 3 | |
| 1.435.0 | 5 / 3 | |
| 1.434.0 | 5 / 3 | |
| 1.433.0 | 5 / 3 | |
| 1.432.0 | 5 / 3 | |
| 1.431.0 | 5 / 3 | |
| 1.430.0 | 5 / 3 | |
| 1.429.0 | 5 / 3 | |
| 1.428.0 | 5 / 3 | |
| 1.410.1 | 5 / 3 | |
| 1.410.0 | 5 / 3 | |
| 1.405.0 | 5 / 3 | |
| 1.404.0 | 5 / 3 | |
| 1.403.0 | 5 / 3 | |
| 1.402.0 | 5 / 3 | |
| 1.401.0 | 5 / 3 | |
| 1.400.0 | 5 / 3 | |
| 1.399.0 | 5 / 3 | |
| 1.398.0 | 5 / 3 | |
| 1.397.0 | 5 / 3 | |
| 1.396.0 | 5 / 3 | |
| 1.395.0 | 5 / 3 | |
| 1.394.0 | 5 / 3 | |
| 1.393.0 | 5 / 3 | |
| 1.392.0 | 5 / 3 | |
| 1.391.0 | 5 / 3 | |
| 1.390.0 | 5 / 3 | |
| 1.389.2 | 5 / 3 | |
| 1.389.1 | 5 / 3 | |
| 1.389.0 | 5 / 3 | |
| 1.388.0 | 5 / 3 | |
| 1.387.0 | 5 / 3 | |
| 1.386.0 | 5 / 3 | |
| 1.385.0 | 5 / 3 | |
| 1.384.0 | 5 / 3 | |
| 1.383.0 | 5 / 3 | |
| 1.382.0 | 5 / 3 | |
| 1.381.0 | 5 / 3 | |
| 1.380.0 | 5 / 3 | |
| 1.379.1 | 5 / 3 | |
| 1.379.0 | 5 / 3 | |
| 1.378.0 | 5 / 3 | |
| 1.377.1 | 5 / 3 | |
| 1.377.0 | 5 / 3 | |
| 1.376.0 | 5 / 3 | |
| 1.375.0 | 5 / 3 | |
| 1.374.0 | 5 / 3 | |
| 1.373.0 | 5 / 3 | |
| 1.372.1 | 5 / 3 | |
| 1.372.0 | 5 / 3 | |
| 1.371.0 | 5 / 3 | |
| 1.370.0 | 5 / 3 | |
| 1.369.0 | 5 / 3 | |
| 1.368.0 | 5 / 3 | |
| 1.367.0 | 5 / 3 | |
| 1.366.0 | 5 / 3 | |
| 1.365.0 | 5 / 3 | |
| 1.364.0 | 5 / 3 | |
| 1.363.0 | 5 / 3 | |
| 1.362.0 | 5 / 3 | |
| 1.361.0 | 5 / 3 | |
| 1.360.1 | 5 / 3 | |
| 1.360.0 | 5 / 3 | |
| 1.359.0 | 5 / 3 | |
| 1.358.0 | 5 / 3 | |
| 1.357.0 | 5 / 3 | |
| 1.356.0 | 5 / 3 | |
| 1.355.0 | 5 / 3 | |
| 1.354.0 | 5 / 3 | |
| 1.353.1 | 5 / 3 | |
| 1.353.0 | 5 / 3 | |
| 1.352.0 | 5 / 3 | |
| 1.351.1 | 5 / 3 | |
| 1.351.0 | 5 / 3 | |
| 1.350.0 | 5 / 3 | |
| 1.349.0 | 5 / 3 | |
| 1.348.1 | 5 / 3 | |
| 1.348.0 | 5 / 3 | |
| 1.347.1 | 5 / 3 | |
| 1.347.0 | 5 / 3 | |
| 1.346.0 | 5 / 3 | |
| 1.345.0 | 5 / 3 | |
| 1.344.0 | 5 / 3 |
v1.450.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.449.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.448.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.447.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.447.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.