@akinon/ui-system
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@akinon/ui-hooks | AI (dependencies): Sibling package from the same @akinon org; stable false positive for this package family. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Akinon org publisher with established approval history; dormancy consistent with org release cadence, not takeover indicators. | ai | |
| provenance | no-provenance | AI (provenance): Akinon org consistently publishes without provenance; stable false positive for this package family. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.3.1 | 3 / 5 | |
| 1.3.0 | 3 / 5 | |
| 1.2.9 | 3 / 5 | |
| 1.2.8 | 3 / 5 | |
| 1.2.1 | 3 / 5 | |
| 1.1.3 | 3 / 5 | |
| 1.1.2 | 3 / 5 | |
| 1.1.1 | 3 / 5 | |
| 1.1.0 | 3 / 5 | |
| 1.0.2 | 3 / 5 |
v1.3.1
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.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.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.
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.