nowfound

Alternatives

Products that do what Git Audit does

VS code extension for auditing code repos

  1. 1GB
  2. 2WS

    I’ve been in the MLOps space for ~10 years, and data is still the hardest unsolved open problem. Code is versioned using Git, data is stored somewhere else, and context often lives in a 3rd location like Slack or GDocs. This is why we built XetHub, a platform that enables teams to treat data like code, using Git. Unlike Git LFS, we don’t just store the files. We use content-defined chunking and Merkle Trees to dedupe against everything in history. This allows small changes in large files to be stored compactly. Read more here:…

    2022 · xethub.com

  3. 3GW

    I've always wanted a better way to explore the authorship data embedded in a Git commit log. I'm having fun building a CLI tool to do this. It's a bit like the "Contributors" tab on Github that shows you how many commits each contributor has made but much faster and with many more options. If you get a chance to try it out, please let me know. I'd love to hear feedback and suggestions. Thank you!

    2025 · github.com

  4. 4

    Report bugs in GitHub 20x faster

    2022

  5. 5VA

    I explored an alternative way to view codebases to the typical folder/file list, showing a bird's-eye-view of its structure. https://octo.github.com/projects/repo-visualization

    2021 · octo.github.com

  6. 6QB
  7. 7GB
  8. 8GA

    Gitlogue is a CLI that turns your Git commits into a typing-style replay. It visualizes diffs line by line, shows the file tree, and plays back each edit as if it were typed in real time. Key points • Realistic typing animation • Syntax-highlighted diffs • File-tree view • Replay any commit • Self-contained CLI Demo video is in the README. Repo: https://github.com/unhappychoice/gitlogue

    Nov 2025 · github.com

  9. 9

    See the top contributor + % lines per author

    2025

  10. 10

    Document everything, from start to ship

    2022

  11. 11

    Figure out ways to fix GIT screw-ups

    2019

  12. 12

    Your year in code

    2021

  13. 13GT

    2017 · gitorials.com

  14. 14IM

    I use interactive rebase quite often, and particularly like the editor bundled with IntelliJ. But I do not always work with IntelliJ, and am not 'fluent' with Vim, so I tried to replicate roughly the same rebase experience within a TUI. I used a small TUI OCaml project i made last year. The notable features are: - Move commits up and down, fixup, drop - Rename commits from the editor (without having to stop for a reword during the rebase run) - Visualize modified files along commits - 'Explode' a commit ,creating a commit for each modified file (a thing I found myself doing quite often)…

    2024 · github.com

  15. 15FK
  16. 16
    Gut98

    An easy-to-use git alternative to version-control your code

    2023

  17. 17GO

    This is a tool for auditing github organizations including their repos, users, and teams. It is useful for compliance, security and auditing.

    2022 · github.com

  18. 18AB

    This was more so an exercise in prompting with Lovable and Cursor than it was in creating a highly polished product/tool. Yet the end result works :) AuthorTrail is a locally running web UI that you can point to any Git repo. It will then look for all the files you have ever touched. This can be useful for large repos with lots of activity, where you want to remind yourself how you did something in the past. For example, I am using it to remind myself how I wrote an obscure unit test, without needing to browse my older PRs. Feedback welcome!

    2024 · github.com

  19. 19GM
  20. 20GS
  21. 21CL

    2023 · ghloc.vercel.app

  22. 22

    Check if a GitHub repo's stars are real before you commit.

    Apr 2026 · chromewebstore.google.com

  23. 23PT

    I've been trying to figure out how long feature development takes, for years. I'm not a fan of (a priori) estimations of work, which just seem like the wrong measure. I think I've got a better way. Genuinely interested if some git gurus can improve this. Particularly around the pre-push hook, which is dependent on retained squash commit text. Or if there's an entirely better way to achieve the same thing.

    2025 · doocot.sh

  24. 24GW

    hey all! Vaibhav and Ethan here. We asked a silly question, "what if you attempted to look into every commit of every repo?" and over the holidays ended up building something kind of fun. Here's some interesting stats: Charlie Marsh has put a crazy amount of work in on UV... so far #1 with over 149k minutes of work this year. (103 days of non-stop coding ).. #2 is me with 85k (just over 59 days...) on BAML #3 - Jérémy M. with 82k (57 days) working on Twenty #4 - Alexander Belanger with 79k (54 days) working on Hatchet Some fun repos:…

    2024 · wrapped.dev

Ranked by how close each launch is in meaning, then by votes. Refine with a description →