@ankhorage/zora
Opinionated React Native and React Native Web UI kit built on @ankhorage/surface.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@ankhorage/color-theory | AI (dependencies): Same-org package (@ankhorage); consistent with monorepo dependency pattern replacing culori. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version bump (0.16.2 -> 1.3.0) for a UI kit; large source expansion is expected. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from manual publish (artiphishle) to GitHub Actions CI with SLSA provenance attestation; legitimate automation handoff. | ai | |
| typosquat | typosquat.levenshtein:koa | AI (typosquat): Scoped UI kit package; name similarity to koa is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped UI kit package; name similarity to cors is coincidental, not impersonation. | ai | |
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped UI kit package; name similarity to zod is coincidental, not impersonation. | ai |
Versions (showing 8 of 108)
| Version | Deps | Published |
|---|---|---|
| 0.1.3 | 1 / 11 | |
| 0.1.2 | 1 / 11 | |
| 0.1.1 | 1 / 11 | |
| 0.1.0 | 1 / 11 | |
| 0.0.4 | 1 / 10 | |
| 0.0.3 | 1 / 10 | |
| 0.0.2 | 1 / 10 | |
| 0.0.1 | 1 / 10 |
v0.1.3
2 findingsThis version was published by a different npm account than previous versions on 2026-04-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
2 findingsThis version was published by a different npm account than previous versions on 2026-04-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.