pkg.soopen package index

brew / Rang 5513

yorkie mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install yorkie

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Document store for collaborative applications

Befehle und Aliase

  • yorkie

Verlauf

Projektgeschichte und Nutzung

Yorkie is an open-source document store for real-time collaborative applications. Its niche is CRDT-backed application state: clients keep local replicas of JSON-like documents, edit offline, and synchronize through a Yorkie server backed by MongoDB or in-memory storage.

Projektgeschichte

The public Yorkie repository was created in October 2018 and presents the project as a Go server plus client SDK ecosystem for collaborative documents. The README describes the core architecture as Client, Document, and Server, with documents exchanged as changes and stored as snapshots/changes in the server-side store.

Yorkie evolved around the practical problems that appear once CRDTs move from papers into applications: offline editing, synchronization, conflict resolution, document watches, administration, and deployment. Its documentation now separates getting-started guides, SDK docs, CLI tooling, internals, and deployment material, which is a sign of a project aimed at application builders rather than only CRDT researchers.

Adoptionsgeschichte

Yorkie sits in the wave of collaboration infrastructure popularized by multiplayer editors, shared whiteboards, and local-first software. Its adoption story is smaller than Yjs or Automerge, but package managers matter here because a self-hostable server and CLI make CRDT collaboration something teams can run as infrastructure instead of embedding only a browser library.

The surrounding organization maintains related pieces such as a JavaScript SDK and dashboard, and the GitHub metadata in July 2026 showed active development with hundreds of stars and forks. That points to a modest but real community around self-hosted collaborative document infrastructure.

Wie es verwendet wird

Practically, Yorkie is used by developers who want to add shared state to an application: run or deploy the Yorkie server, connect clients through the Go, JavaScript, iOS, or Android SDKs, attach to documents, apply updates locally, and let Yorkie synchronize the CRDT changes.

The CLI is part of the package-manager story: it gives operators and developers a local command for interacting with Yorkie projects and documents while the server handles storage, synchronization, and conflict resolution.

Warum Paket-Nerds sich dafür interessieren

Yorkie is interesting because it packages CRDT collaboration as server infrastructure, not just as an npm library. For package nerds, it represents the move from single-user command-line tools to installable collaboration backends that still fit normal open-source distribution channels.

Zeitleiste

  • 2018-10-24: The public yorkie-team/yorkie GitHub repository is created.
  • 2020s: Yorkie develops around CRDT documents, SDKs, a CLI, server deployment, and administrative tooling.
  • 2026-07: GitHub metadata shows continuing activity and a small but established community around the project.

Related projects

  • Automerge and Yjs are adjacent CRDT/local-first collaboration libraries in the broader ecosystem.
  • yorkie-js-sdk is the JavaScript client SDK for browser and Node applications.
  • Yorkie Dashboard is the administrative companion for managing projects and documents.

Sicherheitslage

Risikostufe: orange

formula declares a Homebrew service.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • formula declares a Homebrew service

Signale

  • metadata:service

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Formelmetadaten deklarieren einen Service- oder Daemon-Block.
  • 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
yorkiecliglobales 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-08-04
Manager-Version0.7.13
Manager aktualisiert2026-07-25
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.7.13

https://github.com/yorkie-team/yorkie

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:yorkie
Version0.7.13
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/yorkie
Homepagehttps://yorkie.dev/
Repositoryhttps://github.com/yorkie-team/yorkie
Upstream-Dokumentationhttps://yorkie.dev/
LizenzApache-2.0
Quellarchivhttps://github.com/yorkie-team/yorkie/archive/refs/tags/v0.7.13.tar.gz
Zuletzt aktualisiert2026-07-25T21:32:49+02:00
Pulseupdated
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstdeclared

Registry-Fakten

Details aus der Quelldatenbank

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

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
  • cross-ecosystem install command graph
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment
  • pkg.so package database
  • pkgdb category and tag curation