@targetprocess/layout-management-client
Js client for layout-management 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
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.12.6 | 0 / 2 | |
| 3.12.5 | 0 / 2 | |
| 3.12.2 | 0 / 2 | |
| 3.12.1 | 0 / 2 | |
| 3.12.0 | 0 / 2 | |
| 3.11.0 | 0 / 2 | |
| 3.10.0 | 0 / 2 | |
| 3.9.4 | 0 / 3 | |
| 3.9.3 | 0 / 3 | |
| 3.9.2 | 0 / 3 | |
| 3.9.1 | 0 / 3 | |
| 3.9.0 | 0 / 3 | |
| 3.8.14 | 0 / 3 | |
| 3.8.9 | 0 / 3 | |
| 3.8.6 | 0 / 3 | |
| 3.8.5 | 0 / 3 | |
| 3.8.0 | 0 / 3 | |
| 3.6.9 | 0 / 3 | |
| 3.6.5 | 0 / 3 |
v3.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.