$ rev-local roadmap
What’s planned
Where rev-local stands today, why nothing else is scheduled, and what it isn’t going to do.
Where it stands
Everything in the v1 scope is done.
That includes discovery, review, the engine adapters, per-engine token accounting, the publish and audit paths, a live-engine acceptance suite, a security review of the publish and secrets paths, and installer builds for macOS, Windows and Linux. There’s no open work in the tracker. There are no prebuilt downloads yet, but the source is public under Apache 2.0 and builds with Cargo.
Planned work
Nothing new is scheduled
Rev-Local was built to a written specification, and all of it is implemented, down to the config keys it mentions. No feature work is queued. What comes next depends on the first people who run it, so get in touch if you’d like to be one of them.
Out of scope
Not on the roadmap
If you need one of these, rev-local isn’t the right product for you.
-
Uploading your repository
Rev-Local reviews code on hardware you control. That’s the whole idea. Sending code to the cloud would make it a different product with a different threat model.
-
A CI service
It reviews changes it finds locally. It doesn’t host your pipeline.
-
Fixing what it finds
It reports problems. Whether to change the code is your call.
How this is maintained
Every item above is tracked in our own issue tracker, and this page is rewritten from it. Open bugs and security work are left off. Those stay in the tracker until they’re closed.
Want more detail on something here, or to know where it stands? Write to dmoore@
Next
Build rev-local
It’s open source under the Apache 2.0 license. There are no prebuilt downloads yet, so you build it from source with Rust.
git clone https://github.com/dmoore-dwmmholdings/rev-local
cargo build --release --workspace
cargo tauri build --features desktop
The desktop app needs tauri-cli and is built from crates/revlocal-tauri. On Linux you’ll also need the WebKitGTK development packages. The public source is updated in batches, so it can be behind the newest features described here.
Questions, or something it doesn’t do yet? Email dmoore@