Automic VaultAutomic Vault

brew

Install wails with Homebrew, MacPorts, Nix

Create beautiful applications using Go. Version 2.13.0 via Homebrew; verified 2026-07-07.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install wails

local Homebrew formula metadata

MacPortsverified · 94%
sudo port install wails

MacPorts ports tree · devel/wails/Portfile · source: api.github.com

Linux

Nixverified · 92%
nix profile install nixpkgs#wails

nixpkgs package indexes · pkgs/by-name/wa/wails/package.nix · source: api.github.com

overview

Package summary

Create beautiful applications using Go

Commands and aliases

  • wails

history

Project history and usage

Wails is a Go desktop-application framework that pairs a Go backend with a web frontend while using native platform webview components instead of bundling a Chromium runtime. It is commonly described by the project as a lightweight Electron alternative for Go developers.

Project history

Creator and maintainer Lea Anthony traced the idea to wanting an HTML, JavaScript, and CSS interface for Restic without making users run a web server in a browser, then discovering the cross-platform WebView library. The early problem Wails set out to solve was the hard synchronization boundary between a native Go backend and a web frontend.

The first public code appeared on GitHub on May 1, 2019 after roughly a year and a half of private development. Wails v1 was announced on December 10, 2019 as the stable-API milestone after nearly two years of work; the v1 post also listed the path toward v2, including replacing WebView as the windowing library, more desktop integration, and a broader refactor.

Wails v2 was released on September 22, 2022 after about 18 months from the first v2 alpha and about a year from the first beta. The v2 release was a major transition: it added modern templates, Vite-powered live development, Windows WebView2 support, native menus and dialogs, TypeScript model generation, packaging improvements, and a runtime aimed at richer desktop applications.

The v3 roadmap, published in January 2023, framed the next major cycle around a more programmatic API, better multi-window support, static-analysis-based bindings generation, and a more transparent build system. As of July 2, 2026, the GitHub repository metadata showed more than 35,000 stars, active development on the master branch, v2 as the stable line, and v3 alpha releases in progress.

Adoption history

Wails grew from a Go-community project into one of the best-known Go desktop frameworks. The v1 announcement reported about 1,300 GitHub stars and around 10,000 documentation-site users in late 2019, while the v2 announcement credited roughly 2,200 commits by 89 contributors between the initial alpha and v2 release.

The project positions itself for developers who want native-feeling desktop applications without Electron's bundled-browser footprint. The docs emphasize templates for Svelte, React, Preact, Vue, Lit, and vanilla JavaScript, plus native menus, dialogs, theming, WebView2 on Windows, and platform packaging.

How it is used

A typical Wails project uses the `wails` CLI to create, develop, build, and package an app. Developers write Go methods in the backend, call them from JavaScript, and let Wails generate TypeScript models for Go structs so frontend and backend can share data shapes.

During development, `wails dev` runs a native desktop shell while serving frontend assets from disk and reloading as Go or frontend files change. For release builds, Wails bundles frontend assets into a native executable and can package platform-specific app artifacts.

Why package nerds care

In package terms, Wails is important because it represents the Go ecosystem's native-webview answer to Electron-style desktop development. It turns a Go toolchain plus frontend build into a single distributable desktop app, so packagers and developers often compare it with Electron, Tauri, Fyne, WebView, and Lorca-like approaches.

Timeline

  • May 1, 2019: the first public Wails code was released on GitHub, according to Lea Anthony's v1 history post.
  • December 10, 2019: Wails v1 was announced as the stable-API milestone.
  • September 22, 2022: Wails v2 was released after a long alpha and beta cycle.
  • January 17, 2023: the project published the Road to Wails v3, outlining multi-window and build-system changes.
  • July 2, 2026: GitHub API metadata showed the repository still actively maintained with more than 35,000 stars.

Related projects

  • Wails is usually discussed alongside Electron and Tauri because all three let developers build desktop software with web technologies. It also has roots in the WebView project and in the Go ecosystem's desire for desktop apps that do not require shipping a separate browser runtime.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Installs with 1 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
wails.json

executables

Installed executables

CommandKindExposureNote
wailscliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version2.13.0
manager updated2026-07-07
local dataok
upstreamcurrent
latest detectedv2.13.0

https://github.com/wailsapp/wails

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:wails
Version2.13.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/wails
Homepagehttps://wails.io
Repositoryhttps://github.com/wailsapp/wails
Upstream docshttps://wails.io/docs/introduction
LicenseMIT
Source archivehttps://github.com/wailsapp/wails/archive/refs/tags/v2.13.0.tar.gz
Last updated2026-07-07T05:10:28Z
Pulseupdated
Dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namewails
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

wails

nix profile install nixpkgs#wails
  • normalized package name match
  • Matched by: Wails
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/wa/wails/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
MacPorts95%

wails

sudo port install wails
  • normalized package name match
  • Matched by: Wails
MacPorts ports tree · api.github.com · MacPorts ports tree: devel/wails/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment