# svlint mit Homebrew, Nix installieren

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

## Installation

```sh
sudo av install brew:svlint
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install svlint
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#svlint
```

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

## Paketfakten

- **Paketschlüssel:** brew:svlint
- **Paketmanager:** Homebrew
- **Version:** 0.9.5
- **Quellzusammenfassung:** SystemVerilog linter
- **Homepage:** <https://github.com/dalance/svlint>
- **Repository:** <https://github.com/dalance/svlint>
- **Zuletzt aktualisiert:** 2026-06-14T15:13:51+02:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- svlint (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

svlint is a Rust command-line linter for SystemVerilog. It belongs to the small but important group of HDL tools that package managers expose as normal Unix-style binaries, making hardware-design checks easier to install in CI jobs and editor workflows.

### Projektgeschichte

The upstream README describes svlint as a SystemVerilog linter compliant with IEEE1800-2017, written in Rust and based on sv-parser. GitHub repository metadata records the dalance/svlint repository as created on 2019-10-21, and the releases API records v0.1.0 published on 2019-10-29.

### Adoptionsgeschichte

The README documents several distribution routes: downloadable releases, Cargo installation with `cargo install svlint`, and Snap installation. The input package-manager facts also show it packaged for Homebrew and Nix, which reflects its use beyond Rust-only environments.

### Wie es verwendet wird

Typical usage is the direct CLI pattern: run `svlint --help` to inspect options, `svlint --version` to identify the installed binary, and configure lint rules through `.svlint.toml`. The manual says svlint searches upward from the current directory for `.svlint.toml`, allows `--config`, and supports `SVLINT_CONFIG` for explicit project-wide rules.

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

svlint matters to package nerds because it brings hardware linting into the same install-and-run model as software linters. It also exposes prewritten rulesets and wrapper scripts, so the packaging boundary affects how much of the upstream release is available beyond the main binary.

### Zeitleiste

- 2019: GitHub repository created for dalance/svlint.
- 2019: v0.1.0 release published.
- 2025: v0.9.5 release published.

### Related projects

- svlint is based on sv-parser, is integrated into svls, and has an official sample repository for external svlint plugins.

### Quellen

- <https://api.github.com/repos/dalance/svlint>
- <https://api.github.com/repos/dalance/svlint/releases?per_page=100>
- <https://github.com/dalance/svlint>
- <https://github.com/dalance/svlint/blob/master/MANUAL.md>
- source_facts.package-manager


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## 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: .svlint.toml
## Andere Paketmanager-Einträge

- Nix - svlint: normalized package name match | nixpkgs package indexes: pkgs/by-name/sv/svlint/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/svlint.yml](https://github.com/mxcl/pkgdb/blob/main/combined/svlint.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