pkg.soopen package index

brew / Rang 7473

jvm-mon mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install jvm-mon

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Console-based JVM monitoring

Befehle und Aliase

  • jvm-mon

Verlauf

Projektgeschichte und Nutzung

jvm-mon is a console-based JVM monitoring tool for inspecting Java processes from a terminal. Its README describes the target use case plainly: SSH into a server and see what is happening inside running JVM applications.

Projektgeschichte

The jvm-mon repository was created on 2017-02-06 and published release 0.1 the same day. Early releases were aimed at a terminal UI for JVM process monitoring, showing running processes, CPU and garbage-collection load, heap usage, and top threads.

The 1.3 release, published on 2025-03-28, marked a substantial implementation change: the README says the tool was rewritten in Go, distributed as a single executable, able to monitor Java 8 and above, and no longer required an existing JDK. The bundled agent jar attaches to a selected JVM and communicates metrics back over a socket.

Adoptionsgeschichte

jvm-mon has a niche but clear adoption profile: terminal-first Java operations. The input package metadata lists Homebrew packaging, and the repository metadata showed about 1,500 GitHub stars on 2026-07-01, which is notable for a focused JVM terminal monitor.

Its adoption sits beside older JVM tools such as JConsole, VisualVM, `jstat`, and `jcmd`, but jvm-mon's package-manager appeal is the single CLI for quick remote inspection.

Wie es verwendet wird

Users launch `jvm-mon`, select a running JVM process, and press Enter to monitor it. The README documents keys for quitting and killing a process, and lists CPU, GC, heap, and thread information as available metrics.

The 1.3 architecture bundles a Java agent jar inside the executable, extracts it at startup, attaches it to the selected JVM, and exchanges metric data through a socket connection.

Warum Paket-Nerds sich dafür interessieren

jvm-mon is package-nerd interesting because it turns a normally GUI-heavy or JDK-tool-heavy monitoring task into a Homebrew-installable terminal binary.

The Go rewrite matters operationally: fewer runtime assumptions and no required local JDK make the package easier to ship onto servers where operators want a quick inspection tool rather than a monitoring platform.

Zeitleiste

  • 2017-02-06: The jvm-mon GitHub repository is created and release 0.1 is published.
  • 2017-03-27: jvm-mon 0.3 is published.
  • 2020-04-29: jvm-mon 1.0-ea1 is published.
  • 2025-03-20: jvm-mon 1.1 is published.
  • 2025-03-28: jvm-mon 1.3 is published with the Go rewrite documented in the README.

Related projects

  • JConsole and VisualVM are GUI-oriented JVM monitoring tools in the broader Java ecosystem.
  • `jstat` and `jcmd` are command-line JDK tools for JVM inspection.
  • Java agents and the JVM attach mechanism are the underlying technique jvm-mon uses to collect metrics.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 8 Plattformziele verfügbar.
  • Build-Metadaten listen 2 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
jvm-moncliglobales 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-Version1.3
Manager aktualisiert2026-07-25
lokale DatenOK
Upstreamaktuell
neueste erkannte Version1.3

https://github.com/ajermakovics/jvm-mon

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:jvm-mon
Version1.3
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/jvm-mon
Homepagehttps://ajermakovics.github.io/jvm-mon/
Repositoryhttps://github.com/ajermakovics/jvm-mon
Upstream-Dokumentationhttps://ajermakovics.github.io/jvm-mon/
LizenzApache-2.0
Quellarchivhttps://github.com/ajermakovics/jvm-mon/archive/refs/tags/1.3.tar.gz
Zuletzt aktualisiert2026-07-25T20:58:06-04:00
Pulseupdated
Build-Abhängigkeitengo, openjdk
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namejvm-mon
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