Architecture

Reference Value
Subject and boundary Vulnerability reporting, repository and release supply-chain controls, security-relevant package contracts and the configuration surface. Product CSP, hosting and secrets stay in each product.
Verified source SECURITY.md, secret-scan.yml, release.yml, dependabot.yml and the trust-root test at tag v0.40.0. Verified tag v0.40.0, commit 43bba26a73dd0f7aa01cb7c8f37d697734b367ad, checked 2026-11-10; earlier pass checked November 7, 2026. Release attestation checked against v0.40.0 and v0.39.1 assets on 2026-11-10.
Support state Repository control configuration and package contracts at v0.40.0. Repository settings and deployed product security need separate live evidence.

Reporting and support

Report suspected vulnerabilities privately through GitHub private vulnerability reporting or by email to [email protected] with the subject [security], never in a public issue. Only the latest release is supported. Fixes ship as a new release; a published tag or Release is never changed. Defect reports use the bug form with the release tag from the product's package URLs.

Supply-chain controls

Control Mechanism
Action pinning Every external workflow and composite-action dependency is pinned to a commit SHA; the repository trust-root contract test fails otherwise. The browser job's Playwright container is pinned by digest.
Secret scanning gitleaks 8.30.1, downloaded with a SHA-256 check. Scans the pull request diff, the merge-group range in the main merge queue, pushed commits on main, and full history weekly (Monday 10:17 UTC) and on manual dispatch. Findings are redacted.
Code scanning CodeQL is outside the checked-in workflow directory. Current run status and repository settings must be inspected separately; source alone does not establish enabled settings.
Dependency updates Dependabot opens monthly grouped GitHub Actions and Bun-workspace updates, with at most three npm PRs. Root overrides pin brace-expansion, fast-uri, nanoid and postcss.
Install integrity CI and contributors install with --frozen-lockfile. Consumers pin release tarball URLs, and bun.lock records each tarball's integrity.
Release integrity The tag-triggered workflow has contents, id-token and attestations write permissions, runs only in yesid-dev/yesid.design, checks out without persisted credentials, attests build provenance for the eight tarballs and publishes from a draft only after every upload. Immutable releases lock the published Release.
Review CODEOWNERS assigns every path to the maintainer. The CI workflow declares ci as the required check; branch-protection settings live outside the repository.

Consumers verify a v0.40.0 or later tarball with gh attestation verify <tarball> --repo yesid-dev/yesid.design and a Release with gh release verify <tag>. v0.36.1 to v0.39.1 were signed as mgkdante/yesid.design, and v0.36.0 and earlier as mgkdante/yesid.dev-design; verify those with --owner mgkdante --signer-repo <that repository>. Packed sibling peers in v0.40.0 tarballs use yesid-dev/yesid.design URLs (#202).

Security-relevant package contracts

Contract Owner split
SECURITY_HEADERS (@yesid/seo-kit/headers) Package-owned standard headers. Products own CSP serialization, directives and any feature or HSTS override. The package has no CSP serializer export.
Theme boot script (@yesid/ui/head) and @yesid/ui/boot.json Theme and section geometry execute before paint. A hash-mode script-src must allow the exact v0.40.0 script hash below. Consumers import boot.json during their build. A CSP relying on 'unsafe-inline' must not add a hash, since any hash disables that source.
JSON-LD serialization < is escaped in the @graph body.
Satori peer >=0.33.5 <1; the product guide uses tested version 0.33.5.
Analytics Cookieless, no storage writes, host-guarded, reduced URLs and referrers. The optional ./relay forwards each event once to Plausible with the visitor's user agent and IP; it trusts CF-Connecting-IP only when the connecting address is in Cloudflare's published ranges, accepts at most 4 KiB and refuses other sites and preview hosts.
Persisted UI state The bulk section choice uses origin-local localStorage['sections-choice'], with values collapsed or expanded. Only bulk actions write it; individual toggles and jumps do not. It has no cookie, server, CMS, expiry or cross-origin state. Storage failures preserve usable bulk actions and declared interactive defaults. Generic persisted() uses sessionStorage for other locale-free state; theme has its own localStorage key.
Gate filesystem walk Root containment, link and non-regular refusal, traversal budgets.

Boot asset identity and recovery

Identity at v0.40.0 Value
CSP source for the script body sha256-T9RENAm4pC90ybStT4bxIcqVoQRsaBAsbPFNg8179bw=
SHA-256 fingerprint of the public ./boot.json asset 168b9a3e53dc73f0caa95b158fbc77b126b23b11c0c19272c0ac3881742a0030

The CSP value hashes the injected script body; the asset fingerprint hashes the JSON file's exact bytes. Sources: boot.json, boot.ts and the UI API report.

Pending section triggers report the painted open/closed state through aria-expanded and data-state; body inert and aria-hidden follow it. The bulk control's localized accessible name and title follow its state, and its button is disabled until ready. Boot exceptions, runtime errors, failed same-origin /_app/ module scripts or modulepreloads and unhandled rejections open pending bodies; optional and cross-origin script failures keep the stored choice. A five-second timer supplies the same readable fallback for a startup stall. Recovery opens pending bodies, clears the bulk active state and keeps the hidden, disabled control's layout space. Hydration preserves fallback on those pending cards; future mounts adopt the choice. Startup failure listeners, observers and timer finish when parsing and pending mounts complete. Server-rendered bodies are open and complete when JavaScript is disabled.

Configuration surface

Name Scope Meaning
PUBLIC_PLAUSIBLE_DOMAIN Consumer production environment Measured host; unset means analytics stay off.
GALLERY_BROWSER_PORT Local and CI Gallery browser runs Preview port, default 4173.
CI Gallery Playwright Enables forbidOnly and CI reporters.
API_BASE_SHA, GH_TOKEN, TAG Workflow internals Base commit for API approval, the workflow's own token for release creation, and the release tag. Never set locally.

The repository holds no deployment secrets. Release publication uses only the workflow token.

Licensing

Code is MIT (LICENSE). GSAP, the bundled fonts and the Lenis stylesheet keep their own licences (NOTICE); the release workflow copies LICENSE and NOTICE into every tarball. The yesid name and marks follow TRADEMARK.md.