Automic VaultAutomic Vault

brew

juicefs mit Homebrew, Nix, scoop installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für juicefs in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install juicefs

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#juicefs

nixpkgs package indexes · pkgs/by-name/ju/juicefs/package.nix · Quelle: api.github.com

Windows

Scoopverifiziert · 92%
scoop install main/juicefs

Scoop official bucket manifest trees · bucket/juicefs.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

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

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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.

Sicherheitslage

Risikostufe: orange

infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • infrastructure mutation or orchestration signal

Signale

  • text:cloud

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
juicefscliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-08
Manager-Version1.4.0
Manager aktualisiert2026-07-06
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.4.0

https://github.com/juicedata/juicefs

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:juicefs
Version1.4.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/juicefs
Homepagehttps://juicefs.com
Repositoryhttps://github.com/juicedata/juicefs
Upstream-Dokumentationhttps://juicefs.com/docs/community
LizenzApache-2.0
Quellarchivhttps://github.com/juicedata/juicefs/archive/refs/tags/v1.4.0.tar.gz
Zuletzt aktualisiert2026-07-06T10:07:59Z
Pulseupdated
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

juicefs

nix profile install nixpkgs#juicefs
  • normalized package name match
  • Abgeglichen nach: Juicefs
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ju/juicefs/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Scoop95%

main/juicefs

scoop install main/juicefs
  • normalized package name match
  • Abgeglichen nach: Juicefs
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/juicefs.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

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