RepoMedic

Diagnose. Fix. Build better.

RepoMedic is a compact, read-only project health dashboard inside the Visual Studio Code Activity Bar. Scan your workspace root or choose a nested folder, then review the checks RepoMedic can currently perform for that project.

Features

• An at-a-glance health score, check counts, and recent findings.
• Separate Dashboard, Diagnostics, Dependencies, and Configuration views.
• Choose an in-workspace nested folder as the scan target, or reset to the workspace root.
• Click findings with a related file to open that file in VS Code.
• Scan and refresh actions that inspect the current target without changing project files.
• VS Code theme-aware styling and a compact sidebar layout.
• Locally bundled Codicons with their original license notices included.

Project detection and checks

RepoMedic currently recognizes these root-level project markers:

• Node.js: package.json
• Python: pyproject.toml, requirements.txt, or Pipfile
• Rust: Cargo.toml or Cargo.lock
• Go: go.mod
• Java: pom.xml, build.gradle, or build.gradle.kts
• PHP: composer.json
• Ruby: Gemfile
• Swift: Package.swift
• Dart/Flutter: pubspec.yaml
• Deno: deno.json or deno.jsonc
• C#: .csproj, .fsproj, .vbproj, .sln, or .slnx
• C/C++ or Make-based projects: CMakeLists.txt or Makefile

Detection is not the same as full language support. At this release, substantive project checks are implemented for package.json projects: RepoMedic checks for a README and .gitignore, parses the manifest, checks for a supported package-manager lockfile when dependencies are declared, and looks for a test script. Other detected project types are reported as unsupported for checks; their dependencies and configuration are not inferred.

The Dependencies view shows declared package names, version specifiers, and dependency groups from a valid package.json, plus whether a recognized lockfile exists. It does not inspect installed package versions, resolve packages, or run a vulnerability audit. The Configuration view lists a small set of detected root-level files, package metadata and scripts when available, and whether .git metadata is present at the scan target.

Health score

The score is calculated from checks that RepoMedic actually runs:

passed checks ÷ (passed checks + warnings + errors) × 100

The result is rounded to the nearest whole number. Informational findings do not affect the score. When no supported checks run, RepoMedic shows no score rather than inventing one. The score reflects only the checks listed above; it is not a general code-quality or security rating.

Install

After RepoMedic is available on the Visual Studio Code Marketplace:

1. Open Extensions (Ctrl+Shift+X on Windows/Linux, Cmd+Shift+X on macOS).
2. Search for RepoMedic by RepoMedic and install it.

To install a reviewed VSIX file instead, use:

code --install-extension repomedic-0.1.0.vsix

Getting started

1. Open a project folder or multi-root workspace in VS Code.
2. Select the RepoMedic icon in the Activity Bar.
3. Use Run Diagnosis to inspect the displayed scan target.
4. Choose Choose Folder to scan a nested folder inside the current workspace. Use Root to return to the workspace root.
5. Review the Dashboard, Diagnostics, Dependencies, and Configuration sections.

You can also run RepoMedic: Run Scan or RepoMedic: Refresh Results from the Command Palette.

Privacy and file access

RepoMedic uses the VS Code filesystem API to enumerate the selected folder, check for a defined set of root-level files, and read package.json (up to 1 MB) when present. Its source contains no external network requests or telemetry. Filesystem access follows the active VS Code environment and filesystem provider, which may be remote when using a remote development session.

RepoMedic does not execute project scripts, install packages, read environment-variable values, or modify project files. Finding links open files through VS Code. This describes RepoMedic's implemented behavior and does not make claims about other VS Code components or extensions.

Known limitations

• Detection checks only the selected scan target's top level; it does not search recursively.
• Only package.json projects receive substantive checks and dependency/script details.
• The recognized configuration-file list is intentionally limited to common root-level files.
• A declared lockfile is checked for presence, not parsed or verified against the manifest.
• No package vulnerability, outdated dependency, source-code, build, or test execution checks are performed.
• The scan target is held for the current extension session and must be inside the open VS Code workspace.

Development

1. Clone or open the source project in VS Code.
2. Run npm install.
3. Press F5 to launch the Extension Development Host.

Available checks:

• npm run compile — compile the TypeScript extension.
• npm run lint — run ESLint.
• npm test — compile, lint, and run automated extension tests.

License

No LICENSE file is included yet. A license must be selected and added by the project owner before public release; RepoMedic does not choose one on the owner's behalf.