Automic VaultAutomic Vault

brew

Install jbake with Homebrew, Nix

Java based static site/blog generator. Version 2.7.0 via Homebrew; verified 2026-06-22.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install jbake

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#jbake

nixpkgs package indexes · pkgs/by-name/jb/jbake/package.nix · source: api.github.com

overview

Package summary

Java based static site/blog generator

Commands and aliases

  • jbake

history

Project history and usage

JBake is a Java-based open-source static site and blog generator aimed at developers and designers. It converts plain content, templates, assets, and metadata into a static website that can be hosted without a server-side CMS.

Project history

The JBake site identifies the JBake Team beginning in 2012, and the project team page lists Jonathan Bullock as founder and developer. The repository README presents JBake as a Java static site/blog generator, and the documentation records its Gradle, Maven, mill, sbt, and SBuild integrations.

The project adopted Semantic Versioning from v2.2.0 onward, according to its README. Later releases and documentation show the project moving through Java runtime requirements, Gradle-based builds, plugin integrations, and template/content support for common JVM publishing workflows.

Adoption history

JBake occupies the JVM side of the static-site-generator ecosystem, with package metadata in the input showing Homebrew and Nix distribution and the official site listing sites built with JBake. Its adoption is narrower than Jekyll or Hugo, but useful for Java teams that want static publishing while keeping content generation inside familiar JVM tooling.

How it is used

A typical JBake project contains content, templates, assets, and a jbake.properties file; users run the jbake command or a build-tool plugin to generate HTML. The documentation describes Maven and Gradle integrations, watch/server-style workflows, Markdown, AsciiDoc, HTML content, metadata headers, and templating through engines such as Freemarker, Groovy, and Thymeleaf.

Why package nerds care

JBake is package-nerd interesting because it is a static site generator that lives in Java packaging culture rather than the Ruby, Go, or JavaScript ecosystems. It bridges CLI packaging, Maven artifacts, Gradle plugins, and content tooling in a way that makes sense for JVM shops and documentation sites.

Timeline

  • 2012: JBake Team copyright period begins on the official site.
  • 2013: Official documentation pages show early JBake manual authorship and project structure docs.
  • v2.2.0: JBake adopts Semantic Versioning.
  • 2016: JBake 2.6.0 release notes describe a move to a Gradle build and a Java 7 runtime requirement.
  • 2021: JBake 2.7.0 release-candidate news documents continued Maven plugin and release work.

Related projects

  • JBake is related to Jekyll-style static site generation, Markdown, AsciiDoc, Freemarker, Groovy templates, Thymeleaf, Maven, Gradle, sbt, mill, SBuild, GitHub Pages-style hosting, and other static publishing tools.

security posture

Risk level: green

narrow executable package without higher-risk signals.

Risk classifier

green risk · low confidence · appliance

Why

  • narrow executable package without higher-risk signals

Signals

  • metadata:no-higher-risk-signals

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 1 platform targets.
  • Installs with 1 runtime dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

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
jbake.propertiescustom.properties

executables

Installed executables

CommandKindExposureNote
jbakecliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-07
manager version2.7.0
manager updated2026-06-22
local dataok
upstreamnot checked
latest detectednot detected

https://github.com/jbake-org/jbake

install metadata

Package metadata

Package keybrew:jbake
Version2.7.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/jbake
Homepagehttps://jbake.org/
Repositoryhttps://github.com/jbake-org/jbake
Upstream docshttps://jbake.org/docs
LicenseMIT
Source archivehttps://github.com/jbake-org/jbake/releases/download/v2.7.0/jbake-2.7.0-bin.zip
Last updated2026-06-22T14:03:48-07:00
Pulseupdated
Dependenciesopenjdk
Bottleavailable (on all)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

jbake

nix profile install nixpkgs#jbake
  • normalized package name match
  • Matched by: Jbake
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/jb/jbake/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • 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