Install and Verify DevHud
DevHud is distributed as a coordinated release. A release is public only when its desktop packages, mobile stores, Chrome extension, API, updater, and documentation have passed their independent checks.
Desktop
Supported systems are macOS 13 or later, Windows 10 22H2 or later, and Ubuntu 22.04 LTS using X11. Releases provide x64 and Arm64 artifacts where listed: macOS disk images, Windows MSI or NSIS installers, and Ubuntu AppImage or Debian packages. Native Wayland is not supported.
Download from Delino OSS GitHub Releases. Verify the published SHA-256 checksums and signed release evidence before opening the installer. Updates retain the package type you installed.
The release evidence uses Sigstore bundles. With cosign installed, download the selected artifact and the devhud-v<VERSION>-release-evidence.tar.gz archive from the same release. The checksum manifest and Sigstore evidence are stored inside that archive rather than published as separate release assets. Extract it into a new, empty directory and inspect the archive contents before extraction; do not extract it over an existing directory or trust files outside the expected relative paths:
Then authenticate the extracted checksum manifest with:
The expected signer is the delinoio/oss package-devhud-private.yml GitHub Actions workflow running from refs/heads/main; do not substitute an identity from another repository, workflow, ref, or issuer. After that succeeds, verify every archive-owned evidence file against the authenticated manifest from inside its directory. The separately published installers are not archive members, so exclude their root-level entries while requiring every packaged evidence entry:
Do not use --ignore-missing: a missing SBOM, provenance record, validation record, or updater signature must fail verification. Then verify the downloaded artifact against its matching SHA256SUMS entry. Verify the artifact's matching Sigstore bundle from release-evidence/sigstore/ with the same identity and issuer before opening it.
Before opening the package, bind the verification to the requested release: confirm that the release page is tagged devhud@v<VERSION>, resolve that tag to its commit, and require the extracted artifact provenance to identify that exact source revision. Also confirm that the artifact's embedded release metadata identifies <VERSION> and that its provenance subject and checksum entry identify the artifact you downloaded. If the tag, source revision, embedded version, artifact name, or digest does not match, discard the package and evidence archive rather than opening it.
Windows verification
In PowerShell, use the Windows-provided tar.exe and Get-FileHash commands to inspect and verify the release evidence before opening an MSI or NSIS installer. Install the Windows build of cosign separately, then run:
Use the same signer and issuer to verify the matching artifact bundle under release-evidence\sigstore. Confirm the release tag, source revision, embedded version, artifact name, and digest all match the requested release; discard any mismatch.
Mobile stores
Install iOS 16 or later from the Apple App Store, or Android 10/API 29 or later from Google Play. Mobile updates are store-managed. Both packages include the optional one-Deck home-screen widget.
Chrome extension
Install DevHud from the Chrome Web Store. The extension is a permission-scoped context picker: it does not continuously observe pages, and it does not collect cookies, storage, console output, or network traffic. The picker is unavailable in incognito tabs; this is expected, and DevHud falls back to capture without browser context plus manual repository selection. After an explicit picker gesture, it scans up to 10,000 candidate elements across the active page. The picker times out after 30 seconds; if it disappears, restart the picker gesture. If the page exceeds that bound, or the selected subtree exceeds 10,000 total nodes, it degrades to capture without browser context and requires manual repository selection. Otherwise, it retains and persists only the selected, sanitized context. A Chrome-assisted RealQA draft includes that browser context by default when submitted, so the redacted URL, page title, user agent, viewport and bounds, accessibility values, and sanitized markup may be published in the GitHub issue. Review the draft and use its browser-context removal control before submitting if you do not want to share those details. Pair it from DevHud Settings after installing the desktop app.
Verification checklist
- Confirm the download source and platform match the release notes.
- Confirm the checksum and platform signature where your operating system provides one.
- Open DevHud and complete first-run setup before pairing Chrome or enabling a widget.
- If a release is under store review, wait for the coordinated release rather than treating one package as generally available.