Automic VaultAutomic Vault

brew

Install storj-uplink with Homebrew, Nix, winget

Uplink CLI for the Storj network. Version 1.158.3 via Homebrew; verified 2026-07-07.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install storj-uplink

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#storj-uplink

nixpkgs package indexes · pkgs/by-name/st/storj-uplink/package.nix · source: api.github.com

Windows

Windows Package Managerverified · 92%
winget install --id Storj.Uplink -e

Windows Package Manager source index · Storj.Uplink · source: cdn.winget.microsoft.com

overview

Package summary

Uplink CLI for the Storj network

Commands and aliases

  • uplink

history

Project history and usage

Storj Uplink CLI is the command-line client for Storj object storage. It gives package-manager users a native `uplink` binary for setting up access, managing buckets, and copying or sharing objects on the Storj network.

Project history

The Storj repository describes Storj v3 as a distributed cloud storage network and S3-compatible platform whose files are encrypted, split into pieces, and stored across a distributed network. The Uplink CLI docs present `uplink` as the command-line application for accessing Object Storage.

Adoption history

The official docs organize Uplink as a full CLI API with install, setup, access, import, copy, list, bucket, metadata, move, remove, and share commands. The supplied package metadata shows Homebrew, Nix, and Windows winget packaging, reflecting the need for a cross-platform storage client.

How it is used

`uplink setup` creates a config file, imports an API key or access grant, records the satellite address, and asks for an encryption passphrase. The command set then covers bucket creation, object upload/download, listing, metadata, removal, and restricted sharing.

Why package nerds care

Storj Uplink is significant because decentralized object storage still needs boring packageable client tooling. Package users care about it as the reproducible, scriptable bridge between shell workflows and Storj's access-grant and client-side-encryption model.

Timeline

  • 2019: Storj wiki history shows Uplink CLI documentation updates during v3-era development.
  • Current: Storj docs publish Uplink CLI as the native CLI tool for Storj Object Storage.
  • 2026: GitHub repository page shows ongoing Storj v3 development and hundreds of releases.

Related projects

  • The Storj repository links the Uplink library and S3 Gateway documentation as adjacent developer and compatibility surfaces. The CLI docs also connect Uplink access grants with bucket and object commands.

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for storj-uplink. Nucleus package metadata is still published here so future coverage has a stable package URL.

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 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.

Credential files

Credential-bearing paths to review before unattended agent runs.

Linux
~/.config/storj/uplink/access.json

executables

Installed executables

CommandKindExposureNote
uplinkcliglobal 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 version1.158.3
manager updated2026-07-07
local dataok
upstreamcurrent
latest detectedv1.158.3

https://github.com/storj/storj

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:storj-uplink
Version1.158.3
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/storj-uplink
Homepagehttps://storj.io
Repositoryhttps://github.com/storj/storj
Upstream docshttps://storj.dev/dcs/api/uplink-cli
LicenseAGPL-3.0-only
Source archivehttps://github.com/storj/storj/archive/refs/tags/v1.158.3.tar.gz
Last updated2026-07-07T12:42:35Z
Pulseupdated
Build 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 Namestorj-uplink
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • 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%

storj-uplink

nix profile install nixpkgs#storj-uplink
  • normalized package name match
  • Matched by: Storj Uplink
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/st/storj-uplink/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
winget95%

Storj.Uplink

winget install --id Storj.Uplink -e
  • normalized package name match
  • Matched by: Storj Uplink
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: Storj.Uplink from https://cdn.winget.microsoft.com/cache/source.msix

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