@akanjs/ui
This package is a sub-library of akanjs. For more information, please refer to [@akanjs/cli](https://www.npmjs.com/package/@akanjs/cli) and the [Akan.js Github](https://github.com/akan-team/akanjs).
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal org UI library; sparse metadata is consistent across versions, not indicative of spam/malware. | ai | |
| dependencies | unvetted-dep:react-spring | AI (dependencies): react-spring is a well-known animation library; stable dependency for this UI package. | ai | |
| dependencies | unvetted-dep:@react-spring/web | AI (dependencies): @react-spring/web is the official web target of react-spring; stable dependency for this UI package. | ai | |
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped UI library; Levenshtein match to joi is a false positive. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped UI library; Levenshtein match to yup is a false positive. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped UI library; Levenshtein match to uuid is a false positive. | ai | |
| phantom-deps | phantom-dep:react-easy-crop | AI (phantom-deps): react-easy-crop declared dep; referenced in config files, stable false positive. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): clsx is a declared dep used in config/style context; stable false positive for this UI package. | ai | |
| typosquat | typosquat.levenshtein:pg | AI (typosquat): Scoped UI library; Levenshtein match to pg is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped UI library; Levenshtein match to qs is a false positive. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.0.21 | 21 / 0 | |
| 1.0.20 | 21 / 0 | |
| 1.0.19 | 21 / 0 | |
| 1.0.18 | 21 / 0 | |
| 1.0.17 | 21 / 0 | |
| 1.0.16 | 21 / 0 | |
| 1.0.15 | 21 / 0 | |
| 1.0.14 | 21 / 0 | |
| 1.0.13 | 21 / 0 | |
| 1.0.12 | 21 / 0 | |
| 1.0.11 | 21 / 0 | |
| 1.0.10 | 21 / 0 | |
| 1.0.9 | 21 / 0 | |
| 1.0.6 | 21 / 0 | |
| 1.0.2 | 21 / 0 | |
| 0.9.59 | 21 / 0 | |
| 0.9.58 | 21 / 0 | |
| 0.9.57 | 21 / 0 | |
| 0.9.56 | 21 / 0 | |
| 0.9.55 | 21 / 0 |
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.57
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.56
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.