sayantan181222 / razorsentry
Hackathon
github.com/sayantan181222/razorsentryIndexed at 7f24862Up to date with upstream
About this codebase
31 files and 233 symbols in 4 modules, led by Python (20 files) and Shell (2).
Built from the index
Code health
This codebase scores 7.6 out of 10 for code health, which we rate good. It also scores maintainability 8.9 and static performance 9.5 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 5 of 31 files are git hotspots, and they average 6.7 — which is where the fixes pay off most.
Do next
Nothing stands out in the week to Sep 4, the last indexed commit.
Improve what Repowise can see
Add a test coverage report
Without one, Repowise cannot tell tested code from untested code, so every test-related action says “unknown”.
- line coverage
- Unknown, no report
Small effort
Use sayantan181222/razorsentry in your agent
Point Claude Code, Cursor, Codex or VS Code at this repository. Your agent gets the index this page is built from: cited answers, callers, history and health for any file.
https://api.repowise.dev/mcp/sayantan181222/razorsentryOne command, run anywhere. Adds the server to your local Claude Code config.
Docsclaude mcp add --transport http repowise https://api.repowise.dev/mcp/sayantan181222/razorsentry \ --header "Authorization: Bearer rw_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
This repo is public, so anyone with a Repowise account and an API key can connect.
Try asking
- get_overview()
- get_answer("how is razorsentry put together?")
- get_why("why is razorsentry structured this way?")
Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed.
Go deeper
- OverviewEverything the index found, what changed this week, commits and decisions.
- DocumentationModule-by-module documentation, 50 pages, 0 written by a model.
- ArchitectureDependency graph, layers and third-party dependencies.
- Code healthEvery file's score, the findings behind it, tests and refactoring plans.
- CommitsEach commit's effect on code health, with agent provenance.
- ContributorsWho owns what, and where one person holds most of the knowledge.
- DecisionsArchitectural decisions mined from commits and pull requests.
- Ask this codebaseSign inGrounded answers over the indexed code.
For maintainers
Add a badge to your README
Both badges are public, cached, and update on their own after every index. Nothing to install.
Repowise badge
Links to this page. Adding it also re-indexes the repo every week.
[](https://repowise.dev/repo/sayantan181222/razorsentry)Code health badge
Average health across every file, straight from the latest index.
[](https://repowise.dev/repo/sayantan181222/razorsentry)How sayantan181222/razorsentry works
Hackathon This page is a map of the sayantan181222/razorsentry repository, written primarily in Python, rebuilt from the source each time it is indexed. Repowise parses every symbol, computes a dependency graph, scores per-file code health from complexity, duplication, test coverage and churn, mines git history for hotspots and ownership, and lifts the architectural decisions into documentation you can read here or query through MCP.
The codebase has 31 files and 233 symbols in 4 modules, led by Python, Shell and Dockerfile. Code health is 7.6 out of 10, rated good.
Use the links above to open each view, or connect this repository to your agent for grounded answers inside Claude, Cursor, Codex or VS Code.