carlos / contra Public

Namespace check: CONTRA Question open

Run 2026-09-01, in the same shape as the check done for "carlos" before that name was committed to.

The good news, and it is the part that matters: there is no password manager called Contra. The name is clear in the actual product category, which is the collision that would have hurt.

Taken:

  • npm contra — an async flow-control library, v1.9.4, still published. (contra-app is free.)
  • GitHub org contra — taken, 7 public repos; and contraapp is taken too. (getcontra, contrapm are free.)
  • Domains — contra.dev, contra.app, contra.sh, getcontra.com and usecontra.com all resolve. contra.app is a parked lander, so some of these are probably purchasable rather than in use. contrapass.com is free.
  • contra.com is the freelancer/hiring platform — live, funded, and well known. Different category, but it owns the plain search result.

Free: homebrew-core has no contra formula, and the family ships through carlosframework/tap anyway, so packaging is unaffected.

Read: this is roughly where "carlos" was — a known collision in an unrelated category, noted rather than treated as a blocker. The real cost is discoverability against contra.com, not a naming conflict. If the name stands, the practical follow-ups are picking a domain that is actually available and deciding the npm/GitHub handles early.