@salesforce/lds-runtime-browser
LDS runtime for browser environments (depends on IndexedDB and Fetch API).
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:@luvio/engine | AI (dependencies): Salesforce-internal Luvio ecosystem dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@luvio/environments | AI (dependencies): Salesforce-internal Luvio ecosystem dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@luvio/durable-store-idb | AI (dependencies): Salesforce-internal Luvio ecosystem dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@luvio/network-adapter-fetch | AI (dependencies): Salesforce-internal Luvio ecosystem dep; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@salesforce/lds-network-adapter | AI (dependencies): Salesforce-internal LDS ecosystem dep; stable pattern across all versions of this package. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 1.441.0 | 7 / 0 | |
| 1.440.0 | 7 / 0 | |
| 1.439.0 | 7 / 0 | |
| 1.438.1 | 7 / 0 | |
| 1.438.0 | 7 / 0 | |
| 1.437.0 | 7 / 0 | |
| 1.436.0 | 7 / 0 | |
| 1.435.1 | 7 / 0 | |
| 1.435.0 | 7 / 0 | |
| 1.434.0 | 7 / 0 | |
| 1.405.0 | 7 / 0 | |
| 1.404.0 | 7 / 0 | |
| 1.403.0 | 7 / 0 | |
| 1.402.0 | 7 / 0 | |
| 1.401.0 | 7 / 0 | |
| 1.400.0 | 7 / 0 | |
| 1.399.0 | 7 / 0 | |
| 1.398.0 | 7 / 0 | |
| 1.397.0 | 7 / 0 | |
| 1.396.0 | 7 / 0 | |
| 1.395.0 | 7 / 0 | |
| 1.394.0 | 7 / 0 | |
| 1.393.0 | 7 / 0 | |
| 1.392.0 | 7 / 0 | |
| 1.391.0 | 7 / 0 | |
| 1.390.0 | 7 / 0 | |
| 1.389.2 | 7 / 0 | |
| 1.389.1 | 7 / 0 | |
| 1.389.0 | 7 / 0 | |
| 1.388.0 | 7 / 0 | |
| 1.387.0 | 7 / 0 | |
| 1.386.0 | 7 / 0 | |
| 1.385.0 | 7 / 0 | |
| 1.384.0 | 7 / 0 | |
| 1.383.0 | 7 / 0 | |
| 1.382.0 | 7 / 0 | |
| 1.381.0 | 7 / 0 | |
| 1.380.0 | 7 / 0 | |
| 1.379.1 | 7 / 0 | |
| 1.379.0 | 7 / 0 | |
| 1.378.0 | 7 / 0 | |
| 1.377.1 | 7 / 0 | |
| 1.377.0 | 7 / 0 | |
| 1.376.0 | 7 / 0 | |
| 1.375.0 | 7 / 0 | |
| 1.374.0 | 7 / 0 | |
| 1.373.0 | 7 / 0 | |
| 1.372.1 | 7 / 0 | |
| 1.372.0 | 7 / 0 | |
| 1.371.0 | 7 / 0 | |
| 1.370.0 | 7 / 0 |
v1.441.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.440.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.439.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.438.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.438.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1
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.405.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.404.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.403.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.402.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.401.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.400.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.399.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.398.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.397.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.396.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.395.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.394.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.393.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.392.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.391.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.390.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.389.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.389.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.389.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.388.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.387.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.386.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.385.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.384.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.383.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.382.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.381.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.380.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.379.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.379.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.378.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.377.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.377.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.376.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.375.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.374.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.373.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.372.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.372.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.371.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.370.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.