Automic VaultAutomic Vault

brew

djl-serving mit Homebrew installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install djl-serving

local Homebrew formula metadata

Überblick

Paketzusammenfassung

This module contains an universal model serving implementation

Befehle und Aliase

  • djl-serving

Verlauf

Projektgeschichte und Nutzung

DJL Serving is the model-serving component of the Deep Java Library ecosystem. It packages deep-learning inference behind HTTP endpoints, with support for multiple engines, model stores, dynamic batching, worker scaling, plugins, and REST management APIs.

Projektgeschichte

The official GitHub repository was created in August 2021 and describes DJL Serving as a universal, scalable machine-learning model deployment solution. The README says it serves PyTorch TorchScript, TensorFlow SavedModel, ONNX CPU models, Python script models, and extension-backed model types such as XGBoost, LightGBM, SentencePiece, and fastText or BlazingText.

The project is tied to the larger DJL documentation set rather than only a standalone README. Official docs describe global, engine, workflow, model, and application configuration layers, while LMI documentation explains `serving.properties` and environment-variable configuration for large-model inference containers.

Adoptionsgeschichte

DJL Serving adoption follows Java and AWS-centered inference workflows more than general desktop CLI culture. The official README includes Homebrew installation and service commands for macOS, Debian package installation for Ubuntu, Windows zip startup, and Docker images, making it approachable both as a local package and as a containerized service.

The release history shows regular model-serving maintenance across the 2020s, including v0.23-era releases in 2023, v0.29.0 in 2024, and v0.36.0 in 2026. That cadence tracks the changing model-serving world: new inference backends, LMI configuration, and operations APIs matter as much as the command itself.

Wie es verwendet wird

Users start `djl-serving` from the command line or as a Homebrew service, point it at models or workflows, and interact with inference and management endpoints. Configuration commonly lives in a `serving.properties` file, while LMI container deployments use `/opt/ml/model` as the default model-artifact location.

Warum Paket-Nerds sich dafür interessieren

For package-history purposes, DJL Serving is interesting because it is both a Unix-installable daemon and a cloud/container serving stack. It puts JVM-based ML serving into Homebrew next to small CLI tools, but its real operational shape includes Docker, REST APIs, model stores, and SageMaker-style large-model inference configuration.

Zeitleiste

  • 2021-08-16: Official GitHub repository created.
  • 2023-06-14: v0.23.0-alpha release published.
  • 2024-08-16: v0.29.0 release published.
  • 2026-03-12: v0.36.0 release published.

Related projects

  • Related serving systems include TorchServe, TensorFlow Serving, NVIDIA Triton Inference Server, KServe, and the broader Deep Java Library project that supplies engines and model APIs underneath DJL Serving.

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 1 Plattformziele verfügbar.
  • Installiert mit 1 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
/opt/ml/model/serving.propertiesserving.properties

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
djl-servingcliglobales 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-25
Manager-Version0.36.0
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/deepjavalibrary/djl-serving

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:djl-serving
Version0.36.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/djl-serving
Homepagehttps://github.com/deepjavalibrary/djl-serving
Repositoryhttps://github.com/deepjavalibrary/djl-serving
Upstream-Dokumentationhttps://docs.djl.ai/master/docs/serving/serving/docs/configurations.html
LizenzApache-2.0
Quellarchivhttps://publish.djl.ai/djl-serving/serving-0.36.0.tar
Abhängigkeitenopenjdk
Bottleverfügbar (auf all)
Homebrew post-installnicht definiert
Dienstdeclared

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namedjl-serving
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • 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
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment