pkg.sopackage field notes

brew / rank 5359

Install juicefs with Homebrew

Cloud-based, distributed POSIX file system built on top of Redis and S3. Version 1.4.1 via Homebrew; verified 2026-07-31.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install juicefs

provider-native install command

overview

Package summary

Cloud-based, distributed POSIX file system built on top of Redis and S3

Commands and aliases

  • juicefs

history

Project history and usage

JuiceFS is a cloud-native distributed POSIX file system that separates file data from metadata: file data lives in object storage and metadata lives in a database or key-value engine. That split made it attractive for Kubernetes, machine-learning, big-data, and cloud migration workloads that need a familiar filesystem interface over elastic storage.

Project history

JuiceFS project materials describe the system as started in 2017 and designed for unstructured data management across multi-cloud, cross-cloud, and hybrid-cloud environments. Its open-source Community Edition is released under Apache-2.0, and official architecture documentation explains the object-storage plus metadata-engine design.

Adoption history

The project moved from an early open-source release line in 2021 to a 1.0.0 release published on August 9, 2022. Packaging in Homebrew, Nix, and Scoop made the single `juicefs` CLI easy to install across developer laptops and automation environments.

How it is used

Users format a JuiceFS volume against a metadata engine, mount it through the CLI, and back file data with S3-compatible or other object storage. In package-manager terms, it is a heavyweight CLI because the same binary is both an administration tool and the client that mounts the filesystem.

Why package nerds care

JuiceFS is significant because it packages a distributed storage client as a normal CLI while depending on external services for durability and metadata. It sits at the intersection of FUSE filesystems, cloud object stores, Kubernetes CSI drivers, and database-backed metadata.

Timeline

  • 2017: JuiceFS project materials describe the project as having started in this year.
  • 2021: Public GitHub releases show the 0.x open-source release line.
  • 2022: JuiceFS 1.0.0 was published on August 9.
  • 2023: v1.1 documentation introduced directory statistics and directory quota behavior.

Related projects

  • Kubernetes CSI drivers are a major deployment surface for JuiceFS.
  • Redis, TiKV, MySQL, PostgreSQL, and SQLite are documented metadata-engine options.
  • Amazon S3 and S3-compatible object stores are common backing stores.

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:cloud

Install behavior

  • No Homebrew bottle metadata was recorded.

Recommended review

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

executables

Installed executables

CommandKindExposureNote
juicefsexecutableindexed executableDiscovered from the local executable index.

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-08-03
manager version1.4.1
manager updated2026-07-31
local dataunknown
upstreamnot available
latest detectednot detected
  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:juicefs
Version1.4.1
Package managerHomebrew
Homepagehttps://juicefs.com
Repositoryhttps://github.com/juicedata/juicefs
Last updated2026-07-31T05:31:51Z
Pulseupdated
Bottlenot recorded
Servicenone declared

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
  • curated package history
  • pkgdb category and tag curation