Software Engineer

Why Any of This Is Public

None of these projects are products. They are the tools that came out of doing client work and hitting something that did not exist yet — a CMS integration that had to be written twice, a PDF parser that needed to survive files exported by a decade-old practice management system, a scraper built because the data was only ever going to arrive as HTML.

They are published because a small utility that solves a real problem is worth more in the open than sitting in a private repository. It also means the engineering practice behind the Araptus ecosystem is inspectable rather than asserted. Anyone evaluating whether to hand over their infrastructure can read the code instead of taking a sales page at its word.

How Open Source Feeds Client Work

The connection is not sentimental. Tools that get released have to be written to a higher standard than tools that stay internal, and that standard is the one client infrastructure gets held to:

• Documented behavior, because someone who is not you has to run it.
• Dependencies kept minimal, because every added package is an added supply-chain risk.
• Failure modes handled explicitly, since a library cannot ask a user what it should do.
• Versioning that means something, so upgrades are decisions rather than surprises.

That last point is why supply-chain security is treated as a first-class concern here rather than a checklist item. The most common way a small business gets compromised in 2026 is not a targeted attack — it is a dependency nobody was watching.