Implementations
Who speaks CTXPKG
Independent implementations are the point of a standard — and the trigger for shared governance
In plain terms: a standard is only real when more than one program speaks it. This page tracks every known implementation, what each one covers, and how to get yours listed.
1Known implementations#
lean-ctx
Reference implementation- Language:
- Rust
- Covers:
- Reader · Writer · Signer · Registry client
- Conformance:
- Level 1–3
- Maintainer:
- CTXPKG maintainers
Creates, signs, verifies, merges and installs packages. The implementation the test vectors were generated with. Released 3.11.4 fails the two map-form-dependency vectors; 3.11.5 is expected to pass all seven.
github.com/yvgude/lean-ctx@ctxpkg/verify
Verifier · release candidate- Language:
- TypeScript
- Covers:
- Reader (verification only)
- Conformance:
- Level 1–2 read
- Maintainer:
- CTXPKG maintainers
Zero-dependency verifier written from the spec text alone — integrity hashing and Ed25519 via node:crypto. Passes all seven test vectors. Release candidate 1.1.0 — published on npm (source: github.com/yvgude/ctxpkg-verify) together with LeanCTX 3.11.5; not yet installable.
conformance vectorsctxpkg.com
Registry- Language:
- Rust
- Covers:
- Registry protocol v1 (full surface)
- Conformance:
- Registry conformance
- Maintainer:
- CTXPKG maintainers
Public registry: signed publishing with six verification gates, secret scanning, quality scores, anonymous installs of free packages.
ctxpkg.comHonesty note: all three are currently maintained by the same team. The shared-governance trigger requires implementations from different maintainers — which is exactly why the section below exists.
2Conformance matrix#
| Capability | lean-ctx | @ctxpkg/verify | ctxpkg.com |
|---|---|---|---|
| Parse & load v2 graph | yes | yes | n/a |
| Parse & load v1 layers (§10 mapping) | yes | yes | n/a |
| Integrity verification (§8, text-based) | yes | yes | yes (publish gate) |
| Ed25519 signature verification (§9) | yes | yes | yes (publish gate) |
| Reject all 4 invalid test vectors | 3.11.5+ (3.11.4: not the map-form vector) | yes | n/a |
| Accept all 3 valid test vectors | 3.11.5+ (3.11.4: not the map-form vector) | yes | n/a |
| Write & sign packages | yes | no | n/a |
| Graph merge (Level 2) | yes | no | n/a |
| Cognitive state (Level 3) | yes | no | n/a |
| Registry protocol v1 endpoints | client | no | server |
Verified against the official test vectors (all seven), October 2026 — lean-ctx column refers to 3.11.5, @ctxpkg/verify to release candidate 1.1.0.
3Submit yours#
Built a reader, writer or registry? Getting listed takes one e-mail and passes through the same bar as ours:
- Run the seven test vectors — all three valid files must load, all four invalid files must be rejected.
- State your conformance level and which roles you cover (reader, writer, registry).
- Send the results, a link to your project and your maintainer identity to standard@ctxpkg.org.
The first listing from an independent maintainer does more than fill a table: it starts the clock on shared governance. We mean that as an invitation.