@codaco/fresco-ui
Fresco UI components, styles, and utilities
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): jthrilly is an established publisher in the same org; transition appears legitimate. | ai | |
| dependencies | unvetted-dep:cva | AI (dependencies): cva is a well-known class-variance-authority successor; pinned beta version is intentional for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established @codaco org package; lack of Sigstore attestation is a process gap, not a security signal for this publisher. | ai | |
| phantom-deps | phantom-dep:@codaco/tailwind-config | AI (phantom-deps): Same-org config package; phantom-dep is a false positive for build-time config deps. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped org-internal UI library; sparse metadata is expected for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@tiptap/pm | AI (phantom-deps): @tiptap/pm is listed as a direct dependency in package.json; phantom-dep is a false positive here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 2.10.0 | 24 / 28 | |
| 2.4.0 | 23 / 27 | |
| 2.1.0 | 23 / 26 | |
| 2.0.1 | 24 / 25 | |
| 2.0.0 | 24 / 24 | |
| 1.0.0 | 24 / 24 | |
| 0.3.0 | 24 / 24 | |
| 0.2.1 | 25 / 24 | |
| 0.2.0 | 25 / 24 | |
| 0.1.1 | 24 / 24 |
v2.10.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.