pkglint

A security-focused linter for Arch Linux packages.

pkglint statically analyzes PKGBUILDs and their install scriptlets, without ever sourcing them, and reports findings about source integrity, build hermeticity, code execution, and persistence patterns, condensed into a letter grade per package. It parses a real bash AST (mvdan.cc/sh), so the quoting and line-continuation tricks that slip past regex-based scanners don't work here.

It also reproduces makepkg's own build-breaking metadata checks, so a PKGBUILD that would fail to build is caught (and, where the fix is mechanical, rewritten) before you run makepkg.

Built packages (*.pkg.tar.zst and friends) are inputs too: pkglint inspects the archive the way namcap does (ELF hardening, stripping, dependencies inferred from linked libraries and shebangs, packaged .INSTALL scriptlets, filesystem hygiene) while never executing anything from the package (ELF files are parsed, not loaded; no ldd).

The AUR Report Card runs pkglint nightly over the official repositories and the AUR's most-voted and recently updated packages, with a page per package and per rule.

$ pkglint ~/pkgbuilds/somepkg
somepkg: grade F, 3 finding(s)
  PKGBUILD:16:3: critical [PB304] a network download is piped straight into bash and executed
  PKGBUILD:11:1: error [PB101] remote source "http://..." has no checksum (SKIP): the download is never verified
  PKGBUILD:24:3: warn [PB403] chmod 4755 creates a setuid/setgid file

1 package linted: 1 with findings
1 finding(s) fixable with --unsafe-fix

Packages with nothing to report are only counted in the closing summary line (--verbose lists them individually). The line after it tallies the findings a fix run will attempt, split by the flag that applies them.

Install

AUR

yay -S pkglint

PyPI

uv tool install pkglint

Go

go install github.com/jmelahman/pkglint@latest

GitHub Releases

Prebuilt binaries for Linux and macOS (amd64 and arm64) are attached to every release.

Commit hook

repos:
  - repo: https://github.com/jmelahman/pkglint
    rev: a3b3651b15d3c2b04b2548a39925643a625d5f4e # frozen: v1.6.1
    hooks:
      - id: pkglint
      - id: pkglint-build

Four hook ids are available:

• pkglint builds from source with the Go toolchain.
• pkglint-system runs whatever pkglint is already on $PATH.
• pkglint-fix applies the safe auto-fixes in place (offline by default).
• pkglint-build builds each PKGBUILD and lints the package it produces (see Build and validate).

Tune any of them with args:, e.g. args: [--ignore, PB105, --fail-on, critical].

Usage

pkglint [flags] [path ...]     # paths are package dirs, PKGBUILD files,
                               # or built packages (*.pkg.tar.*) (default: .)

  --format text|json|sarif     # output format (sarif = SARIF 2.1.0, for code scanning)
  --fail-on SEVERITY           # exit 1 at or above: info, warn (default), error, critical, never
                               # (a path that cannot be loaded exits 1 even with never)
  --ignore PB105,PB206         # disable rules
  --select PB101,PB304         # check only these rules (--ignore still subtracts from them)
  --color auto|always|never    # colorize text output (auto = only on a terminal; honors NO_COLOR)
  --verbose                    # list packages with no findings individually, not just in the summary
  --rules                      # list every rule with its documentation
  --fix                        # apply safe auto-fixes in place
  --unsafe-fix                 # also apply behavior-changing fixes (implies --fix)
  --diff                       # with --fix/--unsafe-fix/--add-ignores: show changes instead of writing
  --offline                    # with --fix: skip fixes needing network (VCS ref resolution, https probing)
  --add-ignores                # insert ignore directives suppressing every current finding
  --no-inline-ignores          # disregard ignore directives (audit an untrusted package)

pkglint explain PB101 ...      # print one rule's documentation, example, and
                               # how to fix or suppress it (ID or name, any case)

Suppress a reviewed, intentional finding inline:

# pkglint: ignore=PB204
go build -o "$pkgname" .

The directive covers its own line and the line below it, in the file it appears in only. --add-ignores writes one for every finding still reported, so a package can adopt pkglint before fixing everything it flags; --diff previews the insertions. A directive that no longer matches a finding is itself flagged (PB913, stale-ignore-directive) and deleted by --fix, so a fixed issue cannot leave behind a comment that would silence its return. When reviewing a package you don't trust, --no-inline-ignores reports whatever the maintainer suppressed.

Auto-fixing

--fix rewrites what it can and prints every change; --diff previews without writing. Fixes come in two tiers: safe fixes preserve behavior or restore a security default; unsafe fixes are mechanical but change what the build does, so review them.

Every fix stands down where it cannot see the whole picture (a flag arriving through an expansion, an array it cannot re-render faithfully, a rename it cannot prove complete) rather than leave a half-applied edit. An inline # pkglint: ignore= on a finding's line also suppresses its fix. Findings whose remediation isn't a mechanical rewrite print a one-line suggestion instead (updpkgsums for checksums, makepkg --printsrcinfo for a stale .SRCINFO), computed from what is left after fixing.

Safe: --fix

Unsafe: --unsafe-fix

PB102 checksums

The PB102 fix hashes sources already downloaded into the package directory or $SRCDEST (pkglint never fetches a source) and writes a digest only after re-computing the existing md5/sha1 from the same bytes and finding it matches, so the new sha256sums covers exactly what the weak digest already vouched for. Sources that aren't present or a digest that doesn't match leave the finding standing, and updpkgsums remains the way to close it. The weak array is kept; the edit is purely additive.

From the build: pkglint build --fix

The built-package rules judge an artifact, so their fixes live on the one command that has both: pkglint build --fix lints the PKGBUILD, builds it, lints the archive, and writes the answer back into the PKGBUILD it built (--diff previews, --unsafe-fix widens the tier as it does elsewhere). It only touches a PKGBUILD that declares exactly one package, since a split PKGBUILD's depends belongs to each package_<name>() rather than to the file, and only the error gaps: a library reached transitively or through an optdepends is a judgment the maintainer makes. The build gate runs first, as always: a build that is refused produces no archive and fixes nothing. The PKGBUILD-scope fixes above stay with pkglint --fix.

Build and validate

The built-package rules need a built package. pkglint build produces one:

$ pkglint build ~/pkgbuilds/somepkg

It lints the PKGBUILD, hands the package to makepkg, and then lints the archive that comes out. pkglint-build is the same thing as a hook; it is stages: [manual] because a full build has no business running on every commit.

This is the one pkglint command that executes a PKGBUILD, because that is what makepkg does. It is a separately named verb that pkglint <path> never reaches, and it refuses to build a package whose static findings reach --fail-on, always refusing on a critical finding no matter what --fail-on says. --force overrides that; the findings still count toward the exit code.

Because that gate decides whether to run code, the PKGBUILD gets no say in it:

• The gate disregards the file's own # pkglint: ignore= directives: a curl | bash with an ignore=PB304 above it is still a curl | bash. The report printed beside the refusal still honors them; only the decision to execute is taken on the unsuppressed findings.
• A file argument must be a PKGBUILD, since makepkg builds the PKGBUILD in its working directory regardless of which file pkglint linted.
• makepkg's -p and -D/--dir are rejected, for the same reason.

Because build is a verb, a package directory named ./build is spelled pkglint ./build.

The packaging tree is left exactly as it was found: makepkg writes into a temporary PKGDEST, and the PKGBUILD is held read-only so a pkgver() package cannot rewrite the file that was gated. --keep <dir> moves the archives out. Sources are cached in ${XDG_CACHE_HOME:-~/.cache}/pkglint/sources and the build tree goes under $TMPDIR; export $SRCDEST or $BUILDDIR to relocate either. Dependencies are not synced, since that needs root and a hook that prompts for a password is a hook that hangs. Pass -- -s (or --makepkg-arg=-s, the form that survives pre-commit's args:) to opt in. --nosign is passed for the same reason.

Without makepkg on the host, or with --docker or an explicit --image, the build runs in a container. Name the image with --image or $PKGLINT_BUILD_IMAGE and pick the runtime with $PKGLINT_BUILD_RUNNER (docker by default, else podman). The package directory is bind-mounted read-only and the archives come back out with <runner> cp, owned by you. The image is your trust decision, and the container is a convenience, not a sandbox: the PKGBUILD's own code still runs. -- -s inside one needs an image with passwordless sudo pacman, which stock archlinux:base-devel lacks.

Rules

pkglint --rules prints the full documentation for each, with its severity and the flag that auto-fixes it. pkglint explain PB101 (or pkglint explain skipped-checksum) prints one rule's page: documentation, a flagged snippet beside the preferred spelling, and how to fix or suppress it. The rule reference publishes the same pages.

Relationship to namcap

pkglint covers namcap's rule set, both the PKGBUILD checks and the built-package checks, with a few deliberate differences:

• Nothing from the analyzed package is ever executed. namcap runs ldd -r -u on packaged binaries; pkglint compares dynamic symbol tables instead.
• Findings the lint host cannot verify are reported as info, not as hard errors.
• Everything lands in the same graded, suppressible, JSON/SARIF-capable report the PKGBUILD rules use.
• Dependency inference reads pacman's local database directly and skips just those rules on non-Arch hosts.

Grading

The first row that matches sets the grade:

A grade is a static hygiene score, not a malware verdict: it measures how reviewable and reproducible a PKGBUILD is. A low grade means "worth reviewing", never "malicious", and a high grade is not an endorsement. Static analysis cannot catch a malicious upstream release pinned with a perfectly valid checksum.

License

GPLv3. See LICENSE.