muhfaris / gherkio
Gherkio lets you describe HTTP-based integration tests as declarative YAML scenarios. Define requests, assertions, variable extractions, and orchestration — all in a simple, human-readable format that stays maintainable over time.
Code health
muhfaris/gherkio scores 6.1 out of 10 on defect risk, which Repowise rates Fair. 18 of 184 files are git hotspots, the places where changes and bug fixes concentrate.
Full health report- Files
- 184
- Symbols
- 503
- Modules
- 29
- Doc pages
- 0
- Dead exports
- 33
Where the risk concentrates
All 18 hotspotsRanked by prior bug fixes and change frequency, mined from the full git history rather than from the code alone.
| File | Churn | Prior fixes | Maintainers | Commits 90d |
|---|---|---|---|---|
| executor.gointernal/runner | 97.3th %ile | 2 | 2 | 8 |
| executor_test.gointernal/runner | 94.7th %ile | 1 | 2 | 4 |
| server.gointernal/mcp | 98.7th %ile |
Read more about muhfaris/gherkio
- OverviewFiles, symbols, languages, packages, git intelligence
- ArchitectureDependency graph, layered architecture, symbol index, and third-party dependencies
- Code healthPer-file health scores, hotspots, test coverage, dead code, and refactoring targets
- AI docsProModule-by-module documentation generated from source
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 keeps the index refreshing weekly.
[](https://repowise.dev/repo/muhfaris/gherkio)Code health badge
Average health across every file, straight from the latest index.
[](https://repowise.dev/repo/muhfaris/gherkio)How muhfaris/gherkio works
Gherkio lets you describe HTTP-based integration tests as declarative YAML scenarios. Define requests, assertions, variable extractions, and orchestration — all in a simple, human-readable format that stays maintainable over time. This page is an auto-generated, always-fresh map of the muhfaris/gherkio repository, written primarily in HTML. Repowise indexes the source, 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 resulting architectural decisions into a wiki you can read or query through MCP.
The codebase has 184 source files, 503 symbols, and 8 languages, organised into 29 modules, led by go, markdown, yaml. Static analysis leaves 312 open findings across the three health dimensions.
Use the links above to open the interactive dashboards, or connect this repo to your editor via the Repowise MCP server for grounded answers inside Claude, Cursor, or VS Code.