Skip to content

Roadmap

Codemetry is actively developed. Here’s what’s available now and what’s planned.

  • Git Analysis — Churn, scatter, commit patterns
  • Follow-up Fix Detection — Identifies corrections after changes
  • Baseline Normalization — Compare against repository norms
  • Heuristic Scoring — Deterministic 0-100 scores with labels
  • Confidence Scores — Indicates result reliability
  • Confounders — Context flags for interpretation
  • Reasons — Human-readable score explanations
  • Laravel — Full adapter with Artisan command
  • Core Package — Framework-agnostic for any PHP project
  • OpenAI — GPT-4o, GPT-4, GPT-3.5
  • Anthropic — Claude 3.5 Sonnet, Opus, Haiku
  • DeepSeek — DeepSeek Chat
  • Google — Gemini Pro, Gemini Flash
  • Table — Terminal-friendly display
  • JSON — Machine-readable with full details

Custom Scoring

Configurable thresholds and weights for the scoring algorithm. Adjust penalties and rewards to match your team’s priorities.

Quality Tool Providers

Built-in providers for PHPStan, ESLint, Psalm, and other static analysis tools.

Team Dashboards

Web interface for viewing trends across repositories and time periods.

GitHub Action

Official GitHub Action for CI/CD integration with PR comments.

Multi-Repository

Aggregate analysis across multiple repositories with unified reporting.

Trend Detection

Automatic detection of improving or declining patterns over time.

Alerting

Notifications when scores drop below configurable thresholds.

Symfony Adapter

Official adapter for Symfony framework.

  • IDE Integration — Real-time mood indicators in VS Code, PhpStorm
  • API Service — Hosted analysis for repositories
  • AI Score Adjustment — Allow AI to suggest score modifications
  • Custom Window Sizes — Analyze by week, sprint, or custom periods
  • Historical Comparison — Compare current period to same period last year

These features were considered but deferred:

Codemetry explicitly does not analyze emotions. The “mood” terminology refers to code health indicators, not developer feelings. This is by design, not a limitation.

While --author filtering exists for focused analysis, Codemetry is not designed for performance management. Use it for understanding code patterns, not evaluating people.

V1 analyzes historical data. Real-time commit analysis (webhooks, streaming) may come later but isn’t the current focus.

Codemetry currently supports Git only. SVN, Mercurial, or Perforce support may be considered based on demand.

Interested in contributing to Codemetry’s development?

  1. Report Issues — Found a bug or unexpected behavior? Open an issue.
  2. Request Features — Have an idea? Share it in discussions.
  3. Submit PRs — Bug fixes and improvements welcome.
  4. Build Providers — Create and share custom signal providers.
  5. Write Adapters — Help support more frameworks.

Current development priorities:

  1. Stability and reliability of core features
  2. Documentation and examples
  3. Community-requested improvements
  4. Performance optimization

Your feedback shapes Codemetry’s direction:

  • Star the repository to show support
  • Open issues for bugs and feature requests
  • Join discussions for broader conversations
  • Share how you use Codemetry

The roadmap evolves based on real-world usage and community input.


Last updated: 2024