How we verify Metronome installs

Name: Metronome
Availability: InStock
Author: Metronome

Cadence Bind treats a install guide install line as verified when the package id or asset filename resolves on a public index or GitHub Releases tag cited in research notes.

What we check

GitHub Releases asset names for ZaneH/guide, preferring guide-*-x64-noyt.exe on Windows.
winget id Metronome.This guide in microsoft/winget-pkgs.
Homebrew cask install guide on formulae.brew.sh.
Snap install guide on the Snap Store.

What we mark unverified

Installer prompts we could not run on a real machine stay marked unverified in research notes. Skip invented SmartScreen publisher strings.

Corrections

Send corrections via contact. Upstream bugs go to ZaneH/metronome.

Editorial work here means checking GitHub Releases asset names, package registries when they exist, and licence files on the review date. Commands that were not run on a real machine stay marked unverified in research notes.

Readers should leave with one honest install door, not a pile of mirrored setups. When a registry has no package, the guide says so instead of inventing an id.