infradrift
The problem
A server that was fine last week starts misbehaving. Someone opened a port, added a user or changed a cron job, and nobody knows what.
What I built
A CLI that snapshots packages, listening ports, users and sudo groups, cron jobs and systemd services while the server is healthy, then compares any later state against that baseline.
The result
A drift report ranked by severity, as terminal output, JSON for CI or Markdown. It exits with code 1 when something drifted, so it can run from cron.
infradrift · drift report
- Baseline
- 2026-09-26T09:52:48
- Current
- 2026-09-26T09:52:50
Users
critical+deploy-test uid=1000 /bin/bash, new user
Privileged Groups
critical+deploy-test added to privileged group sudo
Cron Jobs
warning+New cron job: */5 * * * * root /usr/bin/true
3 changes detected (2 critical, 1 warning)