@sqlrooms/layout
Layout slice and mosaic utilities for SQLRooms panel-based UIs.
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Scoped monorepo package; missing description is a stable cosmetic issue, not a malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all versions; not a security risk for this established package. | ai |
Versions (showing 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 0.28.0 | 6 / 0 | |
| 0.27.0 | 6 / 0 | |
| 0.26.0 | 7 / 0 | |
| 0.24.27 | 7 / 0 | |
| 0.24.26 | 7 / 0 | |
| 0.24.25 | 7 / 0 | |
| 0.24.24 | 7 / 0 | |
| 0.24.23 | 7 / 0 | |
| 0.24.22 | 7 / 0 | |
| 0.24.21 | 7 / 0 | |
| 0.24.20 | 7 / 0 | |
| 0.24.19 | 7 / 0 | |
| 0.24.18 | 7 / 0 | |
| 0.24.17 | 7 / 0 | |
| 0.24.16 | 7 / 0 | |
| 0.24.15 | 7 / 0 | |
| 0.24.14 | 7 / 0 | |
| 0.24.13 | 7 / 0 | |
| 0.24.12 | 7 / 0 | |
| 0.24.11 | 7 / 0 | |
| 0.24.10 | 7 / 0 | |
| 0.24.9 | 7 / 0 | |
| 0.24.8 | 7 / 0 | |
| 0.24.7 | 7 / 0 | |
| 0.24.6 | 7 / 0 | |
| 0.24.5 | 7 / 0 | |
| 0.24.4 | 7 / 0 | |
| 0.24.3 | 7 / 0 | |
| 0.24.2 | 7 / 0 | |
| 0.24.1 | 7 / 0 | |
| 0.24.0 | 7 / 0 | |
| 0.23.0 | 7 / 0 | |
| 0.22.0 | 7 / 0 | |
| 0.21.0 | 7 / 0 | |
| 0.20.0 | 4 / 0 | |
| 0.19.2 | 4 / 0 | |
| 0.19.1 | 4 / 0 | |
| 0.19.0 | 4 / 0 | |
| 0.18.1 | 2 / 0 | |
| 0.18.0 | 2 / 0 | |
| 0.17.0 | 2 / 0 | |
| 0.16.4 | 2 / 0 | |
| 0.16.3 | 2 / 0 | |
| 0.16.2 | 2 / 0 | |
| 0.16.1 | 2 / 0 | |
| 0.16.0 | 2 / 0 | |
| 0.15.0 | 2 / 0 | |
| 0.14.0 | 2 / 0 | |
| 0.13.2 | 2 / 0 | |
| 0.13.1 | 2 / 0 | |
| 0.13.0 | 2 / 0 | |
| 0.12.0 | 2 / 0 | |
| 0.11.0 | 2 / 0 | |
| 0.10.1 | 2 / 0 | |
| 0.10.0 | 2 / 0 | |
| 0.9.3 | 2 / 0 | |
| 0.9.2 | 2 / 0 | |
| 0.9.1 | 2 / 0 | |
| 0.9.0 | 2 / 0 | |
| 0.8.1 | 2 / 0 | |
| 0.8.0 | 2 / 0 | |
| 0.7.0 | 2 / 0 | |
| 0.6.0 | 2 / 0 | |
| 0.5.1 | 2 / 0 | |
| 0.5.0 | 2 / 0 | |
| 0.4.2 | 2 / 0 | |
| 0.4.1 | 2 / 0 | |
| 0.4.0 | 2 / 0 | |
| 0.3.0 | 2 / 0 | |
| 0.1.0 | 2 / 0 | |
| 0.0.3 | 2 / 0 | |
| 0.0.2 | 2 / 0 | |
| 0.0.1 | 2 / 0 |
v0.16.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.