RinaWarp is built for real repositories, real commands, and real verification. The product should show what it inspected, ask before high-impact changes, and keep proof attached to every repair.
The current public release is available for Linux as a checksum-verified .deb and AppImage. macOS and Windows are pending signed, notarized, and smoke-tested installers before they return to the download page.
RinaWarp runs developer work from the selected workspace and keeps repository inspection tied to the local project context.
Repairs should stay scoped to the project you opened. High-impact actions must be visible before they run.
File changes, install steps, and risky commands should require clear approval instead of happening silently.
Repair work should preserve a recovery path so developers can understand and undo changes when a fix is not right.
Build, test, and health-check output should stay attached to the repair so success is evidence-based.
Logs and telemetry should avoid secrets, tokens, file contents, command output, and private paths unless they are safely redacted or hashed.
Local memory should help RinaWarp remember project context without turning private code into a public profile. Cloud sync is optional, not the default. Developers should be able to export or delete saved memory.
Capability packs need a manifest, publisher, version, permissions, risk level, install approval, disable control, changelog, and proof of what ran. Packs should not bypass Agent Thread, policy, execution, verification, and proof.
Installers are linked through public release metadata and checksums. If the SHA256 checksum does not match the published file, do not run the installer.
Verify downloadsRinaWarp should measure activation events like install, first launch, first scan, first proof, fix approval, proof export, marketplace install, memory saved, memory cleared, and crash report creation. It should not collect source files, terminal output, secrets, tokens, or private paths.
Read privacy policy