@nomos-ui/layout
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@nomos-ui/common | AI (phantom-deps): Same-org scope dep likely re-exported; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@nomos-ui/uanela-redux-next | AI (phantom-deps): Same-org scope dep likely re-exported; stable false positive for this monorepo package. | ai | |
| provenance | no-provenance | AI (provenance): Common for small UI libraries; no other risk signals present. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.0.7 | 5 / 13 | |
| 0.0.6 | 1 / 13 | |
| 0.0.5 | 1 / 13 | |
| 0.0.4 | 1 / 13 | |
| 0.0.3 | 1 / 13 | |
| 0.0.2 | 0 / 13 | |
| 0.0.1 | 0 / 13 |
v0.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.