# genuinetools/bane

Custom & better AppArmor profile generator for Docker containers.

Repository: https://github.com/genuinetools/bane
Canonical: https://ross.abutalabs.com/products/bane
Language: Go
License: MIT
License Family: permissive
Topics: docker, apparmor-profile, apparmor, containers, linux, cli, security, opencontainers
Last push: 2020-09-17T20:10:45+00:00

## Health v2 (maintenance only)
Score: 23/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 8, longevity 100
- inputs: {"age_days": 3982, "days_push": 2176, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 1230, forks 90 (observed 2026-08-28T04:04:03.830926+00:00)

## What it is
bane is a Go command-line tool that generates custom AppArmor security profiles for Docker containers from a declarative TOML config file. It replaces hand-written AppArmor rules with generated, least-privilege profiles that can be installed and attached to containerized services.

## Use cases
- generate an apparmor profile for a docker container
- confine a containerized nginx with apparmor without writing rules by hand
- harden docker containers with mandatory access control on linux
- create least-privilege file access rules for containerized services
- apparmor profile generator for oci containers
- manage container apparmor profiles from a toml config

## When to choose
- You run Docker on an AppArmor-enabled Linux host such as Ubuntu or Debian and want a tailored profile per container
- You want profiles generated from a declarative config file instead of hand-editing /etc/apparmor.d rules
- You prefer a small single-binary Go CLI you can drop into provisioning scripts or CI

## When to avoid
- Your host enforces SELinux or another MAC system instead of AppArmor
- You need actively maintained tooling - the last release was September 2020
- You primarily run containers on macOS or Windows, where AppArmor does not exist
- You need Kubernetes-native or Podman-focused security policy tooling rather than Docker-centric profiles

## Facets
- artifact type: cli-tool
- maturity: abandoned
- function: security, developer-tools, cli
- domain: security, operating-systems
- platform: cli, go
- tags: apparmor, apparmor-profile-generator, docker-security, mandatory-access-control, container-hardening, opencontainers, genuinetools, toml-config, containers, devops, command-line, linux, docker

## Member repositories
- genuinetools/bane (main) score 23

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:04:03.830926+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T06:15:01.388528+00:00, confidence not recorded.
  - readme: https://github.com/genuinetools/bane (fetched 2026-08-28T04:04:03.830926+00:00, sha e4b9491646d6)
- Data as of 2026-08-30T08:39:29.467469+00:00.