Automic VaultAutomic Vault

brew

checkmake mit Homebrew, dnf, MacPorts, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install checkmake

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install checkmake

MacPorts ports tree · devel/checkmake/Portfile · Quelle: api.github.com

Linux

Fedora dnfverifiziert · 92%
sudo dnf install checkmake

Fedora Rawhide package metadata · checkmake · Quelle: dl.fedoraproject.org

Nixverifiziert · 92%
nix profile install nixpkgs#checkmake

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

Überblick

Paketzusammenfassung

Linter/analyzer for Makefiles

Befehle und Aliase

  • checkmake

Verlauf

Projektgeschichte und Nutzung

checkmake is a Go command-line linter for Makefiles. It is a small but package-relevant tool because Makefiles are ubiquitous, and checkmake gives them the kind of static analysis that shell scripts, YAML, and source code often already receive.

Projektgeschichte

The checkmake/checkmake repository was created in August 2016 and describes the project as a linter and analyzer for Makefiles. The README says it scans one or more Makefiles for potential issues according to configurable rules.

The project was inspired by an idea from Dan Buch, according to the README, and later moved into the checkmake GitHub organization while retaining older badge references to the original mrtazz/checkmake namespace.

Adoptionsgeschichte

The official README documents installation with Go, prebuilt releases, packages, packagecloud, Homebrew-style package-manager use through batch metadata, and official container images on quay.io. It also provides pre-commit hook configuration for repository-level adoption.

The README notes that checkmake is natively embedded in MegaLinter, which makes it available inside a broader multi-language linting workflow even when users do not install it directly.

Wie es verwendet wird

Typical usage is to run checkmake against Makefile, GNUmakefile, or *.mk inputs and receive text or JSON reports. The CLI supports a default checkmake.ini configuration file, listing rules, and custom output templates.

In CI and pre-commit workflows, checkmake is used to catch missing phony declarations and similar Makefile maintainability issues before they are merged.

Warum Paket-Nerds sich dafür interessieren

checkmake is package-nerd interesting because it lints one of the oldest build-description formats still found in modern repositories. It is also a tidy example of a Go CLI distributed through source install, binary releases, containers, packagecloud, Homebrew, MacPorts, Nix, and distro packages.

Its presence in pre-commit and MegaLinter shows the common path from standalone command to plumbing inside larger developer-tool aggregators.

Zeitleiste

  • 2016: checkmake/checkmake repository created.
  • 2022: 0.2.1 release published on GitHub.
  • 2023: 0.2.2 release used in the official pre-commit example.
  • 2026: v0.3.x releases published, showing renewed maintenance.

Related projects

  • pre-commit is an adjacent integration surface documented by the project.
  • MegaLinter embeds checkmake for Makefile linting, and GNU Make is the input format the tool analyzes.

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 6 Plattformziele verfügbar.
  • Build-Metadaten listen 2 Build-Abhä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
./checkmake.ini
Windows
.\checkmake.ini

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
checkmakecliglobales 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.3.2
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv0.3.2

https://github.com/checkmake/checkmake

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:checkmake
Version0.3.2
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/checkmake
Homepagehttps://github.com/checkmake/checkmake
Repositoryhttps://github.com/checkmake/checkmake
Upstream-Dokumentationhttps://github.com/checkmake/checkmake#readme
LizenzMIT
Quellarchivhttps://github.com/checkmake/checkmake/archive/refs/tags/v0.3.2.tar.gz
Build-Abhängigkeitengo, pandoc
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Nix95%

checkmake

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

checkmake 0.3.2-2.fc45

Linter/analyzer for Makefiles

https://github.com/checkmake/checkmake

sudo dnf install checkmake
  • License: Apache-2.0 AND BSD-3-Clause AND ISC AND MIT
  • Category: Unspecified
  • Architecture: x86_64
  • Source Package: checkmake
  • 3 Abhängigkeiten
  • 2 stellt bereit
  • normalized package name match
  • Abgeglichen nach: Checkmake
Fedora Rawhide package metadata · dl.fedoraproject.org · Fedora Rawhide package metadata: checkmake from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst
MacPorts95%

checkmake

sudo port install checkmake
  • normalized package name match
  • Abgeglichen nach: Checkmake
MacPorts ports tree · api.github.com · MacPorts ports tree: devel/checkmake/Portfile from https://api.github.com/repos/macports/macports-ports/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 configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment