@foundrykit/blocks
A collection of pre-built page sections and content blocks for rapid website development. These blocks provide complete, customizable sections that can be easily integrated into any page layout.
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 | no-provenance | AI (provenance): Consistent across all versions of this package; no other risk signals present. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Consistent pattern across this org's releases; no malicious signals accompany the rapid publish. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Peer dep declared in both deps and peerDeps; config-only reference is expected. | ai | |
| phantom-deps | phantom-dep:tailwind-merge | AI (phantom-deps): Declared runtime dep used in Tailwind-based component library; stable false positive. | ai | |
| phantom-deps | phantom-dep:clsx | AI (phantom-deps): Declared runtime dep; likely used in compiled output or config — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@foundrykit/components | AI (phantom-deps): Same-org dep; consistent pattern across this package's versions. | ai | |
| phantom-deps | phantom-dep:@foundrykit/animation | AI (phantom-deps): Same-org dep; likely re-exported or used indirectly — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:next | AI (phantom-deps): Next.js referenced in config files for this Next-based component library; not a real phantom dep. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.0.9 | 12 / 8 | |
| 2.0.8 | 12 / 8 | |
| 2.0.7 | 12 / 8 | |
| 2.0.6 | 12 / 8 | |
| 2.0.5 | 12 / 8 | |
| 2.0.4 | 12 / 8 | |
| 2.0.3 | 12 / 8 | |
| 2.0.2 | 12 / 8 | |
| 2.0.1 | 12 / 8 | |
| 2.0.0 | 12 / 8 | |
| 1.2.0 | 12 / 8 | |
| 1.1.0 | 12 / 8 | |
| 1.0.25 | 12 / 8 |
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.