Code health
yairEO/dateRangePicker scores 10.0 out of 10 on defect risk, which Repowise rates Excellent.
Full health report- Files
- 0
- Symbols
- 0
- Modules
- 0
- Doc pages
- 0
- Dead exports
- 0
Read more about yairEO/dateRangePicker
- 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/yairEO/dateRangePicker)Code health badge
Average health across every file, straight from the latest index.
[](https://repowise.dev/repo/yairEO/dateRangePicker)How yairEO/dateRangePicker works
This page is an auto-generated, always-fresh map of the yairEO/dateRangePicker repository. 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 0 source files, 0 symbols, and 0 languages, organised into 0 modules.
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.