The local tools are open source
Erden's local tools are now public at cbnsndwch/erden, under Apache 2.0.
If checks are going to count as evidence, you should be able to read how they work.
What's in the repository
| Path | What it is |
|---|---|
apps/cli/ | The erden CLI: init, check, install, pack, publish, doctor |
packages/client/ | Registry client: upload, download, reads |
packages/contracts/ | Manifest, lockfile, check report and registry wire formats |
packages/project/ | Local project operations: check, install, pack, the package store |
packages/ontology/ | Local assembly, SHACL, competency questions |
packages/package-format/ | The package archive format |
reasoner/ | The reasoner's Rust source, qualification, protocol and resolver |
shacl/ | The erden-shacl engine's Rust source, qualification and resolver |
There's a small demo project too. Its ontology declares an artifact, the reasoner infers its superclass type, and SHACL validates that inferred fact.
Trying it today
The first public release is still being prepared, so for now you build from source. Each engine build is checked against its pin and only installed if it's byte-identical.
When releases land, each platform (Linux x64 and arm64, macOS arm64, Windows x64) gets one archive holding the CLI, the Node.js runtime and both engines. Install scripts carry their release's digests and refuse any other file, and there's an offline path for machines with no network access.
What this doesn't include
The hosted registry is a separate, closed-source service, and self-hosting isn't offered. Publishing, discovery and the web UI live there.
I'm also not taking outside pull requests yet, which keeps the code under a single copyright holder while the project takes shape. Issues are very welcome, though: bugs, questions, missing features, anything that got in your way.
Next up is getting the hosted side in front of its first outside users.