@foundrykit/components
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:@foundrykit/utils | AI (dependencies): Same-org package from the same publisher; consistent with the rest of the @foundrykit monorepo dependencies. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): No material changes vs prior version; consistent monorepo publishing pattern reduces takeover concern. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @foundrykit/components versions; no other risk signals present. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Component library re-exports or uses zod via config; declared dep is expected pattern. | ai | |
| phantom-deps | phantom-dep:@hookform/resolvers | AI (phantom-deps): Form library dep used via config/re-export pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Listed as both dep and peerDep; phantom-dep fires on config references, stable false positive. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Utility used in build/config context; stable false positive for this component library. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 17 / 8 | |
| 2.0.5 | 17 / 8 | |
| 2.0.4 | 17 / 8 | |
| 2.0.3 | 17 / 8 | |
| 2.0.2 | 17 / 8 | |
| 2.0.1 | 17 / 8 | |
| 2.0.0 | 17 / 8 | |
| 1.2.0 | 17 / 8 | |
| 1.1.0 | 17 / 8 |
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package 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.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.