@akinon/ui-alert
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal scoped UI component library; missing metadata is consistent across all akinon packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across akinon scoped packages; not a malware indicator here. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across akinon package family; consistent with their publishing workflow. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.2.14 | 4 / 5 | |
| 1.2.13 | 4 / 5 | |
| 1.2.12 | 4 / 5 | |
| 1.2.11 | 4 / 5 | |
| 1.2.10 | 4 / 5 | |
| 1.2.9 | 4 / 5 | |
| 1.2.8 | 4 / 5 | |
| 1.2.7 | 4 / 5 | |
| 1.2.6 | 4 / 5 | |
| 1.2.5 | 4 / 5 | |
| 1.2.4 | 4 / 5 | |
| 1.2.3 | 4 / 5 | |
| 1.2.2 | 4 / 5 | |
| 1.2.1 | 4 / 5 | |
| 1.2.0 | 4 / 5 | |
| 1.1.2 | 4 / 5 | |
| 1.1.1 | 4 / 5 | |
| 1.1.0 | 4 / 5 | |
| 1.0.2 | 3 / 5 | |
| 1.0.1 | 3 / 5 | |
| 1.0.0 | 3 / 5 |
v1.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v1.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.
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.