@akinon/ui-tabs
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): Akinon internal component; missing description is a stable pattern across their packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Akinon's internal UI component packages consistently lack public metadata; not indicative of spam. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.0.13 | 4 / 5 | |
| 1.0.12 | 4 / 5 | |
| 1.0.11 | 4 / 5 | |
| 1.0.10 | 4 / 5 | |
| 1.0.9 | 4 / 5 | |
| 1.0.8 | 4 / 5 | |
| 1.0.7 | 4 / 5 | |
| 1.0.6 | 4 / 5 | |
| 1.0.5 | 4 / 5 | |
| 1.0.4 | 4 / 5 | |
| 1.0.3 | 4 / 5 | |
| 1.0.2 | 4 / 5 | |
| 1.0.1 | 4 / 5 | |
| 1.0.0 | 4 / 5 |
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.