HBForge is not on npm. There are no open pull requests. No issues tab. No public roadmap votes. We work with developers who bring production-grade discipline — not contributors who want a GitHub star.
Current status: T0 internal · T1 limited enterprise · T2 preview applications open
Every tier carries the same quality expectations. What changes is scope, depth, and influence over the roadmap.
T2 → T1 graduation after 3 months of active, production-grade usage + one accepted RFC
"The open source model optimises for reach. We optimise for correctness. Anyone can open a PR. Not everyone should ship to production."— HyperBridge Digital, on why HBForge is not open source
The guild is not the easiest way to build. It is the most honest way to build. Here is what you get in return.
Every production incident you've ever blamed on a transitive dependency ends here. HBForge has zero external dependencies — not "minimal", not "optional" — zero. When you ship on HBForge, the only code that runs is code you can read, understand, and trust. No supply-chain surprises at 3 AM. No abandoned maintainer pulling a package. No version conflict two levels deep. Guild engineers describe this as the first time they've felt in control of a production stack.
HBForge isn't a framework built to showcase ideas. It powers HyperBridge Digital's own internal products — live systems under real load, with real clients, real audits, and real consequences. When a guild engineer integrates HBForge, they're using the same stack the team that built it uses every day. There's no "works in theory, breaks in production" gap. Every API surface, every edge case, every performance decision was made under production pressure — not in a greenfield demo.
Most open-source contributions disappear into PR queues and never ship. In the guild, an accepted RFC means the T0 team implements your capability request in the next release cycle. Your name appears in the public changelog — permanently. This isn't a contributor credit buried in a README. It's authorship on a production framework used by engineers across India and enterprise clients globally. One good RFC is worth more on a CV than fifty merged PRs to a project no one uses.
Web7-L6 is the next generation of the web protocol stack — intent-first APIs, cryptographically attested outcomes, decentralised identity, zero-knowledge ML proofs, and L0 settlement. HBForge is the only framework that implements this stack today with 30/30 conformance tests passing. Guild members use these capabilities in production before any public release. By the time the ecosystem catches up to Web7, guild engineers will have 12–18 months of production experience that no one else has.
The guild's quality standards are not a checklist to get through. They're a way of thinking that changes how you write code outside HBForge too. Engineers who've worked in the guild report that they can no longer write a function without asking "does this have hidden side effects?" or accept a dependency without asking "do I need this, or do I need what it does?". The zero-dependency discipline, the named-exports architecture, the explicit error handling, the conformance testing mindset — these compound. You leave the guild a fundamentally better engineer than you entered it.
These are not aspirational guidelines. They are enforced gates. Guild members are expected to maintain them in any integration, RFC, or production deployment that touches HBForge.
Error()camelCase, PascalType)console.log in library code — use forge/notify or forge/traceforge/data or Node built-ins — never third-party_internal/ — never duplicated across modulesforge/test — no external test runnerseval(), Function(), or dynamic script injection anywhereexp, iss, aud all checkedGuild members don't push code to HBForge. They submit structured capability requests. The T0 team evaluates, decides, and implements. This is how the framework stays coherent.
The guild application takes time to review. Don't waste yours or ours if any of the following apply.
Once your guild token is issued, two lines in .npmrc and you're installing from our private registry — no public npm involved.
Registry hosted at registry.hbforge.dev · Powered by Cloudflare Workers + R2 · Zero third-party infra
Send a brief introduction: who you are, what you're building, why zero dependencies matters to you, and what production gap you think HBForge can close. Applications without a clear production use-case are declined without reply.
Applications are reviewed manually within 5–10 business days. If approved, you'll receive a signed access agreement and scoped npm token. If declined, you'll receive a one-line reason — no negotiation.