16
🏝️ Submodules with no production dependencies
Almost half the codebase — including rights-management, vault, auditable-item-graph, and engine — composes entirely from @twin.org packages. External dependency surface is concentrated where it needs to be.
3×
📚 Standards is a statistical outlier
At 131,270 lines, twin-standards is 3.2× larger than the next biggest repo. It covers 14 standards packages — W3C, GS1, DCSA, UNECE, VDA, Dublin Core, FOAF, and more. UNECE is the only machine-generated one; the rest are hand-crafted.
7
⛓️ Submodules that touch the IOTA ledger
dlt, identity, wallet, hierarchies, notarization, nft, and verifiable-storage all have an IOTA-specific connector or direct @iota/* dependency. The remaining 27 submodules are fully chain-agnostic.
17
🧲 Production deps absorbed by twin-framework
Framework takes on 17 of 54 unique external deps — crypto primitives (noble, scure), i18n, CLI, schema tooling — and re-exports them so 33 downstream repos don't have to declare them directly.
34/34
✅ Perfectly uniform toolchain
TypeScript 6.0.3, vitest 4.1.9, ESLint 10.5.0, prettier 3.8.4, release-please 17.9.0 — identical across every submodule. Version skew across 34 repos is zero.
4
☁️ Infrastructure vendors, all localized
AWS (blob-storage, entity-storage, messaging), Azure (blob-storage, entity-storage), GCP (blob-storage, entity-storage), and HashiCorp Vault (vault) are each confined to dedicated connector submodules. No vendor dependency bleeds into the core services.