@epicdm/flowstate-ui
Shared UI components for FlowState apps (shadcn/ui)
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@radix-ui/react-avatar | AI (dependencies): @radix-ui packages are well-known, widely-used React primitives; stable false positive for this UI library. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-hover-card | AI (dependencies): @radix-ui packages are well-known, widely-used React primitives; stable false positive for this UI library. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is a runtime dep used via config/re-export pattern in this UI lib; stable false positive. | ai | |
| phantom-deps | phantom-dep:@hookform/resolvers | AI (phantom-deps): @hookform/resolvers is a runtime dep used via config/re-export pattern; stable false positive. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.0.7 | 40 / 15 | |
| 1.0.6 | 40 / 15 | |
| 1.0.5 | 40 / 15 | |
| 1.0.4 | 40 / 15 | |
| 1.0.3 | 40 / 15 | |
| 1.0.2 | 40 / 15 | |
| 1.0.1 | 40 / 15 | |
| 1.0.0 | 40 / 15 |
v1.0.7
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.