Ross ROSS = Recommend OSS · open-source software intelligence for agents

zboxfs/zbox

Zero-details, privacy-focused in-app file system. observed · 2026-08-28

github.com/zboxfs/zbox · homepage · Rust · Apache-2.0 (permissive) · archived observed · 2026-08-28

Health v2 · maintenance only

10/100

  • Activity 0
  • Release rhythm 8
  • Longevity 100

Flags: archived

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 3200
  • days_rel: n/a
  • days_push: 1047
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

1543 stars · 85 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

ZboxFS is a zero-details, privacy-focused embedded file system written in Rust that encrypts everything, including metadata and directory structure, using libsodium-backed AEAD cryptography. It runs in the application's memory space, supports multiple storage backends (memory, OS filesystem, RDBMS, key-value object stores), and offers deduplication, compression, versioning, and ACID transactions.

Use cases

  • store app files encrypted so no metadata leaks to the storage layer
  • embed a private file system inside a Rust, Node.js, or browser application
  • encrypt files client-side before uploading to cloud storage
  • build privacy-first apps in fintech or healthcare that need confidential file storage
  • add versioned, transactional encrypted storage to a desktop or mobile app
  • prevent traffic analysis by packing files into uniform same-sized blocks

When to choose

  • your application needs an embedded, single-process encrypted file system rather than a shared OS-level one
  • you must hide not only file contents but also names, sizes, and directory structure from the storage backend
  • you want modern AEAD crypto (AES-256-GCM, XChaCha20-Poly1305, Argon2) without implementing it yourself
  • you need the same encrypted storage API across Rust, Node.js, and the browser (WASM)

When to avoid

  • multiple processes need concurrent shared access to the same file system
  • you need a battle-tested, production-hardened solution - the project warns it is still under development and disclaims data loss
  • you only need full-disk or OS-level encryption like LUKS or VeraCrypt
  • you need POSIX-compliant file system semantics or mounting as a real volume

Facets

library · maturity maintenance

file-system cryptography compression security privacy security files developer-tools cross-platform rust cross-platform windows wasm browser encrypted-filesystem in-app-filesystem libsodium zero-knowledge client-side-encryption deduplication copy-on-write acid-transactions storage linux macos nodejs

4 sources

Member repositories

RepositoryRoleHealth v2
zboxfs/zboxmain10

For agents

markdown · JSON · MCP: product_card(name="zboxfs/zbox")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem