Skip to content

Security: Foscat/Layout-Style-CSS

Security

SECURITY.md

Security Policy

layout-style-css is a CSS-only layout package. It does not execute JavaScript at runtime, make network requests, process user input, store credentials, or read secrets.

Supported Versions

Version Supported
2.x Yes
1.1.x Migration support only
1.0.x No

Reporting A Vulnerability

Use GitHub security advisories for private reports when available. If advisories are not enabled, open a minimal GitHub issue that avoids public exploit details and asks for a private coordination path.

Please include:

  • affected version and package entrypoint
  • affected selector, file, or demo behavior
  • reproduction steps
  • expected impact
  • whether the issue affects package consumers, the demo, or GitHub Pages deployment

Security Model

The primary security risks for this package are supply-chain and documentation risks:

  • incorrect package exports that make consumers import unexpected files
  • malformed CDN examples that point to wrong assets
  • accidental runtime JavaScript or network behavior in docs or demo code
  • package contents that include secrets, build caches, or unrelated local files
  • CSS that hides important controls or breaks keyboard-visible flows in the demo

The release gate verifies package contents, README imports, documentation links, CSS contracts, GitHub Pages artifact structure, and rendered behavior in Chromium, Firefox, and WebKit.

Dependency Checks

Run the local dependency audit before publishing:

npm audit --audit-level=moderate

The package also uses npm run release:verify to run build, lint, static, Pages, cross-browser, pack dry-run, and publish dry-run checks.

The npm workflow validates a strict tag, exact peeled commit, protected-main ancestry, and package version before dependency lifecycle code runs. Publishing requires the protected npm GitHub Environment, emits npm provenance, and exposes NODE_AUTH_TOKEN only to the publish step. npm trusted publishing and immutable commit SHA pins for GitHub Actions remain follow-up hardening work.

The demo's two exact-version companion CDN fixtures use SHA-384 subresource integrity with anonymous CORS. Their hashes are derived from the pinned local development fixtures and enforced by the rendered smoke contract.

There aren't any published security advisories