---
name: "aports-lint"
section: "1"
platform: "linux"
package: "atools"
version: "20.2.2-5"
release: "Arch Linux 2026-11-01"
platforms: ["linux"]
url: "https://new.carta.tech/aports-lint"
---

# aports-lint(1)

A linter for Alpine Linux's ports (aports)

## 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. See **[alint(5)](/alint/5.md)** under the aports-lint section for an explanation of each violation that aports-lint checks for.

aports-lint will print the policy violations found and exit 1, if no violations are found then nothing will be printed and it will exit 0.

## OUTPUT

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

SEVERITYCERTAINITY:\[TAG\]:PATH::MSG

- •

  **SEVERITY** refers to how severe a violation is, ranging from **S** to **M**.

- •

  **CERTAINITY** refers to how likely it is not a false positive, ranging from **C** to **P**

- •

  **TAG** refers to the tag of the violation, see **[alint(5)](/alint/5.md)** for more details.

- •

  **PATH** refers to the path given for **apkbuild-lint** to check.

- •

  **MSG** is a short message meant for humans to know what is the violation.

## EXPENSIVE FIND REPO

A slower yet more accurate version of the internal find\_repo function used to detect whether a package is present in an upper repo can be accessed by setting the **EXPENSIVE\_FIND\_REPO** variable. Using it will cause time needed to process an APKBUILD to jump from miliseconds to seconds and is not recommended if providing feedback to the user in a timely manner is required (like running this as a vim ALE plugin).

## AUTHORS

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

## SEE ALSO

**[alint(5)](/alint/5.md)** **[apkbuild-lint(1)](/apkbuild-lint/1.md)**