Files
gitea-mirror/www
ARUNAVO RAY e49cf0e367 fix(security): raise dependency floors for the 2026-09-08 advisories (#414)
Every one of these advisories was published on 2026-09-08 between 20:30 and 21:26 UTC, against the versions this repository was already pinning from the earlier rounds. Same package names, new CVEs, not a regression from anything that merged today.

**Application** (the nine Docker Scout alerts on main)

| Package | Was | Now | Advisory |
| --- | --- | --- | --- |
| astro | 7.1.0 | 7.3.2 (floor ^7.2.8) | GHSA-26w7-cxv4-gfx2, remote code execution through AVIF image optimization (critical) |
| @xmldom/xmldom | 0.8.13 | 0.8.15 | eight advisories, CVE-2026-83605 through CVE-2026-83619 (high) |
| sharp | floor ^0.35.0 | ^0.35.4 | GHSA-rgj7-g3m4-5g8c, libheif |
| js-yaml | floor ^4.3.1 | ^4.3.2 | GHSA-2883-xcg3-v3hh |
| svgo | (no floor) | ^4.1.0 | GHSA-w27v-7q3p-w38r, GHSA-4vpr-x523-8j87 |

**Documentation site** (the six Dependabot alerts against `www/pnpm-lock.yaml`)

astro to ^7.2.8 (resolves 7.3.2), and pnpm overrides for sharp ^0.35.4, svgo ^4.1.0 and js-yaml ^4.3.2. That covers all six, including the moderate Astro authorization bypass (GHSA-376h-93r7-7g6f) which 7.2.4 already fixed.

This supersedes the two Dependabot pull requests, which only cover the site and overlap with each other.

Checked: 906 tests pass, `bun run build` passes, and the site builds its 37 pages. The lockfile change is confined to the bumped packages and their transitive resolution.
2026-09-09 11:45:32 +05:30
..
2025-10-03 11:05:55 +05:30
2025-07-08 19:29:26 +05:30
2025-07-09 00:55:28 +05:30
2025-10-03 12:35:04 +05:30
2025-07-08 21:58:45 +05:30
2025-10-03 12:35:04 +05:30

Gitea Mirror Marketing Site

This Astro workspace powers the public marketing experience for Gitea Mirror. It includes the landing page, screenshots, call-to-action components, and the new use case library that highlights real-world workflows.

Developing Locally

bun install
bun run dev

The site is available at http://localhost:4321. Tailwind CSS v4 handles styling; classes can be used directly inside Astro, MDX, and React components.

Project Structure

  • src/pages/index.astro – Main landing page
  • src/components/ – Reusable UI (Header, Hero, Features, UseCases, etc.)
  • src/lib/use-cases.ts – Central data source for use case titles, summaries, and tags
  • src/pages/use-cases/ – MDX guides for each use case, rendered with UseCaseLayout
  • src/layouts/UseCaseLayout.astro – Shared layout that injects the header, shader background, and footer into MDX guides

Authoring Use Case Guides

  1. Add or update a record in src/lib/use-cases.ts. This keeps the landing page and library listing in sync.
  2. Create a new MDX file in src/pages/use-cases/<slug>.mdx with the UseCaseLayout layout and descriptive frontmatter.
  3. Run bun run dev to preview the layout and ensure the new guide inherits global styles.

Deployment

The marketing site is built with the standard Astro pipeline. Use bun run build to generate a production build before deploying.