Knolo Project Registry: What Is Official, What Is Compatible
How the Knolo project registry on knolo.org records owner, repository, license, lifecycle state and security contact, and why unpublished beats invented.
Knolo is the open-source, local-first Knowledge Image runtime and format, released under Apache-2.0 with Knolo's @knolo/core on npm. As more code works with the Knolo format, a simple question gets harder to answer: which projects are Knolo's own, and which are compatible work by others? The Knolo project registry on knolo.org is where that answer is meant to live.
Why Knolo needs a project registry
A file format is only useful if people can tell which tools speak it, and who stands behind each one. Without a registry, a reader sees a package name and has to guess whether it is maintained, experimental or abandoned, and where to report a security problem. The Knolo registry is built to remove that guess. Its stated aim is to tell you what is official, what is experimental, and who maintains it.
What a Knolo project record holds
The registry is structured around a few fields per project:
- Owner: who maintains the project.
- Repository: where the source lives.
- License: the terms it ships under.
- Lifecycle state: one of proposed, active or archived.
- Security contact: a per-project disclosure path.
That last field matters. A security report should go to the people who can fix the code, through a channel they publish, not through a general contact form.
What the Knolo registry lists today
The registry is seeded from public source. Today it shows three entries:
- knolo-core: the TypeScript and Rust runtime for Knowledge Images, Apache-2.0, in the Knolo core repository on GitHub.
- @knolo/core: the published npm package, Apache-2.0.
- knolo (Python): a read-only, V5-compatible Python runtime.
The page says plainly that full records are not published yet. That is deliberate. knolo.org follows a simple rule: unpublished is better than invented. A blank field is honest; a filled-in guess is not.
Knolo-maintained versus compatible
The registry separates Knolo-maintained work from compatible or independent implementations. Being listed as compatible is not an endorsement. A compatibility claim should rest on evidence such as versioned tests and fixtures, as the Knolo compatibility page explains. The registry records who owns a project; compatibility evidence shows what it actually does with the bytes.
How the Knolo registry fits the open-technology process
The registry sits beside the other public Knolo records: Knolo specifications define the format, Knolo KIPs propose changes, and the Knolo lifecycle page explains how work moves between states. If you build a tool that reads or writes Knolo Knowledge Images, the registry is where its owner, license and security path should eventually be recorded.
Follow Knolo
Read the open records on Knolo at knolo.org, start building with the Knolo developer docs on knolo.dev, and follow the source in the Knolo GitHub repository.
knolo · open-technology · projects · governance · compatibility
