@gnome-ui/layout
Full-page layout shell components following the GNOME Human Interface Guidelines
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/components/AdaptiveLayout/AdaptiveLayout.cjs | AI (source-diff): Standard Vite/Rollup minified CJS bundle output; readable React component logic, no obfuscation. | ai | |
| phantom-deps | phantom-dep:@gnome-ui/core | AI (phantom-deps): @gnome-ui/core is a same-org sibling dependency; phantom detection is expected for monorepo-style packages where deps may be used indirectly or at build time. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 1.29.0 | 2 / 21 | |
| 1.28.3 | 2 / 21 | |
| 1.28.2 | 2 / 21 | |
| 1.28.1 | 2 / 21 | |
| 1.28.0 | 2 / 21 | |
| 1.27.0 | 2 / 21 | |
| 1.26.0 | 2 / 21 | |
| 1.25.0 | 2 / 21 | |
| 1.24.0 | 2 / 21 | |
| 1.23.0 | 2 / 21 | |
| 1.22.1 | 2 / 21 | |
| 1.22.0 | 2 / 21 | |
| 1.21.1 | 2 / 21 | |
| 1.21.0 | 2 / 21 | |
| 1.20.0 | 2 / 21 | |
| 1.19.0 | 1 / 22 | |
| 1.18.0 | 1 / 22 | |
| 1.17.0 | 1 / 22 | |
| 1.16.0 | 1 / 22 | |
| 1.15.0 | 1 / 22 | |
| 1.14.0 | 1 / 22 | |
| 1.13.1 | 1 / 22 | |
| 1.13.0 | 1 / 22 | |
| 1.12.1 | 1 / 22 | |
| 1.12.0 | 1 / 22 | |
| 1.11.4 | 1 / 22 | |
| 1.11.3 | 1 / 21 | |
| 1.11.2 | 1 / 21 | |
| 1.11.1 | 1 / 21 | |
| 1.11.0 | 1 / 21 | |
| 1.10.0 | 1 / 21 | |
| 1.9.0 | 1 / 21 | |
| 1.8.0 | 1 / 21 | |
| 1.7.0 | 1 / 21 | |
| 1.6.0 | 1 / 21 | |
| 1.5.0 | 1 / 21 | |
| 1.4.0 | 1 / 21 | |
| 1.3.0 | 1 / 20 | |
| 1.2.0 | 1 / 20 | |
| 1.1.0 | 1 / 20 | |
| 1.0.0 | 1 / 20 |
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.