Skip to main content

Public roadmap

Where DebtLens is going. Honest about what a small team ships — no promises we cannot keep. Feedback welcome at hello@debtlens.tech.

Shipped

  • CLI with 8 technical debt metrics

    Hotspots, Complexity×Churn, Temporal Coupling, Knowledge Silos, Dead Code, Velocity Trend, Merge Discipline, AI Governance. Free for local analysis, single binary for macOS/Linux/Windows.

  • Hub with license activation

    Flat-rate pricing, per-machine activation, magic-link auth.

  • AI-powered executive narrative

    Claude-generated PDF with three euro-denominated cost dimensions (firefighting, debt servicing, recovery investment).

  • Customizable economic settings

    Per-user daily cost, working days, recovery effort assumptions, display currency (EUR/USD/GBP/CHF).

  • 12-month financial projection

    Three scenarios (status quo, Q1 recovery, progressive cleanup) with break-even month, in both web view and PDF.

  • Board presentation export

    Five-slide 16:9 PDF deck (executive summary, cost dimensions, top priorities, recovery roadmap, next review).

  • Compare mode

    Side-by-side diff between two reports of the same repository, with score, count and cost deltas.

  • Public sample reports

    Pre-generated analyses on Laravel, Symfony, Vue.js, React, Livewire.

  • Team tier at €99/month

    3 repos, 3 machines, real-time AI narrative, historical trend tracking.

In progress

  • GitHub Action (grazulex/debtlens-action)

    PR comments with score delta, fail threshold and README badge. CLI already supports --output=json, so the action consumes it natively.

  • CLI --dry-run flag for debtlens report

    Prints the exact JSON payload that would be sent to the hub, without sending it. Privacy-by-design transparency tool.

Exploring

  • Sectoral benchmarks

    Anonymised peer comparison (opt-in, k-anonymity ≥ 20). Gated on having six-plus months of hub data.

  • Monorepo-aware analysis

    Per-package scoring when a repository contains multiple logical subprojects.

Deliberately short. Priorities shift based on user feedback and what a small team can ship well. Items get promoted from “Exploring” to “In progress” when we commit to a shipping date.