Just shipped v1.3 here's what's new:
- Report PDFs, done properly. "Download PDF" used to just be a shortcut to your browser's print dialog, which meant formatting depended on whatever browser and OS you happened to be using. It's now a real document generated on our servers consistent, designed, and ready to share or attach to a doc regardless of what you're viewing it on.
- Team management that scales past "add people manually." You can now invite teammates by email with a specific role (owner/admin/member/viewer), or if you're on a plan with SSO verify ownership of your company's email domain and let anyone signing up with that domain request to join automatically. Join requests show up for an admin to approve, so you're never letting people in blind.
- SSO polish. Logging in with a work email tied to an SSO org now redirects you straight to your identity provider no more hunting for a separate "Sign in with SSO" link. Also fixed a gap where SAML configuration could be edited by any team member instead of just owners/admins.
Full changelog: debtdrone.net/changelog
the auto-PR idea is genuinely cool but i'd love to see a way to scope it to a specific folder or service, kind of like how dependabot lets you group updates. otherwise fixing debt in a legacy monolith vs the new microservice would feel very different in risk
One thing that would make this really useful for my team — let DebtDrone open draft PRs by default and only promote them to ready-for-review once CI passes, so we're not reviewing fixes that break the build in the first place.
This is genuinely cool, the auto-PR angle is way more useful than yet another dashboard. One thing though, it would help a lot if you could scope the analysis per service or directory instead of the whole repo. Big monorepos have totally different risk profiles per team and a single ranked list ends up being kind of useless for everyone except the platform crew.
The GitHub integration picked up real issues from my repos right away, and I loved that it skipped the trivial linter complaints. Opening a fix PR instead of just flagging the debt is a genuinely smart move.
Tried it on a side repo and it actually opened a sensible PR instead of just listing 200 lint warnings. The impact scoring feels tuned by someone who's been on call.
Love the PR-first approach, way more actionable than yet another dashboard. One thing that would make this even better for my team: let us scope the scans with a config file in the repo so we can exclude legacy directories or files under active refactor, otherwise the AI ends up opening PRs in spots we've intentionally parked.