Automic VaultAutomic Vault

brew

ccm mit Homebrew, MacPorts installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install ccm

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install ccm

MacPorts ports tree · databases/ccm/Portfile · Quelle: api.github.com

Überblick

Paketzusammenfassung

Create and destroy an Apache Cassandra cluster on localhost

Befehle und Aliase

  • ccm

Verlauf

Projektgeschichte und Nutzung

CCM, the Cassandra Cluster Manager, is a Python command-line tool for creating, launching, testing, and destroying local Apache Cassandra clusters. It matters in package-manager catalogs because it packages a repeatable local Cassandra lab into a single executable rather than leaving users to hand-wire several Cassandra nodes.

Projektgeschichte

The official Apache repository describes CCM as a script and library for creating, managing, and destroying a small Cassandra cluster on a local box for testing. The GitHub repository was created in 2011 and is now hosted under the Apache organization as apache/cassandra-ccm.

The install documentation notes that CCM predates the modern Python packaging defaults and then explains current Python 3, virtualenv, and editable-install workflows, which reflects the project's long life across Cassandra and Python eras.

Adoptionsgeschichte

The official install document points users to PyPI and Homebrew packages, so CCM has been distributed both as a Python package and as a Unix package-manager formula. The input package facts also list Homebrew and MacPorts package names.

Wie es verwendet wird

Typical usage creates a named Cassandra cluster for a given Cassandra release or source tree, populates it with local nodes, starts the nodes, inspects rings or logs, and later removes the cluster. By default, node data and configuration live under ~/.ccm/<cluster_name>/, while downloaded Cassandra releases are cached under ~/.ccm/repository/.

Warum Paket-Nerds sich dafür interessieren

CCM is a good example of a package-manager utility whose value is not a single algorithm but a reproducible local topology. It turns Cassandra cluster setup into a developer-facing CLI workflow and is especially useful for tests, demos, compatibility checks, and package maintainers who need disposable Cassandra environments.

Zeitleiste

  • 2011: Official GitHub repository created.
  • 2010s: README documents local multi-node Cassandra cluster creation and versioned Cassandra downloads.
  • 2020s: Install guide documents Python 3, virtualenv, Apple Silicon, and modern macOS caveats.

Related projects

  • Apache Cassandra is the database system CCM manages locally.
  • DataStax Enterprise and Hyper Converged Database are mentioned by the README as third-party cluster types supported through CCM extensions.

Sicherheitslage

Risikostufe: orange

infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • infrastructure mutation or orchestration signal

Signale

  • text:cluster

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 2 Laufzeitabhä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.

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.

Configuration files

Config paths the tool may read or write during local use.

Unix
~/.ccm/<cluster_name>/

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
ccmcliglobales 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-Version3.1.5
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/apache/cassandra-ccm

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:ccm
Version3.1.5
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/ccm
Homepagehttps://github.com/apache/cassandra-ccm
Repositoryhttps://github.com/apache/cassandra-ccm
Upstream-Dokumentationhttps://github.com/apache/cassandra-ccm#readme
LizenzApache-2.0
Quellarchivhttps://files.pythonhosted.org/packages/f1/12/091e82033d53b3802e1ead6b16045c5ecfb03374f8586a4ae4673a914c1a/ccm-3.1.5.tar.gz
Abhängigkeitenlibyaml, python@3.14
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 Nameccm
Version Scheme0
Revision5
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.

MacPorts95%

ccm

sudo port install ccm
  • normalized package name match
  • Abgeglichen nach: Ccm
MacPorts ports tree · api.github.com · MacPorts ports tree: databases/ccm/Portfile from https://api.github.com/repos/macports/macports-ports/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 configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment