secfixes-check(1)

🎀 secfixes-check(1) 🎀

okay so bestie, let me tell you about secfixes-check — it's the linter for Alpine Linux's secfixes declarations in APKBUILDs, and honestly it's giving main character energy in the "keeping your packaging honest" department 💅

---

✨ SYNOPSIS ✨

secfixes-check <apkbuild...>

🌸 DESCRIPTION 🌸

So picture this: secfixes-check is a linter for secfixes declarations inside APKBUILDs. She reads the file you hand her in each command-line argument, checks for policy violations on secfixes, and also validates the yaml by trying to load it with the 'lyaml' module from lua. Like, double duty, no cap 💖

If you wanna know what each violation actually means, go read alint(5) under the secfixes-check section — that's where every violation secfixes-check looks for gets explained, iykyk.

Then: secfixes-check prints the policy violations, and exits with the code that corresponds to the number of violations found. And if there are none? Nothing is printed and she exits with code 0. Clean. Iconic. Periodt. ✨

🔥 OUTPUT 🔥

secfixes-check prints to stdout whenever a policy violation is found, in this exact format:

SEVERITYCERTAINITY:[TAG]:PATH::MSG

okay let's break down the vibes:

• SEVERITY — how severe a violation is, ranging from S to M. (yes that's the whole range, don't come for me 💀)
• 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. a little love letter to your future self 🫶

---

👑 AUTHORS 👑

Maintained by Leo <thinkabit.ukim@gmail.com> — shoutout to Leo, the real one 🫡

🦋 SEE ALSO 🦋

• alint(5)
• apkbuild-lint(1)

---

and that's the whole page bestie! 🌈 this one's from the General Commands Manual, dated 2026-10-14, and it's secfixes-check(1) — go forth and lint those APKBUILDs, you're gonna slay 💜🎀