foundation-sites
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
gakimballkbal11rafibombjoeworkman
Keywords
cssscsssassjsresponsivemobile-firstframeworkeyeglass-modulehandlebars-helper-relhandlebars-helper-slugify
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Usage is in .husky git-hook dev scripts, not runtime code shipped to consumers. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is in gulp build tooling (customizer task), not in the distributed runtime bundle. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 6.9.0 | 0 / 66 |
v6.9.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.