@salesforce/lds-adapters-industries-fieldset
Field Set
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by Salesforce org publisher consolidation to lwc-admin; no malicious payload indicators. | ai | |
| phantom-deps | phantom-dep:@salesforce/lds-bindings | AI (phantom-deps): Same org scope; likely consumed indirectly via the Salesforce LDS runtime rather than direct import. | ai |
Versions (showing 100 of 157)
| Version | Deps | Published |
|---|---|---|
| 1.450.0 | 1 / 2 | |
| 1.449.0 | 1 / 2 | |
| 1.448.0 | 1 / 2 | |
| 1.447.1 | 1 / 2 | |
| 1.447.0 | 1 / 2 | |
| 1.446.0 | 1 / 2 | |
| 1.445.0 | 1 / 2 | |
| 1.444.0 | 1 / 2 | |
| 1.443.0 | 1 / 2 | |
| 1.442.0 | 1 / 2 | |
| 1.441.0 | 1 / 2 | |
| 1.440.0 | 1 / 2 | |
| 1.439.0 | 1 / 2 | |
| 1.438.1 | 1 / 2 | |
| 1.438.0 | 1 / 2 | |
| 1.437.0 | 1 / 2 | |
| 1.436.0 | 1 / 2 | |
| 1.435.1 | 1 / 2 | |
| 1.435.0 | 1 / 2 | |
| 1.434.0 | 1 / 2 | |
| 1.433.0 | 1 / 2 | |
| 1.432.0 | 1 / 2 | |
| 1.431.0 | 1 / 2 | |
| 1.430.0 | 1 / 2 | |
| 1.429.0 | 1 / 2 | |
| 1.428.0 | 1 / 2 | |
| 1.420.0 | 1 / 2 | |
| 1.409.0 | 1 / 2 | |
| 1.405.0 | 1 / 2 | |
| 1.404.0 | 1 / 2 | |
| 1.403.0 | 1 / 2 | |
| 1.402.0 | 1 / 2 | |
| 1.401.0 | 1 / 2 | |
| 1.400.0 | 1 / 2 | |
| 1.399.0 | 1 / 2 | |
| 1.398.0 | 1 / 2 | |
| 1.397.0 | 1 / 2 | |
| 1.396.0 | 1 / 2 | |
| 1.395.0 | 1 / 2 | |
| 1.394.0 | 1 / 2 | |
| 1.393.0 | 1 / 2 | |
| 1.392.0 | 1 / 2 | |
| 1.391.0 | 1 / 2 | |
| 1.390.0 | 1 / 2 | |
| 1.389.2 | 1 / 2 | |
| 1.389.1 | 1 / 2 | |
| 1.389.0 | 1 / 2 | |
| 1.388.0 | 1 / 2 | |
| 1.387.0 | 1 / 2 | |
| 1.386.0 | 1 / 2 | |
| 1.385.0 | 1 / 2 | |
| 1.384.0 | 1 / 2 | |
| 1.383.0 | 1 / 2 | |
| 1.382.0 | 1 / 2 | |
| 1.381.0 | 1 / 2 | |
| 1.380.0 | 1 / 2 | |
| 1.379.1 | 1 / 2 | |
| 1.379.0 | 1 / 2 | |
| 1.378.0 | 1 / 2 | |
| 1.377.1 | 1 / 2 | |
| 1.377.0 | 1 / 2 | |
| 1.376.0 | 1 / 2 | |
| 1.375.0 | 1 / 2 | |
| 1.374.0 | 1 / 2 | |
| 1.373.0 | 1 / 2 | |
| 1.372.1 | 1 / 2 | |
| 1.372.0 | 1 / 2 | |
| 1.371.0 | 1 / 2 | |
| 1.370.0 | 1 / 2 | |
| 1.369.0 | 1 / 2 | |
| 1.368.0 | 1 / 2 | |
| 1.367.0 | 1 / 2 | |
| 1.366.0 | 1 / 2 | |
| 1.365.0 | 1 / 2 | |
| 1.364.0 | 1 / 2 | |
| 1.363.0 | 1 / 2 | |
| 1.362.0 | 1 / 2 | |
| 1.361.0 | 1 / 2 | |
| 1.360.1 | 1 / 2 | |
| 1.360.0 | 1 / 2 | |
| 1.359.0 | 1 / 2 | |
| 1.358.0 | 1 / 2 | |
| 1.357.0 | 1 / 2 | |
| 1.356.0 | 1 / 2 | |
| 1.355.0 | 1 / 2 | |
| 1.354.0 | 1 / 2 | |
| 1.353.1 | 1 / 2 | |
| 1.353.0 | 1 / 2 | |
| 1.352.0 | 1 / 2 | |
| 1.351.1 | 1 / 2 | |
| 1.351.0 | 1 / 2 | |
| 1.350.0 | 1 / 2 | |
| 1.349.0 | 1 / 2 | |
| 1.348.1 | 1 / 2 | |
| 1.348.0 | 1 / 2 | |
| 1.347.1 | 1 / 2 | |
| 1.347.0 | 1 / 2 | |
| 1.346.0 | 1 / 2 | |
| 1.345.0 | 1 / 2 | |
| 1.344.0 | 1 / 2 |
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.