Automic VaultAutomic Vault

brew

Install marmite with Homebrew, Nix

Static Site Generator for Blogs using Markdown. Version 0.4.0 via Homebrew; verified 2026-07-06.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install marmite

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#marmite

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

overview

Package summary

Static Site Generator for Blogs using Markdown

Commands and aliases

  • marmite

history

Project history and usage

Marmite is a Rust static-site generator for blogs built around the idea that Markdown files plus one command should be enough to publish a site.

Project history

The Marmite repository was created on 2024-10-14. The README expands the name as 'Markdown makes sites' and describes the project as a very simple static-site generator for bloggers.

Its official documentation and example content emphasize low setup: a directory of Markdown and media files can become a blog without adopting a rigid folder structure. The CLI defaults to marmite.yaml for configuration and accepts --config for an alternate file.

Adoption history

Marmite is younger than the long-running Markdown tools in this batch, but it gathered visible early interest: by 2026-07-01 GitHub metadata showed 856 stars and 51 forks. The supplied package-manager facts list Homebrew and Nix packages, and the README documents Homebrew and Cargo installation paths.

Release notes through 2025 and 2026 show the project moving from early static-site basics into feeds, themes, IndieWeb/microformats, search, series, shortcodes, and other blog-focused features while keeping a simple CLI entry point.

How it is used

The core command is marmite INPUT_FOLDER OUTPUT_FOLDER. Users point Marmite at a folder of Markdown files and media, optionally provide marmite.yaml or --config, and generate a static output directory that can be served by any static host.

Package maintainers care about Marmite because it is a single Rust CLI in the crowded static-site-generator category, aiming for low-friction blogging rather than a large framework or JavaScript build pipeline.

Why package nerds care

Marmite's packaging story is simple and attractive: a compiled CLI, Homebrew/Nix availability, and Cargo installation. That is exactly the kind of static-site tool package managers like because it gives users a self-contained generator with few runtime surprises.

Timeline

  • 2024: GitHub repository created.
  • 2025: 0.2.x releases expanded blog, theme, feed, and publishing features.
  • 2026: 0.3.x releases continued with binary assets and documentation updates.

Related projects

  • Marmite belongs to the static-site-generator family alongside Hugo, Zola, Jekyll, and other Markdown-to-site tools.
  • It uses CommonMark/GitHub Flavored Markdown style input and focuses on blog publishing workflows.

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 6 platform targets.
  • Build metadata lists 1 build 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
marmite.yamlfile supplied with --config

executables

Installed executables

CommandKindExposureNote
marmitecliglobal 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-08
manager version0.4.0
manager updated2026-07-06
local dataok
upstreamcurrent
latest detected0.4.0

https://github.com/rochacbruno/marmite

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:marmite
Version0.4.0
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/marmite
Homepagehttps://rochacbruno.github.io/marmite/
Repositoryhttps://github.com/rochacbruno/marmite
Upstream docshttps://github.com/rochacbruno/marmite#readme
LicenseAGPL-3.0-or-later
Source archivehttps://github.com/rochacbruno/marmite/archive/refs/tags/0.4.0.tar.gz
Last updated2026-07-06T16:12:32Z
Pulseupdated
Build dependenciesrust
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namemarmite
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • 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%

marmite

nix profile install nixpkgs#marmite
  • normalized package name match
  • Matched by: Marmite
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/ma/marmite/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