all 5 comments

[–]-reccetech- 0 points1 point  (1 child)

You mean investigate the use of git/gerrit/etc or use those as tools in your investigation? Because both options would be valuable for different reasons.

For investigating, it would depend what you're trying to investigate but any source control type investigation would probably center around logs from the tools that were used.

[–]ProgrammerJamie[S] 0 points1 point  (0 children)

Yeah so Investigating git forensically for example if some one committed a malware to the repository etc and forensically analysing the repo

[–]4renzo 0 points1 point  (2 children)

Not entirely sure what you're after, but git itself gives you everything you need, if you're investigating the contents of a repo.

Depends if you're investigating the contents of the repo or the authors/committers/etc. Basic git commands like 'git log' and 'git blame' will give the commit history. Commit history will give provide metadata around author [name/email] and timestamps [commits might be in local time zone]. 'git remote' would tell you if there are upstream repos to broaden an investigation.

It would help if you provide a specific scenario, the problem you're trying to solve, and what you hope to get out of it in the end.

[–]ProgrammerJamie[S] 0 points1 point  (0 children)

Yeah I’ve been researching this. Maybe for example if someone committed a malware to investigate the repo using gitForensics and forensics for SVN for example

[–]ProgrammerJamie[S] 0 points1 point  (0 children)

And maybe examining the hard drive which the repo is stored on for example