RepoSense Studio is a local Studio UI for interactive repository analysis.
.\.venv\Scripts\python.exe -m reposense studio serve --port 8010Open:
http://127.0.0.1:8010
- Choose one import mode:
- Upload a repository ZIP, or
- Analyze a local repository path.
- Start analysis.
- Wait for run completion.
- Open generated outputs:
report.html- Learn UI
- SARIF
- Context Pack
run_manifest.json- backend verifier report
- local AI-derived outputs if generated
- Start Studio.
- Enter a local repository path in
Analyze local repository path. - Click
Analyze local path. - Configure run profile/ruleset/specs and start analysis.
- Track runs and open artifacts from the same run list.
Boundary notes:
- Local path analysis is local-only in Studio.
- RepoSense reads repository files for static analysis and does not execute repository code.
- Browser flow does not upload the full local directory to a hosted cloud service by default.
Studio can display Repository Review artifacts generated by RepoSense when they exist in a run directory.
The panel is read-only. It links to:
repository_review_report.mdhuman_review_required.md- Code Health artifacts such as
code_health_summary.json - Permission Auditor artifacts such as
permission_risk_report.md - AuthZ Matrix artifacts such as
authz_matrix_report.mdandauthz_negative_test_plan.md - Context Pack REVIEW files such as
context_pack/REVIEW/README.md
The panel does not execute review generation automatically. Generate the review artifacts with the existing CLI commands, then refresh the Studio run list.
For a complete local demo that produces the artifacts shown in this panel:
powershell -ExecutionPolicy Bypass -File tools/review_demo.ps1The canonical output is .reposense_review_demo/current/.
The recommended screenshot target for this panel is studio-review-panel.png.
Boundary notes:
- Studio surfaces evidence-backed review artifacts; it does not replace human code review.
- Missing review artifacts are shown as an empty state, not as a pass result.
- Suspected findings require human confirmation.
- It does not currently expose a browser folder picker for local directories.
- It does not upload data to a hosted cloud service by default.
- It does not replace CLI workflows.
- It does not guarantee backend correctness.
For local directory analysis:
.\.venv\Scripts\python.exe -m reposense ci run --repo <repo-path> --out .reposense_runs --profile demo --with-context-packThen open:
.\.venv\Scripts\python.exe -m reposense show <run_dir> --openwebui/studio/index.htmlreposense/studio/server.pyreposense/studio/jobs.pyreposense/cli.py