Skip to content

OMUS v1.0.0 — Every mouse. One system.

Choose a tag to compare

@github-actions github-actions released this 19 Sep 18:55
· 38 commits to main since this release
4e2f64f

OMUS v1.0.0 — Every mouse. One system.

OMUS is One Mouse Universal System: the public successor to Mouse Control.
This is the first public OMUS release; the supported transition is Mouse
Control v0.9.9 → OMUS v1.0.0.
This release introduces the omus command, OMUS desktop identity and canonical
artwork, lossless/idempotent migration from legacy configuration, data, and
cache paths, and package transitions that preserve upgrades from v0.9.9. The
mouse-control command and mouse_control Python namespace remain compatible.
The canonical repository is now DonGeronimo7/OMUS; GitHub redirects links
from DonGeronimo7/mouse-control after the repository rename.

The canonical service is omus.service. Installing it disables the legacy
unit before enabling OMUS so only one remapper owns evdev/HID resources.
Hardware write authority, discovery gates, remapping, reconnect behavior,
DPI/polling, and independent notification replacement IDs are unchanged.

Primary artifacts are omus-1.0.0-1.fc44.noarch.rpm,
omus_1.0.0_all.deb, OMUS-1.0.0-x86_64.AppImage,
omus-1.0.0-py3-none-any.whl, and omus-1.0.0.tar.gz.

Mouse Control v0.9.9

Mouse Control v0.9.9 completes the canonical full-screen product experience,
adds a conservative native-lighting foundation, and extends the hardened
release pipeline with point-in-time VirusTotal analysis of every primary
distributable.

Complete canonical TUI

  • The single canonical controller now includes dedicated Lighting, Updates,
    Tools / Advanced, About, and complete Service-control pages.
  • A checked-in capability inventory enforces CLI/TUI parity while preserving
    installed research and expert workflows under Tools / Advanced.
  • Update checks run only after an explicit action. RPM, DEB, AppImage, and pip
    reuse the existing updater, checksum, trusted-origin, package-ownership,
    approval, and service-restoration paths. Source, unknown, package-source, and
    incompatible AppImage installs are represented honestly and cannot expose an
    unsafe update action.

Safe native-lighting architecture

  • Optional per-device lighting supports multiple zones and native Off, Static,
    Breathing, and Spectrum modes, with RGB24 #RRGGBB, brightness, speed, and
    per-mode persistence vocabulary.
  • Lighting failures remain independent from DPI, polling, remapping, buttons,
    battery, and service health. Volatile state is reconciled once per live
    backend and after a genuine rebind.
  • Shared-device-config lighting is refused unless the exact backend proves a
    trustworthy baseline-preserving read/modify/write operation.
  • Source-backed lighting protocol knowledge remains write-disabled. No newly
    sourced lighting family is claimed as physically validated, and unqualified
    lighting writes remain disabled.

Retained discovery, reliability, and supply-chain protection

  • Existing Automatic Discovery, protocol knowledge, native HID++, G305,
    remapping, reconnect, notifications, service lifecycle, updater, and
    PROVEN-only hardware-write behavior are retained.
  • CodeQL, OpenSSF Scorecard, dependency auditing, immutable action pins,
    least-privilege permissions, workflow-policy checks, wheel reproducibility,
    exact artifact allowlists, SHA256SUMS, CycloneDX SBOM generation, and
    keyless GitHub provenance/SBOM attestations remain release gates.
  • The five primary artifacts are submitted at four per minute through the
    immutable-pinned VirusTotal action. The follow-up verifier waits for completed
    analyses, records filename, SHA-256, detection counts, and direct report links
    in these release notes, and fails the scan workflow on any malicious or
    suspicious result. VirusTotal is a point-in-time signal, not certification.

Validation boundary

The canonical TUI received user physical acceptance before this release. New
lighting families and their write behavior remain unverified on physical
hardware. Automated tests and hosted packaging checks do not broaden hardware
write authority.

Downloads

  • RPM: mouse-control-0.9.9-1.fc44.noarch.rpm
  • DEB: mouse-control_0.9.9_all.deb
  • AppImage: Mouse-Control-0.9.9-x86_64.AppImage
  • Wheel: mouse_control-0.9.9-py3-none-any.whl
  • Source: mouse_control-0.9.9.tar.gz
  • CycloneDX SBOM: mouse-control-0.9.9.cdx.json
  • Integrity manifest: SHA256SUMS

VirusTotal analysis

VirusTotal scanned the five primary distributable artifacts. Results are a point-in-time signal, not a certification of safety.

Artifact SHA-256 Result at scan time Analysis
OMUS-1.0.0-x86_64.AppImage 7f93106e071d7fc47c3aa9e93648f40dbf6b7c6840026874cdecd82ab763b649 0 detections at scan time VirusTotal analysis
omus-1.0.0-1.fc44.noarch.rpm 84b653802fc6aac697d1a544a8f67012f50f866c1ee4373de3656aaabffde55b 0 detections at scan time VirusTotal analysis
omus-1.0.0-py3-none-any.whl bd07ec92b701f0f2aa1d2aa8768d288cda3577b06aa8de24fdc04c2785d14e13 0 detections at scan time VirusTotal analysis
omus-1.0.0.tar.gz 3f7eaab7c8ff4350007e909cb413c3a90c21ccf46cfbcfed3069209bdb9d5b0a 0 detections at scan time VirusTotal analysis
omus_1.0.0_all.deb 9efe39074791e920f85e6312b6dde9bea9fac19d6020d3238e61881fecf44dc5 0 detections at scan time VirusTotal analysis