aports-lint(1)

📦
version 20.2.2 · 2 versions
, in alpine 3.24

💅 aports-lint(1) 💅

okay so bestie, you're looking at the aports-lint(1) page from the General Commands Manual, and it's giving Alpine Linux package-linting realness ✨

🌸 NAME 🌸

aports-lint — a linter for Alpine Linux's ports (aports) 🫶

✨ SYNOPSIS ✨

aports-lint <apkbuild...>

🎀 DESCRIPTION 🎀

aports-lint is a linter for packages in aports and their relation to other packages in the same repo. It searches for instances of policy violations, duplicate packages and others. For an explanation of each violation that aports-lint checks for, see alint(5) under the aports-lint section.

When it finds policy violations, aports-lint will print them and exit 1. If no violations are found, then nothing will be printed and it will exit 0. no cap, that's the whole vibe check 💅

🔥 OUTPUT 🔥

aports-lint will print to stdout whenever a policy violation is found, in the following format:

SEVERITYCERTAINITY:[TAG]:PATH::MSG
  • SEVERITY — how severe a 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 given for apkbuild-lint to check 🛤️
  • MSG — a short message meant for humans to know what the violation is 💬

🔍 EXPENSIVE FIND REPO 🔍

There's a slower yet more accurate version of the internal find_repo function, which is used to detect whether a package is present in an upper repo. You can access it by setting the EXPENSIVE_FIND_REPO variable.

Using it will cause the time needed to process an APKBUILD to jump from miliseconds to seconds, and it is not recommended if providing feedback to the user in a timely manner is required (like running this as a vim ALE plugin). fr fr, that speed drop is real 😭

👑 AUTHORS 👑

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

🌈 SEE ALSO 🌈

💖 That's the page, bestie — from the General Commands Manual, aports-lint(1), dated 2026-10-14. byeee! 💅✨

📦 where this page comes from