RepoPulse: update frontend/src and backend/app (+4 areas)
Public changes compared with the previous published export: 19 files changed. Affected areas: - backend/app: 3 files - dependencies: 2 files - documentation: 1 file - frontend: 2 files - frontend/src: 10 files - tests: 1 file Changed files: - Updated: "backend/app/acquisition.py" - Added: "backend/app/icons.py" - Updated: "backend/app/main.py" - Added: "backend/tests/test_icons.py" - Updated: "docs/ARCHITECTURE.md" - Updated: "frontend/package-lock.json" - Updated: "frontend/package.json" - Updated: "frontend/playwright.config.ts" - Updated: "frontend/src/App.tsx" - Updated: "frontend/src/components/DashboardView.tsx" - Added: "frontend/src/components/HealthRing.tsx" - Updated: "frontend/src/components/HistoryView.tsx" - Added: "frontend/src/components/Icon.tsx" - Updated: "frontend/src/components/PortfolioAtlas.tsx" - Updated: "frontend/src/components/RemediationCenter.tsx" - Added: "frontend/src/components/RepoAvatar.tsx" - Updated: "frontend/src/main.tsx" - Updated: "frontend/src/styles.css" - Updated: "frontend/vite.config.ts" Export provenance/manifests refreshed; excluded from the change summary. Publish curated RepoPulse source from 7a60c53ee2c1daebecd66a01656e323f1db72e56
This commit is contained in:
1 parent
d5ab22ddf1
commit
787a2b1dc3
21 files changed
+1543
-759
No files matched your search
@@ -37,6 +37,8 @@ For a Gitea job, the requested SHA is captured at enqueue time. The acquirer use
|
||||
|
||||
## Scan boundary
|
||||
|
||||
Project icons are resolved read-only from the existing bare mirror at the repository's retained scan revision (`GET /api/v1/repositories/{id}/icon`). The resolver lists the tree with `git ls-tree`, ranks favicon/icon/logo candidates deterministically (SVG first, larger rasters over tiny favicons, `public`/`static`/`app` directories first, tests, fixtures, vendored and screenshot paths excluded), reads at most 128 KiB per blob with `git cat-file` and serves the file only when its content matches its extension. It never fetches, never touches a worktree and caches results per revision in memory. Responses carry `nosniff` and a sandboxing `Content-Security-Policy`, because repository-supplied SVG is untrusted; the frontend renders icons through `<img>` and falls back to readiness-tinted initials when no icon exists.
|
||||
|
||||
When `REPOPULSE_SCAN_ROOT` is configured, every local scan path is resolved and checked against that root before analysis. Compose sets the root to `/scan` and mounts the user-selected source directory read-only. The scanner then resolves every candidate file, rejects symlinked files and directories (including symlink ancestors), and requires the resolved file to remain below the scan root. This prevents the API from being used as a generic filesystem browser outside the configured analysis boundary. Gitea worktrees are acquired into `/data`, not `/scan`, and are controlled by repository-ID/job-ID validation.
|
||||
|
||||
## Persistence and deployment boundary
|
||||
|
||||
Reference in new issue
Block a user