@foundrykit/primitives
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:@radix-ui/react-avatar | AI (dependencies): @radix-ui/react-avatar is a well-established Radix UI primitive; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Declared as runtime dep, likely used in config/type files; stable false positive for this component library. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Declared runtime dep used in build config; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Declared as peer and runtime dep; phantom-dep heuristic misfires on peer deps in component libraries. | ai | |
| phantom-deps | phantom-dep:next-themes | AI (phantom-deps): Declared runtime dep for theme support; stable false positive for this UI library. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Declared runtime dep used in utility functions; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.0.5 | 25 / 9 | |
| 2.0.4 | 25 / 9 | |
| 2.0.3 | 25 / 9 | |
| 2.0.2 | 25 / 9 | |
| 2.0.1 | 25 / 9 | |
| 2.0.0 | 25 / 9 | |
| 1.0.15 | 25 / 9 |
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.