tadanobutubutu / my-publish-docker-exercise
Code health
tadanobutubutu/my-publish-docker-exercise scores 6.7 out of 10 on defect risk, which Repowise rates Good.
Full health report- Files
- 17
- Symbols
- 22
- Modules
- 9
- Doc pages
- 0
- Dead exports
- 0
Read more about tadanobutubutu/my-publish-docker-exercise
- 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/tadanobutubutu/my-publish-docker-exercise)Code health badge
Average health across every file, straight from the latest index.
[](https://repowise.dev/repo/tadanobutubutu/my-publish-docker-exercise)How tadanobutubutu/my-publish-docker-exercise works
This page is an auto-generated, always-fresh map of the tadanobutubutu/my-publish-docker-exercise repository, written primarily in yaml. 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 17 source files, 22 symbols, and 5 languages, organised into 9 modules, led by yaml, markdown, javascript. Static analysis leaves 6 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.