I built a forensics documentation tool because my university course drove me crazy
I'm not a professional forensics investigator, just a security student who had a university course on digital forensics last summer and got increasingly frustrated with one specific part of it: not...

Source: DEV Community
I'm not a professional forensics investigator, just a security student who had a university course on digital forensics last summer and got increasingly frustrated with one specific part of it: not the investigation, but the documentation. Every tool, every command, every hash, manually noted. Timestamps written essentially by hand. Chain of custody as an afterthought. My colleagues felt the same way. So we built something to fix it. forensic-log-tracker wraps your forensic commands, whatever you can do in a shell, and automatically produces timestamped, SHA256-hashed, GPG-signed investigation logs. One command at the end generates a complete case report in Markdown. It also provides explanations, as report readers are hardly ever experts, so for your commands you get structures like: --- ### [+] Command: `sha256sum working_copy.img` - Timestamp: `2026-04-06T09-08-28-524115+00-00` - GPG-signature: [+] Valid - SHA256: `92cebec98bfd99f06db56bd758d5977b62abc27513805ca24a72cdb7ed0f5756` ##