2 ms·

Requires Java.

• exabrial 11y ago
  There's nothing wrong with server side Java... Quick glance through the code doesn't reveal any major risks, actually seems to be fairly well written. Author seems to like to write a lot of static methods/utility classes rather than rely on composition using dependency injection... not exactly a modern development style but it's good enough. Author avoids needless abuse of software patterns. It'd be pretty easy to do a security audit on this code base.