# vunnel mit Homebrew, Nix installieren

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

## Installation

```sh
sudo av install brew:vunnel
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install vunnel
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#vunnel
```

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

## Paketfakten

- **Paketschlüssel:** brew:vunnel
- **Paketmanager:** Homebrew
- **Version:** 0.63.1
- **Quellzusammenfassung:** Tool for collecting vulnerability data from various sources
- **Homepage:** <https://github.com/anchore/vunnel>
- **Repository:** <https://github.com/anchore/vunnel>
- **Zuletzt aktualisiert:** 2026-07-31T20:02:02Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- vunnel (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

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

Vunnel is Anchore's vulnerability-data collection and transformation tool: an ETL-style command-line program used to fetch upstream advisory data, normalize it, and store it for downstream vulnerability database construction.

### Projektgeschichte

Anchore's public repository for Vunnel was created in November 2022. The project describes itself as a tool for fetching, transforming, and storing vulnerability data from many sources, including Linux distribution feeds, GitHub Security Advisories, NVD, and other advisory services.

Vunnel sits in Anchore's Syft/Grype security-tooling ecosystem rather than being a user-facing scanner itself. Anchore's product documentation explains that Anchore Enterprise and Grype use multiple vulnerability sources because upstream advisory data is fragmented, and that Vunnel exists to understand those source-specific formats and emit a consistent form usable by the vulnerability database.

### Adoptionsgeschichte

Its adoption is mostly indirect: users of Grype and Anchore Enterprise benefit from Vunnel through the vulnerability database those tools consume. Anchore's public documentation for contributors treats Vunnel providers as the extension point for adding new vulnerability-data sources.

### Wie es verwendet wird

In package-nerd terms, Vunnel is the data plumbing behind a scanner database. Maintainers write providers that implement source-specific update logic, choose a schema such as OSV or OpenVEX where possible, and normalize feed data so later matching tools can reason over it.

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

Vunnel matters because vulnerability scanners are only as good as their advisory feeds. It is the small, specialized tool that turns a messy world of distro trackers, NVD records, GitHub advisories, and emerging vulnerability-exchange schemas into buildable database input.

### Zeitleiste

- 2022: The anchore/vunnel GitHub repository was created.
- 2023: Public releases in the 0.x series show Vunnel becoming a separately versioned component of Anchore's vulnerability-data pipeline.
- 2026: Anchore contributor documentation describes new-provider schema selection, including preference for OSV and other externally specified formats.

### Related projects

- Grype consumes vulnerability database data built from upstream feeds; grype-db is the database-builder side of the same Anchore ecosystem; OSV, OpenVEX, and CSAF are related vulnerability-data formats mentioned in Vunnel contributor guidance.

### Quellen

- <https://api.github.com/repos/anchore/vunnel>
- <https://docs.anchore.com/5.13/docs/vulnerability_management/>
- <https://github.com/anchore/vunnel>
- <https://oss.anchore.com/docs/contributing/vunnel/>


## Sicherheitshinweise

Für vunnel 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: .vunnel.yaml
## Andere Paketmanager-Einträge

- Nix - vunnel: normalized package name match | nixpkgs package indexes: pkgs/by-name/vu/vunnel/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/vunnel.yml](https://github.com/mxcl/pkgdb/blob/main/combined/vunnel.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