Automic VaultAutomic Vault

brew

asciidoctorj mit Homebrew, chocolatey, MacPorts, Nix, scoop installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install asciidoctorj

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install asciidoctorj

MacPorts ports tree · textproc/asciidoctorj/Portfile · Quelle: api.github.com

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#asciidoctorj

nixpkgs package indexes · pkgs/by-name/as/asciidoctorj/package.nix · Quelle: api.github.com

Windows

Chocolateyverifiziert · 92%
choco install asciidoctorj

Chocolatey community package catalog · asciidoctorj · Quelle: community.chocolatey.org

Scoopverifiziert · 92%
scoop install main/asciidoctorj

Scoop official bucket manifest trees · bucket/asciidoctorj.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Java wrapper and bindings for Asciidoctor

Befehle und Aliase

  • asciidoctorj

Verlauf

Projektgeschichte und Nutzung

AsciidoctorJ is the official JVM integration for Asciidoctor, letting Java and other JVM programs run Asciidoctor and inspect parsed AsciiDoc documents. For package users it is both a command-line converter and a Maven Central artifact family, making AsciiDoc processing available in Java build systems without requiring a separate Ruby toolchain.

Projektgeschichte

The project sits inside the Asciidoctor ecosystem as the Java binding layer for the Ruby Asciidoctor processor. Its official README describes AsciidoctorJ as the official library for running Asciidoctor on the JVM and credits Alex Soto, Dan Allen, and Robert Panzer as maintainers/authors on the README header.

AsciidoctorJ's early public release line was already formalized by 2014: the repository has an annotated `asciidoctorj-1.5.0` tag dated 2014-08-17, and the README notes that the Maven artifactId changed to `asciidoctorj` starting in 1.5.0. The project later kept a long 2.x series and published 3.0.0 in 2024, continuing the JVM-facing role while the wider Asciidoctor documentation moved to docs.asciidoctor.org.

Adoptionsgeschichte

AsciidoctorJ's adoption path is centered on Java build tooling. The README documents Maven, Gradle, SBT, and Leiningen dependency examples and says the artifacts are published to Maven Central, which made it useful for documentation pipelines embedded in JVM projects.

Package-manager adoption followed the same developer-tool pattern: the input package facts list Homebrew, Chocolatey, MacPorts, Nix, and Scoop packages. That spread matters because AsciidoctorJ is often installed as a CLI by documentation authors even when the underlying attraction is JVM integration.

Wie es verwendet wird

The CLI use case is converting AsciiDoc files from the shell, for example running `asciidoctorj -b pdf README.adoc`. The library use case is declaring `org.asciidoctor:asciidoctorj` in a JVM build and invoking Asciidoctor conversion or AST inspection from Java or another JVM language.

Warum Paket-Nerds sich dafür interessieren

AsciidoctorJ is interesting to package nerds because it packages a Ruby-origin documentation processor for the JVM world. It bridges language ecosystems: Ruby Asciidoctor behavior, Java dependency management, build plugins, and a cross-platform command-line distribution all meet in one package.

Zeitleiste

  • 2013: GitHub repository created for Java bindings for Asciidoctor.
  • 2014: `asciidoctorj-1.5.0` annotated tag published; README notes the artifactId changed to `asciidoctorj` in 1.5.0.
  • 2021: 2.5.0 release published.
  • 2024: 3.0.0 release published.

Related projects

  • Asciidoctor is the upstream AsciiDoc processor that AsciidoctorJ runs on the JVM.
  • Asciidoctor Maven and Gradle integrations are documented as build-system paths for using AsciidoctorJ.

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 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.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
asciidoctorjcliglobales 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.0.1
Manager aktualisiert2026-06-22
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/asciidoctor/asciidoctorj

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:asciidoctorj
Version3.0.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/asciidoctorj
Homepagehttps://github.com/asciidoctor/asciidoctorj
Repositoryhttps://github.com/asciidoctor/asciidoctorj
Upstream-Dokumentationhttps://docs.asciidoctor.org/asciidoctorj/latest
LizenzApache-2.0
Quellarchivhttps://search.maven.org/remotecontent?filepath=org/asciidoctor/asciidoctorj/3.0.1/asciidoctorj-3.0.1-bin.zip
Zuletzt aktualisiert2026-06-22T14:02:46-07:00
Pulseupdated
Abhängigkeitenopenjdk
Bottleverfügbar (auf all)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

asciidoctorj

nix profile install nixpkgs#asciidoctorj
  • normalized package name match
  • Abgeglichen nach: Asciidoctorj
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/as/asciidoctorj/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
MacPorts95%

asciidoctorj

sudo port install asciidoctorj
  • normalized package name match
  • Abgeglichen nach: Asciidoctorj
MacPorts ports tree · api.github.com · MacPorts ports tree: textproc/asciidoctorj/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
Chocolatey95%

asciidoctorj

choco install asciidoctorj
  • normalized package name match
  • Abgeglichen nach: Asciidoctorj
Chocolatey community package catalog · community.chocolatey.org · Chocolatey community package catalog: asciidoctorj from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','ansicon'
Scoop95%

main/asciidoctorj

scoop install main/asciidoctorj
  • normalized package name match
  • Abgeglichen nach: Asciidoctorj
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/asciidoctorj.json from https://api.github.com/repos/ScoopInstaller/Main/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 package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment