pkg.soopen package index

cask

neo4j-desktop mit Homebrew Cask installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrew Caskverifiziert · 100%
brew install --cask neo4j-desktop

local Homebrew cask metadata

Überblick

Paketzusammenfassung

Developer IDE or Management Environment for Neo4j instances

Befehle und Aliase

In der lokalen Paketdatenbank wurden keine Executable-Aliase gefunden.

Verlauf

Projektgeschichte und Nutzung

Neo4j Desktop is Neo4j's graphical local development and management environment for creating DBMS instances, managing graph databases, running Cypher, importing data, visualizing graphs, and connecting to remote Neo4j services.

Projektgeschichte

Neo4j Desktop began as a desktop packaging of the Neo4j graph platform with a bundled JVM, Developer Edition database, and graph applications. The official project repository describes it as a client containing everything needed to start working with Neo4j.

Desktop 2.x is described by Neo4j as an evolution of the original Desktop, with a redesigned and more unified experience that mirrors the Neo4j Aura console. It consolidated local instance management with Import, Query, Bloom, and Dashboards in Desktop Studio.

Adoptionsgeschichte

Neo4j Desktop packages a local developer environment around Neo4j rather than requiring users to assemble a database server, JVM, query UI, import tooling, and visualization tools separately. It supports macOS, Windows, and Linux and can manage local databases while also connecting to remote Neo4j and Aura instances.

Desktop includes a Developer edition license for local single-user use and supports installing plugins through its interface, making it a common entry point for graph application development and Cypher experimentation.

Wie es verwendet wird

Developers create projects and local DBMS instances, select a Neo4j version, start or stop instances, edit each instance's `neo4j.conf`, install plugins, import data, and query or visualize graphs from the bundled Studio tools.

The official UI exposes each local instance's folder, log, configuration file, data path, connection URI, security controls, backup actions, and upgrade workflow.

Warum Paket-Nerds sich dafür interessieren

Neo4j Desktop is the batteries-included desktop distribution in the Neo4j ecosystem. Package users care about it because the application manages multiple DBMS versions and instance directories while bundling import, query, Bloom visualization, and dashboard tools.

It differs from the standalone Neo4j server package: Desktop prioritizes an interactive local workspace and lifecycle management, whereas the server and Cypher Shell packages better suit services, scripts, and headless environments.

Zeitleiste

  • The original Neo4j Desktop combined a local Neo4j developer installation with bundled graph applications.
  • Desktop 2.x introduced a redesigned workspace aligned with the Aura console and unified Import, Query, Bloom, and Dashboards as Desktop Studio.
  • Desktop 2.x added migration support for cloning compatible instances from Desktop 1.x.

Related projects

  • Neo4j DBMS is the graph database managed locally by Desktop.
  • Neo4j Aura supplies managed remote Neo4j instances that Desktop can connect to.
  • Cypher Shell provides a command-line path for running queries and administrative commands.
  • APOC plugins can be installed into compatible local instances from Desktop.

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für neo4j-desktop wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

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
<Neo4j Desktop instance folder>/conf/neo4j.conf
Windows
<Neo4j Desktop instance folder>\conf\neo4j.conf

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
Es waren keine Executable-Daten vorhanden.

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-11-04
Manager-Version2.3.1
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://neo4j.com/download/

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz
  • InfoRelease/tag comparison is only available for GitHub repositories.https://neo4j.com/download/none Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselcask:neo4j-desktop
Version2.3.1
PaketmanagerHomebrew Cask
Paketmanager-Seitehttps://formulae.brew.sh/cask/neo4j-desktop
Homepagehttps://neo4j.com/download/
Upstream-Dokumentationhttps://neo4j.com/download/
Quellarchivhttps://dist.neo4j.org/neo4j-desktop-2/mac/neo4j-desktop-2.3.1-universal.dmg
SHA-256045005b2c6d651ecfae6deabfffb807873933a9b484c8c478ae9f7c95c1214f0
Bottlenicht erfasst
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew cask API
Taphomebrew/cask
Full Tokenneo4j-desktop
Names
  • Neo4j Desktop
Old Tokens
  • neo4j
Depends On
Artifacts
Deprecatedno
Disabledno

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

  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment