Saw an #infosec blog post about using #git commands to uncover patterns in a repo, such as code that's old and stable, or where major parts are built and maintained by a sole engineer. Wanted to share it but I've lost the link. Not quite an #audit but more of a pattern of work.

Cam anyone share it with me, if you have it handy? Thanks so much

@educoder this one?

https://piechowski.io/post/git-commands-before-reading-code/

(I found it again by scrolling back through the git hashtag :) )

The Git Commands I Run Before Reading Any Code

Five git commands that tell you where a codebase hurts before you open a single file. Churn hotspots, bus factor, bug clusters, and crisis patterns.

@Hyperlynx that's it, thank you so much!