Public repository field guide Reviewed 11 Aug 2026

Find a project. Prove the fit.

Samsarix LLC stewards 31 public repositories across applications, developer tools, libraries, research, and legacy projects. Browse the evidence-backed catalog—or turn your job and constraints into a transparent shortlist, side-by-side comparison, and smallest credible pilot plan.

01 / Start with an outcome

Three high-signal routes

These are starting points, not endorsements of production readiness.

02 / Browse the public work

Repository catalog

Search by product, repository address, technology, or use case. Cards show current product names alongside current repository addresses; the remaining Helix-era URLs are explicit lifecycle holds.

Preparing the catalog…

03 / Read the labels correctly

A catalog, not a certification

What is reviewed here

Each repository is publicly reachable, its description is deliberately cautious, and its route was checked against the public profile and the available sibling checkout.

What is not certified

Package publication, compatibility, security, maintenance level, licensing, deployment, and production readiness must be verified in the destination repository.

Why some URLs still say Helix

Samsarix is the current company brand. The few remaining Helix-era repository names are explicit historical or consolidation holds; private flagship work is not treated as a public route.

04 / Lightweight by design

No account. No tracking. No live dependency graph.

The catalog ships as static files and makes no background network requests. It stores nothing in your browser. The only network activity after load happens when you choose an outbound link.

That keeps the guide fast, cheap to host, easy to audit, and useful even if another Samsarix project is unavailable.

05 / Understand the boundaries

One portfolio does not mean one runtime.

The Field Guide is now the canonical public map. It preserves the strongest evaluation guidance from the earlier Project Guide and lifecycle context from the Hub Directory without copying their runtimes, historical exports, or license-restricted artifacts.

Read the architecture and lifecycle guide