New blog post 🥳
Stamp It! All Programs Must Report Their Version
> […]
>
> In this article, I’ll explain how 3 simple steps (Stamp it! Plumb it! Report it!) are sufficient to save you hours of delays and stress during incident response.
Read more: https://michael.stapelberg.ch/posts/2026-04-05-stamp-it-all-programs-must-report-their-version/
Aside from the article itself, there’s also a repository to illustrate the technique at https://github.com/stapelberg/stampit, a README where we can collect language ecosystem build stamping status, and an agent SKILL.md to audit your fleet! :)
And of course, I researched **the Nix full picture diagram** (see attached) for this article 🤯
There’s probably some mistakes in there, because I am somewhat pressed for time and this rabbit hole turned out *very deep*.
Please do send corrections (with references, ideally) if something seems wrong! Thanks!🙏
@zekjur I made the FRR library executable (no I didn't get confused there) just so it can report its version. Sadly, this broke at some point due to some changes in GCC re. assumptions about stack alignment (assumes 0/16, but it's 8/16 on x86_64 now), need to push a fix for that…
I invite FRR users to try running libfrr.so, maybe your version still works 😉
Michael Stapelberg 🐧🐹😺
equinox