repowiserepowise
Sign in
skritika563/ecosetu
OverviewDocsArchitectureKnowledge GraphFilesCode HealthSecurityRefactoring

People & History

CommitsContributorsDecisions
Chat
Stats
repowiserepowise
ExplorePricingDocs
Sign in
repowiseskritika563/ecosetu
EC
EC

skritika563 / ecosetu

JavaScript
Use in your agentAsk this codebase

github.com/skritika563/ecosetu·Indexed at af95c66·11h ago·Up to date with upstream

About this codebase

345 files and 1,167 symbols in 2 modules, written in JavaScript.

Built from the index

Start reading

  • Knowledge graph345 files and how they depend on each other.→
  • Contributors2 people: who owns what, and where one person holds most of the knowledge.→

Code health

7.6out of 10Good

This codebase scores 7.6 out of 10 for code health, which we rate good. It also scores maintainability 6.9 and static performance 10.0 out of 10. The three are scored separately and never blended into one number. Risk is concentrated, as it usually is: 25 of 345 files are git hotspots, and they average 4.7 — which is where the fixes pay off most.

Full health report →

Do next

2 things worth doing in the week to Sep 23, the last indexed commit, 2 of them now.

Now

  • Critical

    Simplify AddressFormDialog in frontend/src/components/pickups/AddressPicker.jsx while the change is fresh

    1 commit in the last 7 days added or worsened 3 critical or high findings here, still open. Fixing now costs less than after the next change.

    serious findings
    3
    critical
    2
    latest commit
    Add location picker, collector navigation and live pickup tracking using
    Small effort
  • High

    Simplify serializePickup in backend/services/pickupSerializer.js while the change is fresh

    1 commit in the last 7 days added or worsened 1 critical or high finding here, still open. Fixing now costs less than after the next change.

    serious findings
    1
    critical
    0
    latest commit
    Add location picker, collector navigation and live pickup tracking using
    Small effort

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
All actions in the Overview →

Use skritika563/ecosetu 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/skritika563/ecosetu

One command, run anywhere. Adds the server to your local Claude Code config.

Docs
bash
claude mcp add --transport http repowise https://api.repowise.dev/mcp/skritika563/ecosetu \
  --header "Authorization: Bearer rw_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
The snippet shows a placeholder key. Generate one to get a copyable secret.
Sign in and create an API key to connect.Sign in

This repo is public, so anyone with a Repowise account and an API key can connect.

Try asking

  • get_overview()
  • get_answer("how is ecosetu put together?")
  • get_why("why is ecosetu 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, 426 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.

Repowise badge: explore code
[![repowise](https://api.repowise.dev/badge/wiki/skritika563/ecosetu.svg)](https://repowise.dev/repo/skritika563/ecosetu)

Code health badge

Average health across every file, straight from the latest index.

Code health badge showing the average health score out of 10
[![Code health](https://api.repowise.dev/badge/health/skritika563/ecosetu.svg)](https://repowise.dev/repo/skritika563/ecosetu)

How skritika563/ecosetu works

This page is a map of the skritika563/ecosetu repository, written primarily in JavaScript, 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 345 files and 1,167 symbols in 2 modules, led by JavaScript. 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.