x509watch is a simple command line application that can be used to list soon expiring or already expired X.509 certificates, such as SSL certificates. All certificates are searched by default in the standard PKI directory, but any other directory can be specified as a parameter. Only Base64 encoded DER and PEM X.509 certificates are supported.
HATop is an interactive ncurses client and real-time monitoring and statistics displaying tool for the HAProxy TCP/HTTP load balancer. HATop's appearance is similar to top(1). It supports various modes for detailed statistics of all configured proxies and services in near real-time. In addition, it features an interactive CLI for the HAProxy Unix socket. This allows administrators to control the given HAProxy instance (change server weight, put servers into maintenance mode, etc.) directly out of HATop (using keybinds or the CLI) and monitor the results immediately.
Simple Package Manager (SPM) is intended to operate in a way similar to existing package managers (apt, dpkg, Pacman, etc.). Instead of supporting a centralized package repository, SPM allows remote packages to be downloaded and installed automatically, given their URL. This allows a developer to package and distribute software via a package management system without having to worry about the many different formats and Linux distribution repositories.
DUST (Driver UpdateS Tool) is designed to "just work" for building kernel driver modules. The concept is similar to DKMS, though this has the benefit of being simpler, easier to test and use, and easier to integrate. DUST enables you to package up a driver pack, install it into the dust directory, and prepare for upgrading. Each driver pack has 3 components: an install file (populates a tree with stuff needed to build a working driver); the driver payload (tarball, zip file, etc.); and the update script, which will do nothing but copy the old driver kernel modules to a backup directory, build/install a new copy of the driver kernel, run depmod if needed, and mkinitramfs, mkinitrd, or dracut if needed. The install file is very trivial. It is easy to recode this as an RPM or deb. As long as it moves the driver payload and update script to the right location, you can use any mechanism to do this.