You are not logged in.
I made a tool to track your full pacman/AUR package history as a spreadsheet after the June AUR supply chain attack.
After the recent AUR malware attack I wanted a way to audit exactly what I'd installed and when. Couldn't find anything that did this nicely so I built pkglog.
It parses /var/log/pacman.log and generates a ods spreadsheet that has AUR and pacman history (previously xlsx). Auto-updates via pacman hook after every transaction and also has history tables.
Github: https://github.com/dsarisoy/pkglog
Feedback welcome!!!
Last edited by dsarisoy (2026-06-18 18:07:16)
Offline
Does the xlsx spreadsheet you create follow the official open ecma standard (usually referred to as Office Open XML) ?
Is there a reason you're not using the .ods format from the open document foundation (best known for libreoffice) ?
- Create a package for this so your hook can be tracked by pacman
- log output to a folder/file under /var/log
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thanks so much for the feedback!!
I've completely switched the project over to ods now. I was using xlsx cause I am familiar with openpyxl but for this use case it really doesn't make sense.
I've also stored the script in /usr/local/bin/ so the user can run pkglog from terminal to view the log which is now placed in /var/log/pkglog.
I wanted to hear opinions before I tried making this a package, but that is now the obvious next step which I will work towards (besides more optimizations). I plan to update this thread! Thanks again.
Offline