Repowise · Codebase intelligence
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.
Languages
- go38.6%
- markdown31.5%
- yaml26.6%
- javascript1.1%
- makefile0.5%
- shell0.5%
- toml0.5%
- json0.5%
Explore muhfaris/gherkio
Files, symbols, languages, packages, git intelligence
Interactive view of how files import each other
Files with the most churn and co-change risk
Bus-factor and per-file maintainer maps
Architectural decisions extracted from commits and PRs
Unreachable symbols and unused exports
Module-by-module documentation generated from source
Ask grounded questions over the indexed code
Entry points5
cmd/run.godocs/book/playground/app.jsdocs/book/src/cli/run.mdinternal/mcp/server.gomain.go
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, 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. Git churn analysis flags 18 high-frequency files as hotspots — places where bugs, rewrites, and code review tend to concentrate. The dependency graph clusters into 87 tightly-coupled module communities.
Use the panels 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.