# zlint mit Homebrew, apt, MacPorts, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für zlint in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:zlint
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install zlint
```

  Evidenz: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install zlint
```

  Evidenz: MacPorts ports tree: security/zlint/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- Debian apt (92%):

```sh
sudo apt install zlint
```

  Evidenz: Debian stable package indexes: zlint from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz

- Nix (92%):

```sh
nix profile install nixpkgs#zlint
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/zl/zlint/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:zlint
- **Paketmanager:** Homebrew
- **Version:** 3.7.1
- **Quellzusammenfassung:** X.509 Certificate Linter focused on Web PKI standards and requirements
- **Homepage:** <https://zmap.io/>
- **Repository:** <https://github.com/zmap/zlint>
- **Zuletzt aktualisiert:** 2026-07-25T21:50:59+02:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- zlint (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 3.7.1
## Projektgeschichte und Nutzung

ZLint is a Go-based X.509 certificate linter from the ZMap/Web PKI research ecosystem. It encodes checks from RFC 5280, CA/Browser Forum Baseline Requirements, and related PKI rules so certificates can be linted before or after issuance.

### Projektgeschichte

The public GitHub repository was created in 2016 under the ZMap organization, and the 2018 paper Tracking Certificate Misissuance in the Wild introduced ZLint as part of a systematic study of certificate authority mistakes. The paper describes manually dissecting RFC 5280 and CA/B Forum Baseline Requirements into standalone lints, with hundreds of checks that could be run over certificate corpora.

ZLint grew out of the same measurement culture as ZMap and Censys: turn public Internet and Web PKI data into testable artifacts. Its README presents it both as a command-line tool and as a library that can be integrated into CA software, which is why the package matters beyond one-off certificate inspection.

### Adoptionsgeschichte

The original research ran ZLint over browser-trusted certificates in Censys, making it part of a Web PKI measurement pipeline rather than only a local developer utility. The tool helped quantify how certificate construction errors changed over time and how errors correlated with CA operational practices.

The CA/Browser Forum lists ZLint among linting software resources, alongside tools such as pkilint and pkimetal. That placement is significant because CA/B Forum rules are the policy surface ZLint was built to encode, and the listing reflects its role in the public certificate-issuance tooling ecosystem.

### Wie es verwendet wird

Practical use is usually pre-issuance or post-issuance certificate checking: feed a certificate to the zlint CLI, or call the Go library from CA, CT-monitoring, or compliance tooling. Results are useful for catching malformed extensions, missing required fields, invalid names, and other policy or standards violations that are easier to automate than to audit by hand.

For package users, ZLint is a specialist security tool: it is not a TLS scanner like testssl.sh and not a certificate parser like OpenSSL. Its niche is standards and policy linting for certificate objects themselves.

### Warum Paket-Nerds sich dafür interessieren

ZLint is a good example of research software becoming operational infrastructure. It packages Web PKI policy as runnable checks, so a formula install gives operators and researchers the same kind of linting logic used in large-scale certificate studies.

It also shows the ZMap project's broader pattern: small focused command-line tools that turn Internet measurement and PKI knowledge into reusable Unix-style components.

### Zeitleiste

- 2016-11-30: The zmap/zlint GitHub repository is created.
- 2018: Tracking Certificate Misissuance in the Wild introduces and releases ZLint as a Go-based certificate linting framework.
- 2018: The paper reports running ZLint over browser-trusted certificates in Censys.
- 2020s: The CA/Browser Forum resources page lists ZLint as X.509 certificate linting software.

### Related projects

- ZMap and Censys are related through the broader Internet measurement and Web PKI research lineage.
- pkilint and pkimetal occupy adjacent PKI linting and meta-linting roles listed by the CA/Browser Forum.
- certlint is an earlier certificate linting tool referenced in Web PKI linting literature.

### Quellen

- <https://api.github.com/repos/zmap/zlint>
- <https://cabforum.org/resources/tools/>
- <https://github.com/zmap/zlint>
- <https://jhalderm.com/pub/papers/misissuance-sp18.pdf>


## Sicherheitshinweise

Für zlint wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.


## Andere Paketmanager-Einträge

- Debian apt - zlint - 3.6.2-4: normalized package name match | Debian stable package indexes: zlint from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | X.509 Certificate Linter focused on Web PKI standards (program) | https://github.com/zmap/zlint
- Nix - zlint: normalized package name match | nixpkgs package indexes: pkgs/by-name/zl/zlint/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- MacPorts - zlint: normalized package name match | MacPorts ports tree: security/zlint/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/zlint.yml](https://github.com/mxcl/pkgdb/blob/main/combined/zlint.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
