macOS
brew install tiger-vnclocal Homebrew formula metadata
brew
tiger-vnc のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。
インストール
brew install tiger-vnclocal Homebrew formula metadata
scoop install extras/vncviewerScoop official bucket manifest trees · bucket/vncviewer.json · ソース: api.github.com
winget install --id RealVNC.VNCViewer -eWindows Package Manager source index · RealVNC.VNCViewer · ソース: cdn.winget.microsoft.com
概要
High-performance, platform-neutral implementation of VNC
履歴
TigerVNC is a high-performance, multi-platform implementation of Virtual Network Computing. Its README explains VNC as a remote display system that lets a user view and interact with a desktop environment running on another computer over a network.
The official README gives TigerVNC's origin story directly: it is based on the RealVNC 4 and X.org code bases, started as a next-generation development effort for TightVNC on Unix and Linux, and split from TightVNC in early 2009 so TightVNC could focus on Windows platforms.
TigerVNC's technical identity is also defined by performance. The README says it supports a variant of Tight encoding accelerated by the libjpeg-turbo JPEG codec, which explains why the project became a frequent package choice for users who wanted an open VNC client/server stack with better speed than older VNC implementations.
The project includes both common cross-platform pieces and platform-specific tools. The README lists vncviewer on all platforms, winvnc on Windows, and Unix/Linux programs such as Xvnc, vncpasswd, vncconfig, x0vncserver, w0vncserver, and a systemd vncserver service.
TigerVNC's adoption follows the continuing need for remote graphical access to Unix and Linux desktops, lab machines, servers, and cross-platform GUI sessions. The official repository is maintained under the TigerVNC organization and shows a long-running C++ project with substantial stars, forks, releases, and active development.
In package-manager culture, TigerVNC is the kind of tool installed when SSH is not enough: developers, administrators, and researchers can add a VNC viewer or server from a package manager and connect to remote graphical environments without adopting a proprietary remote-desktop stack.
The Homebrew formula exposes the viewer and related command-line utilities on macOS, while Linux distributions commonly package both client and server pieces. This split packaging pattern is natural for VNC because some users only need a viewer and others need to host sessions.
The vncviewer manual documents the classic client workflow: run vncviewer with a host and display number or port, use a .tigervnc configuration file, authenticate with a password, and open a window showing the remote desktop.
On Unix/Linux, TigerVNC is also used to create virtual X desktop sessions with Xvnc, manage VNC passwords with vncpasswd, configure a running server with vncconfig, and expose an existing X display through x0vncserver.
For package users, the practical pattern is simple: install the package, set or store a VNC password, start or connect to a server, and keep the rest of the workflow in shell scripts, service units, or desktop launchers.
TigerVNC is significant because it packages a historically important remote-desktop protocol into reproducible open-source builds. It sits at the intersection of X11, remote access, compression, authentication, systemd services, and desktop packaging.
Its package details matter more than average: client-only versus server components, password-file locations, XDG configuration paths, FLTK viewer behavior, and platform support all affect whether a user can connect to a remote GUI from a freshly provisioned machine.
セキュリティ状態
tiger-vnc に一致するローカルシークレット処理マニフェストは見つかりませんでした。将来の対応で安定したパッケージ URL を使えるよう、Nucleus パッケージメタデータはここに公開されています。
エージェントに無人実行させる前に、このツールが平文の認証情報を読むか、リモート状態を書き込むか、成果物を公開するか、プラグインを起動するかを確認してください。
local files
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.
Config paths the tool may read or write during local use.
$XDG_CONFIG_HOME/tigervnc/default.tigervnc~/.config/tigervnc/default.tigervncCredential-bearing paths to review before unattended agent runs.
$XDG_CONFIG_HOME/tigervnc/passwd~/.config/tigervnc/passwd実行可能ファイル
| コマンド | 種類 | 公開範囲 | メモ |
|---|---|---|---|
vncconfig | cli | グローバル実行可能ファイル | |
vncpasswd | cli | グローバル実行可能ファイル | |
vncsession | cli | グローバル実行可能ファイル | |
vncviewer | cli | グローバル実行可能ファイル | |
x0vncserver | cli | グローバル実行可能ファイル |
鮮度
これらの信号は、ページ生成時期、パッケージマネージャの活動、上流リリース比較を分けて示します。バージョン遅れは、証拠 URL と比較可能なバージョンがある場合だけ警告されます。
https://github.com/TigerVNC/tigervnc
インストールメタデータ
| パッケージキー | brew:tiger-vnc |
|---|---|
| バージョン | 1.16.2 |
| パッケージマネージャ | Homebrew |
| パッケージマネージャページ | https://formulae.brew.sh/formula/tiger-vnc |
| ホームページ | https://tigervnc.org/ |
| リポジトリ | https://github.com/TigerVNC/tigervnc |
| 上流ドキュメント | https://github.com/TigerVNC/tigervnc/wiki |
| ライセンス | GPL-2.0-or-later |
| ソースアーカイブ | https://github.com/TigerVNC/tigervnc/archive/refs/tags/v1.16.2.tar.gz |
| 最終更新 | 2026-05-11T18:07:38Z |
| Pulse | updated |
| 依存関係 | fltk@1.3, gettext, gmp, gnutls, jpeg-turbo, nettle, pixman |
| ビルド依存関係 | cmake, gettext |
| Bottle | 利用可能 (対象 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | 未定義 |
| サービス | 宣言なし |
レジストリ情報
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | tiger-vnc |
| Version Scheme | 0 |
| Revision | 1 |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
ソースデータベース一致
一致は外部パッケージマネージャインデックスから取得され、ローカルの Automic Vault パッケージリンクとは分けて表示されます。
extras/vncviewer
scoop install extras/vncviewerRealVNC.VNCViewer
winget install --id RealVNC.VNCViewer -eソース経路
このページは scripts/generate-pkg-sqlite.py が生成した非公開のパッケージ SQLite アーティファクトから av-web によって提供されます。
View the package source record on GitHub.