ioquake3 (or ioq3 for short) builds upon id Software's Quake 3 source code release. It cleans it up, fixes bugs, and adds features. Its goal is to be the Quake 3 distribution upon which people base their games and projects. Its design goals include optimizing the engine for playing Quake 3: Arena, Team Arena, and all popular mods. This distribution of the engine has been ported to many new platforms. While it doesn't have PunkBuster (and never will), it does provide more security for servers and clients by way of various bugfixes which aren't in id's client.
Jmx4Perl provides an alternate way of accessing Java JEE Server management interfaces that are based on JMX (Java Management Extensions). It is an agent-based approach where a small Web application deployed on the application server provides HTTP/JSON-based access to JMX MBeans registered within the application server. It is set up from a handful of Perl modules, which can be integrated seamlessly in your own programs. It also includes a Nagios plugin, check_jmx4perl, a jmx4perl command line tool for remote JMX queries and operations, and a readline-based JMX shell j4psh, with context sensitive command completion and syntax highlighting.
Osgish is a command line shell for OSGi. It is based on the Readline Library, Jmx4Perl, as the OSGi backend, and Aries JMX as the OSGi Management layer. It is different than other OSGi shells, as it is implemented in pure Perl and provides unique features like wildcard support, context-sensitive command line completion, syntax highlighting, bulk lifecycle operations, advanced query facilities, and remoting via HTTP. It uses jmx4perl and Aries JMX OSGi bundles for accessing the OSGi container remotely.
The Paranoid modules provide a number of routines that are intended for use in strict and taint-safe scripts. The modules cover a variety of tasks from command-line argument parsing to process and network management. All of the modules use a debug trace framework for diagnostic output that is easily used and extended for application code as well.
autofwd is an automated firewalling daemon intended to block hosts performing unwanted acts. While it was designed to be used to thwart hosts running dictionary attacks on logins (of any service), it can be used for just about anything. The external commands it runs are configurable, allowing you to take additional actions against offending hosts such as running an nmap OS fingerprint before firewalling, or just silently logging the event.
Class::EHierarchy is intended for use as a base class for custom objects. The objects need one or more of the following features: orderly bottom-up destruction of objects, opaque objects, class-based access restrictions for properties and methods, primitive strict property type awareness, and alias-based object retrieval.