install

Additional install commands

macOS

Homebrewverified · 100%

brew install vrc-get

local Homebrew formula metadata

MacPortsverified · 94%

sudo port install vrc-get

MacPorts ports tree · devel/vrc-get/Portfile · source: api.github.com

Linux

Nixverified · 92%

nix profile install nixpkgs#vrc-get

nixpkgs package indexes · pkgs/by-name/vr/vrc-get/package.nix · source: api.github.com

Windows

Windows Package Managerverified · 92%

winget install --id anatawa12.vrc-get -e

Windows Package Manager source index · anatawa12.vrc-get · source: cdn.winget.microsoft.com

overview

Package summary

Open Source alternative of Command-line client of VRChat Package Manager

Project links

Commands and aliases

vrc-get

history

Project history and usage

vrc-get is an open-source command-line client for the VRChat Package Manager, the package-management system used by VRChat Creator Companion for Unity-based avatar and world projects. The project is community-developed and explicitly not an official VRChat project.

Project history

The upstream README defines vrc-get's initial goal as providing an open-source command-line client for VRChat Package Manager and adding functionality beyond the official VPM commands. This positioned it as a scriptable and cross-platform alternative for creators who wanted package operations outside the official GUI-first workflow.

In 2024, the project expanded its stated goals to include a better cross-platform Creator Companion. That expansion is embodied by ALCOM, the graphical application built around the vrc-get toolchain and advertised by the project as a fast open-source alternative to VRChat Creator Companion on Windows, macOS, and Linux.

Adoption history

vrc-get's adoption is tied to the VRChat creator ecosystem's move toward VPM packages. VRChat's own Creator Companion documentation describes VPM as using a Unity Package Manager-compatible format for installing, updating, and managing assets, tools, and prefabs used to make VRChat content.

The author announced ALCOM 0.1.0 on the VRChat Ask forum in April 2024 as a non-beta unofficial Creator Companion alternative that can be used alongside VCC and can install or update multiple packages at once. Community references since then commonly describe vrc-get and ALCOM together: the CLI for automation, the GUI for daily project management.

How it is used

vrc-get is used to install, remove, search, resolve, and update VPM packages in VRChat projects. It operates on VCC-compatible project layouts and package manifests, making it useful in scripts, CI-like project maintenance, or non-Windows environments where creators still need to manage VRChat Unity packages.

ALCOM wraps the same toolchain in a graphical interface for creators who want the VCC-style workflow with faster package operations and cross-platform support.

Why package nerds care

vrc-get is package-nerd significant because it brings familiar open-source package-manager ergonomics to a creator ecosystem that otherwise centers an official desktop companion app.

It is also a useful example of a community package manager growing a GUI wrapper after the CLI proved valuable, rather than starting as a monolithic app.

Timeline

2020s: vrc-get begins as an open-source command-line client for VRChat Package Manager.
2024: The project adds a stated goal of providing a better cross-platform Creator Companion.
2024-04-18: ALCOM 0.1.0 is announced on the VRChat Ask forum as an unofficial Creator Companion alternative.
2020s: vrc-get and ALCOM continue as a shared Rust-based command-line and graphical toolchain on GitHub.

Related projects

vrc-get is directly related to VRChat Creator Companion, VRChat Package Manager, Unity Package Manager-compatible manifests, and ALCOM.
It is also related to community VPM repositories used by avatar and world creators to distribute SDKs, tools, shaders, and prefabs.

Sources

security posture

Risk level: orange

infrastructure mutation or orchestration signal.

Risk classifier

orange risk · medium confidence · infrastructure

Why

infrastructure mutation or orchestration signal

Signals

text:package manager

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 5 platform targets.
Build metadata lists 1 build 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: $XDG_DATA_HOME/VRChatCreatorCompanion/vrc-get-settings.json
Windows: %LOCALAPPDATA%/VRChatCreatorCompanion/vrc-get-settings.json

executables

Installed executables

Command	Kind	Exposure	Note
`vrc-get`	cli	global 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-11-04

manager version1.9.3

manager updated2026-10-24

local dataok

upstreamcurrent

latest detectedv1.9.3

https://github.com/vrc-get/vrc-get

okNo freshness warnings were generated.

install metadata

Package metadata

Package key	brew:vrc-get
Version	1.9.3
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/vrc-get
Homepage	https://github.com/vrc-get/vrc-get
Repository	https://github.com/vrc-get/vrc-get
License	MIT
Source archive	https://github.com/vrc-get/vrc-get/archive/refs/tags/v1.9.3.tar.gz
Last updated	2026-10-24T05:16:37Z
Pulse	updated
Build dependencies	rust
Bottle	available (on arm64_golden_gate, arm64_linux, arm64_sequoia, arm64_tahoe, x86_64_linux)
Homebrew post-install	not defined
Service	none declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	vrc-get
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
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%

vrc-get

nix profile install nixpkgs#vrc-get

normalized package name match
Matched by: Vrc Get

nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/vr/vrc-get/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

MacPorts95%

vrc-get

sudo port install vrc-get

normalized package name match
Matched by: Vrc Get

MacPorts ports tree · api.github.com · MacPorts ports tree: devel/vrc-get/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

winget95%

anatawa12.vrc-get

winget install --id anatawa12.vrc-get -e

normalized package name match
Matched by: Vrc Get

Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: anatawa12.vrc-get from https://cdn.winget.microsoft.com/cache/source.msix

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

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.

Combined YAML source

View the package source record on GitHub.

combined/vrc-get.yml

Used sources

Geiger risk classifier
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
pkg.so package database
pkgdb category and tag curation

Install vrc-get with Homebrew, MacPorts, Nix, winget