Official package
The canonical npm package isfailproofai:
Why we own the alias names
Typosquatting is a common supply-chain attack where a malicious actor registers a package name that is one keystroke away from a popular package. Unsuspecting users who mistype the install command end up running attacker-controlled code with full system access - exactly the kind of threat Failproof AI is designed to defend against. To eliminate this surface, we pre-emptively own all common misspellings and formatting variants offailproofai on npm. None of these names can be registered by a third party. Each one is a thin proxy that installs and delegates to the real failproofai package.
Registered aliases
Formatting variants - different ways to write “failproof ai”:| Package | Status |
|---|---|
failproof | ✅ Published |
failproof-ai | ⏳ Pending npm support |
fail-proof-ai | ⏳ Pending npm support |
failproof_ai | ⏳ Pending npm support |
fail_proof_ai | ⏳ Pending npm support |
fail-proofai | ⏳ Pending npm support |
failprof* typos - missing one o from “proof”:
| Package | Status |
|---|---|
failprof | ✅ Published |
failprof-ai | ✅ Published |
failprofai | ⏳ Pending npm support |
fail-prof-ai | ⏳ Pending npm support |
failprof_ai | ⏳ Pending npm support |
faliproof* typos - transposed a and i:
| Package | Status |
|---|---|
faliproof | ✅ Published |
faliproof-ai | ✅ Published |
faliproofai | ⏳ Pending npm support |
Why pending? npm’s spam-prevention policy blocks names that normalize to the same string as an existing package after stripping punctuation and running similarity checks. We have contacted npm support to reserve these names for anti-squatting purposes. They will be activated once approved.You can verify any published alias is owned by us:
How the aliases work
Each alias package:- Lists
failproofaias a dependency - so the real package (including itspostinstallhook setup) runs on install - Exposes a binary matching its own name (e.g.
failprof-ai) that proxies all arguments to thefailproofaibinary
failproofai itself does.