apkbuild-lint(1)

💅 apkbuild-lint — the aports glow-up inspector

okay so real talk, this is the General Commands Manual page for apkbuild-lint, and it's basically the friend who looks at your APKBUILD and goes "bestie… what is this" 🫶

✨ NAME ✨

apkbuild-lint — a linter for Alpine Linux's build files (apkbuild) 🎀

✨ SYNOPSIS ✨

apkbuild-lint <apkbuild...>

✨ DESCRIPTION ✨

So apkbuild-lint is a linter for packages in aports, no cap. It goes through the APKBUILD file and checks it for violations of policy, superfluous statements, stylistic violations and others 💅 If you wanna know what each individual violation actually means, go read alint(5) under the apkbuild-lint section — that's where every check is explained, iykyk.

The vibe check itself is simple: apkbuild-lint prints the policy violations it found and exits 1. And if there are no violations? Nothing gets printed, and it exits 0. Clean. Iconic. Periodt ✨

🌸 ENVIRONMENT 🌸

• CUSTOM_VALID_OPTIONS — set this to a whitespace-separated list of variables, and those variables will be considered valid inside the options= variable of an APKBUILD 🦋

🦋 OUTPUT 🦋

Whenever it finds a policy violation, apkbuild-lint prints to stdout in this exact format:

SEVERITYCERTAINITY:[TAG]:PATH::MSG

and here's the breakdown of every piece, bestie:

• SEVERITY — how severe the violation is, ranging from S to M.
• CERTAINITY — how likely it is not a false positive, ranging from C to P.
• TAG — the tag of the violation, see alint(5) for more details.
• PATH — the path you gave apkbuild-lint to check.
• LINE — the number of the line where the violation was found.
• MSG — a short message meant for humans, so you know what the violation actually is 💖

👑 AUTHORS 👑

Maintained by Leo <thinkabit.ukim@gmail.com> 🫶

🧚 SEE ALSO 🧚

alint(5) aports-lint(1)

---

and that's the whole page, bestie 🌈 this version of apkbuild-lint(1) is dated 2026-10-14 — go forth and let your APKBUILD be unproblematic 💜