https://themanticoreproject.com/tags/library/Recent content in Library on The Manticore ProjectHugoen-USTue, 20 May 2025 10:00:00 +0000https://themanticoreproject.com/blog/goopts-command-line-parsing-library/Tue, 20 May 2025 10:00:00 +0000https://themanticoreproject.com/blog/goopts-command-line-parsing-library/<p>When I started building security tools in Go for The Manticore Project, I quickly ran into a recurring problem. Every tool needed argument parsing: authentication flags, LDAP connection settings, debug options, positional arguments for modes and subcommands. Go&rsquo;s standard <code>flag</code> package handles simple cases, but it does not support argument groups, subcommands, mutually exclusive options, or even required arguments.</p> <p>I looked at existing libraries. Some were too minimal, others tried to do too much and imposed heavy conventions on how you structure your code. None of them felt right for the kind of tools I was building: security tools with multiple modes (like <code>audit</code>, <code>add</code>, <code>remove</code>), each with their own set of arguments, and common argument groups for authentication and LDAP settings.</p>https://themanticoreproject.com/blog/manticore-v1-0-0-the-beast-awakens/Tue, 13 May 2025 05:49:58 +0000https://themanticoreproject.com/blog/manticore-v1-0-0-the-beast-awakens/<p>Over the past while, building security tooling for The Manticore Project, I kept running into the same situation: each new tool needed the same low-level building blocks. LDAP connectivity and authentication, protocol structures, cryptography helpers, and the assorted primitives that sit underneath any serious offensive or defensive utility. Re-implementing these per tool is wasteful and error-prone, so I started consolidating them into a single, reusable Go library.</p> <p>That library is <strong>Manticore</strong>, and this <code>v1.0.0</code> release marks its first public release.</p>