@akinon/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, 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance across akinon package suite; stable false positive for this publisher. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Org-internal package; missing description is consistent across akinon's package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal UI library from established akinon publisher; missing metadata is cosmetic, not a security signal. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.7.14 | 6 / 11 | |
| 1.7.13 | 6 / 11 | |
| 1.7.12 | 6 / 11 | |
| 1.7.11 | 6 / 11 | |
| 1.7.10 | 6 / 11 | |
| 1.7.9 | 6 / 11 | |
| 1.7.8 | 6 / 11 | |
| 1.7.7 | 6 / 11 | |
| 1.7.6 | 6 / 6 | |
| 1.7.5 | 6 / 6 | |
| 1.7.4 | 6 / 6 | |
| 1.7.3 | 6 / 6 | |
| 1.7.2 | 6 / 6 | |
| 1.7.1 | 6 / 6 | |
| 1.7.0 | 6 / 6 | |
| 1.6.1 | 6 / 6 | |
| 1.6.0 | 6 / 6 | |
| 1.5.0 | 6 / 6 | |
| 1.4.1 | 5 / 6 | |
| 1.4.0 | 5 / 6 | |
| 1.3.0 | 5 / 6 | |
| 1.2.0 | 4 / 7 | |
| 1.1.0 | 2 / 9 | |
| 1.0.1 | 2 / 9 | |
| 1.0.0 | 2 / 6 |
v1.7.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.