Skip to content
CAI
Software that uses CAICheck a score

AabhaJahagirdar/VelociRust

63.1

Adequate · 8 November 2026

62.2k

lines of production code

Rust

primary language

7

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Behavioural changes

Application rebranded from Lapce to Velocirust

The application has been rebranded from Lapce to Velocirust. This change updates the binary name, CLI tool name, and internal module references (e.g., \lapce\_app\ to \velocirust\_app\, \LapceConfig\ to \VelocirustConfig\). User-facing strings, including the window title, 'About' dialog content, and command-line help text, now display 'Velocirust'. Configuration file paths have been updated from \.lapce/\ to \.velocirust/\. Logging targets, notification identifiers, and external resource URLs (GitHub, Matrix, website) have been switched to the Velocirust namespace.

(repo-wide) · high confidence

Application renamed from Lapce to Velocirust across all packaging and distribution assets

The code editor has been rebranded from Lapce to Velocirust. This change updates the application name, executable names (e.g., lapce to velocirust), desktop identifiers, and bundle identifiers in the Linux .desktop and .metainfo files, macOS Info.plist, Windows WiX installer, and Docker build scripts. All URLs, GitHub repository references, and proxy installation scripts have also been updated to reflect the new Velocirust identity.

extra · high confidence

Project rebranded from Lapce to Velocirust

The code editor has been renamed from Lapce to Velocirust across all build artifacts and distribution channels. The binary, package names, desktop entries, and Docker images now use the Velocirust identifier, and all upstream GitHub repository references in the changelog and documentation have been updated to point to the new Velocirust project URLs.

(repo-wide) · high confidence

VelociRust rebrands from Lapce with new AI routing and updated identity

The editor is rebranded from Lapce to VelociRust, updating the application name, CLI arguments, window titles, and all internal configuration structures (e.g., \LapceConfig\ to \VelocirustConfig\). The UI reflects this change with new branding in the 'About' dialog, updated links to VelociRust's GitHub and Matrix channels, and renamed color/icon theme keys. Additionally, the proxy introduces a new AI routing system that directs autocomplete requests to a local model while sending complex reasoning tasks to the Gemini cloud API.

velocirust-app, velocirust-proxy · high confidence

Dependencies

Project rebranded to Velocirust with new AI and runtime dependencies

The codebase has been renamed from Lapce to Velocirust, updating all package names (e.g., velocirust-app, velocirust-core), binary targets, and workspace members. This change introduces new dependencies for AI integration (adk-gemini) and asynchronous runtime (tokio, reqwest), while also updating the wasmtime toolchain to v11.0.1 and refreshing various underlying crates in the lockfile.

(dependencies) · high confidence

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

Score

  • CAI 60 → 63 (+3.3)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 56 → 56 (+0.0)
  • Architecture 92 → 91 (-0.7)
  • Maturity 53 → 62 (+8.7)
  • Readiness 71 → 71 (-0.0)
  • Security 66 → 70 (+4.3)
  • Event Sourcing 100 → 100 (+0.0)
  • Performance 91 → 91 (+0.0)

Resolved (9)

  • Ambiguous distinction between 'color' and 'style_color'. Both return a Color based on a string name. It is unclear if 'style_color' refers to UI styling specifically while 'color' refers to syntax highlighting, or if they are aliases.
  • Duplicate persistence operations for AppData. It is unclear why two methods exist for the same entity. If 'save' is a high-level transactional wrapper and 'insert' is low-level, the API surface exposes implementation details unnecessarily.
  • Duplicate persistence operations for WindowData. Same ambiguity as AppData regarding 'save' vs 'insert' semantics.
  • Duplicate persistence operations for WindowTabData. Same ambiguity as AppData and WindowData.
  • Medium CVE: [GHSA redacted] (Cargo.lock)
  • Medium vulnerability: RUSTSEC-2026-0367 (Cargo.lock)
  • Redundant methods for SVG retrieval. 'files_svg' takes a slice of paths, 'file_svg' takes a single path. While one could call the single-path version in a loop, providing both suggests a batch optimization. However, the naming inconsistency ('files' plural vs 'file' singular) and the fact that one is a wrapper for the other (likely) creates API bloat.
  • Redundant operations with ambiguous distinction. Both methods appear to persist disabled voltages to the database. The naming convention 'save' vs 'insert' is inconsistent across the API (e.g., 'save_app' vs 'insert_app'), and it is unclear if 'save' implies an upsert/merge while 'insert' implies a strict add, or if they are functionally identical aliases.
  • Same redundancy as above, but scoped to workspace-specific voltages. The parallel existence of 'save' and 'insert' variants for the same logical operation creates confusion regarding transactional behavior and idempotency.

New (15)

  • Critical CVE: [GHSA redacted] (Cargo.lock)
  • Critical CVE: [GHSA redacted] (Cargo.lock)
  • Medium advisory (unsound): RUSTSEC-2026-0386 (Cargo.lock)
  • Medium advisory (unsound): RUSTSEC-2026-0395 (Cargo.lock)
  • Medium advisory (unsound): RUSTSEC-2026-0397 (Cargo.lock)
  • Medium advisory (unsound): RUSTSEC-2026-0399 (Cargo.lock)
  • Medium advisory (unsound): RUSTSEC-2026-0400 (Cargo.lock)
  • Medium advisory (unsound): RUSTSEC-2026-0401 (Cargo.lock)
  • Medium advisory (unsound): RUSTSEC-2026-0402 (Cargo.lock)
  • Medium advisory (unsound): RUSTSEC-2026-0404 (Cargo.lock)
  • Medium advisory (unsound): RUSTSEC-2026-0406 (Cargo.lock)
  • Medium vulnerability: RUSTSEC-2026-0403 (Cargo.lock)
  • Medium vulnerability: RUSTSEC-2026-0410 (Cargo.lock)
  • Medium vulnerability: RUSTSEC-2026-0418 (Cargo.lock)
  • Outdated: backtrace

Changes since last survey

  • 2 commits — 2 feature/other, 0 fixes

By area

  • (root) — 2 commits

Notable commits

  • change: Fix README header punctuation for clarity
  • change: Fix header formatting in README.md

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Survey your own repository

AabhaJahagirdar/VelociRust was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.

About this page

  • The score is its most recent published measurement, taken on 8 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit 551fab3ef7bd7d2977babe31d454035beb4320e6 — the exact code this score is about.
  • Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-45ab2cab63de.