# lychee mit Homebrew, apk, MacPorts, Nix, pacman, zypper, scoop, winget installieren

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

## Installation

```sh
sudo av install brew:lychee
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install lychee
```

  Evidenz: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install lychee
```

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

### Linux

- apk (92%):

```sh
sudo apk add lychee
```

  Evidenz: Alpine Linux edge package indexes: lychee from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz

- Nix (92%):

```sh
nix profile install nixpkgs#lychee
```

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

- pacman (92%):

```sh
sudo pacman -S lychee
```

  Evidenz: Arch Linux sync databases: lychee from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

- zypper (92%):

```sh
sudo zypper install lychee
```

  Evidenz: openSUSE Tumbleweed package metadata: lychee from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst

### Windows

- Scoop (92%):

```sh
scoop install main/lychee
```

  Evidenz: Scoop official bucket manifest trees: bucket/lychee.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

- winget (92%):

```sh
winget install --id lycheeverse.lychee -e
```

  Evidenz: Windows Package Manager source index: lycheeverse.lychee from https://cdn.winget.microsoft.com/cache/source.msix

## Paketfakten

- **Paketschlüssel:** brew:lychee
- **Paketmanager:** Homebrew
- **Version:** 0.24.2
- **Quellzusammenfassung:** Fast, async, resource-friendly link checker
- **Homepage:** <https://lychee.cli.rs/>
- **Repository:** <https://github.com/lycheeverse/lychee>
- **Zuletzt aktualisiert:** 2026-05-17T19:17:45Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- lychee (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

lychee is a fast, asynchronous Rust link checker for websites, Markdown, HTML, and other text-like files. It is distributed as a CLI, a Rust library, Docker image, prebuilt binaries, and a GitHub Action.

### Projektgeschichte

The official README says the first prototype was built in episode 10 of Hello Rust. The public Git history for the standalone repository begins in August 2020, and early tags followed in December 2020. Since then the project has developed into a lycheeverse-maintained CLI plus `lychee-lib` library.

The project emphasizes Rust async execution, stream-oriented checking, static binaries, and CI-oriented output formats. Its feature table compares it with other link checkers such as awesome_bot, muffet, broken-link-checker, linkinator, linkchecker, markdown-link-check, and fink, positioning lychee in the cross-language ecosystem of documentation-quality tooling.

### Adoptionsgeschichte

Upstream documents many install paths: Arch, openSUSE, Ubuntu snap, Alpine, Homebrew, MacPorts, Docker, Nix, FreeBSD, Termux, Conda, Scoop, WinGet, Chocolatey, prebuilt binaries, cargo-binstall, Cargo, and GitHub Actions. The README also lists notable users including OpenSearch, papers-we-love, PingCAP docs, Microsoft WhatTheHack, HashiCorp Consul, Fastify, Nuxt, containerd, Gradle, and tldr-pages.

### Wie es verwendet wird

Common usage is `lychee [OPTIONS] [inputs]...`, either locally over documentation files and websites or in CI through the GitHub Action. The official config guide says `lychee.toml` is used by default when present in the current working directory, and `--config <PATH>` can point at another TOML config.

For GitHub-heavy link sets, lychee can use a GitHub token through `GITHUB_TOKEN`, `--github-token`, or the config file. The docs frame this as a way to avoid GitHub API rate limiting when checking public repository links.

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

lychee is a package-nerd favorite because it is the modern static Rust binary version of a classic maintenance chore: keep every link in your docs alive. Its broad install matrix, GitHub Action, Docker image, library crate, config file, and stable CI exit codes make it easy for distributions and automation platforms to carry.

### Zeitleiste

- 2020: Standalone repository history begins after extraction from the Hello Rust show repository.
- 2020: v0.2.0, v0.3.0, and v0.4.0 are tagged.
- 2021: v0.5 and v0.6 alpha releases follow.
- 2026: v0.24.x releases are tagged, with docs noting lychee-v0.24.2.

### Related projects

- lychee-action provides the GitHub Actions integration.
- lychee-lib exposes the Rust library used by the CLI.
- The README compares lychee with awesome_bot, muffet, broken-link-checker, linkinator, linkchecker, markdown-link-check, and fink.

### Quellen

- <https://github.com/lycheeverse/lychee>
- <https://lychee.cli.rs/>
- <https://lychee.cli.rs/guides/cli/>
- <https://lychee.cli.rs/guides/config/>
- <https://raw.githubusercontent.com/lycheeverse/lychee/master/README.md>
- source_facts.package-manager


## Sicherheitshinweise

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



## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: lychee.toml

## Credential files

- Unix: lychee.toml
## Andere Paketmanager-Einträge

- Nix - lychee: normalized package name match | nixpkgs package indexes: pkgs/by-name/ly/lychee/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- apk - lychee - 0.24.2-r0: normalized package name match | Alpine Linux edge package indexes: lychee from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Fast, async, resource-friendly link checker written in Rust | https://lychee.cli.rs
- apk - lychee-doc - 0.24.2-r0: normalized package name match | Alpine Linux edge package indexes: lychee-doc from https://dl-cdn.alpinelinux.org/alpine/edge/testing/x86_64/APKINDEX.tar.gz | Fast, async, resource-friendly link checker written in Rust (documentation) | https://lychee.cli.rs
- pacman - lychee - 0.24.2-1: normalized package name match | Arch Linux sync databases: lychee from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | Fast, async, resource-friendly link checker written in Rust | https://lychee.cli.rs
- zypper - lychee - 0.24.2-1.3: normalized package name match | openSUSE Tumbleweed package metadata: lychee from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Fast, async, stream-based link checker written in Rust | https://lychee.cli.rs
- MacPorts - lychee: normalized package name match | MacPorts ports tree: devel/lychee/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Scoop - main/lychee: normalized package name match | Scoop official bucket manifest trees: bucket/lychee.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1
- winget - lycheeverse.lychee: normalized package name match | Windows Package Manager source index: lycheeverse.lychee from https://cdn.winget.microsoft.com/cache/source.msix


## Combined YAML source

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


## Quellen

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