# Installer vuls avec Homebrew, Nix, apt Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de vuls pour les workflows d'agents IA. ## installation ```sh sudo av install brew:vuls ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install vuls ``` Preuve: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#vuls ``` Preuve: nixpkgs package indexes: pkgs/by-name/vu/vuls/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Ubuntu apt (92%): ```sh sudo apt install vuls ``` Preuve: Ubuntu 24.04 LTS package indexes: vuls from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz ## Faits du paquet - **Clé du paquet:** brew:vuls - **Gestionnaire de paquets:** Homebrew - **Version:** 0.40.1 - **Résumé source:** Agentless Vulnerability Scanner for Linux/FreeBSD - **Page d'accueil:** - **Dépôt:** - **Dernière mise à jour:** 2026-07-30T03:56:20Z - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - future-vuls (alias) - snmp2cpe (alias) - trivy-to-vuls (alias) - vuls (alias) - vuls-scanner (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 0.40.1 ## Historique du projet et usages Vuls is an agentless vulnerability scanner written in Go for Linux, FreeBSD, and later broader targets such as containers, application libraries, WordPress, network devices, Windows, and macOS. Its core idea is to inventory installed software and match it against vulnerability intelligence without requiring a resident scanner agent on every host. ### Historique du projet The GitHub repository was created under Future Architect in March 2016, and the README credits kotakanbe as the creator. The project grew from a concrete operations problem: administrators often cannot simply enable automatic updates on production servers, yet manually tracking NVD, OVAL, vendor trackers, and package advisories across many machines is error-prone. Vuls developed as a Go-based scanner with multiple scan modes. Its documentation describes remote scans over SSH, local scans for hosts that should not be reached centrally, and server mode where target hosts collect software information and send it to a Vuls server over HTTP. Over time Vuls expanded from OS package vulnerability checks into a larger security-data workflow. The README lists data sources and integrations including NVD, JVN, vendor OVAL feeds, distribution security trackers, Microsoft CVRF, exploit and PoC data, CISA Known Exploited Vulnerabilities, MITRE ATT&CK and CAPEC data, application dependency data, and WordPress scanning. ### Historique d'adoption Vuls is one of the more visible open-source host vulnerability scanners from the Go security tooling wave of the mid-2010s. By July 2026, GitHub repository metadata showed about 12.2k stars and more than 1.2k forks, indicating durable use well beyond a single-company internal tool. The project also accumulated companion commands and data tools. Current release assets include `vuls`, `vuls-scanner`, `future-vuls`, `snmp2cpe`, and `trivy-to-vuls`, showing how the project adapted to adjacent scanners, CPE mapping, and hosted-service workflows. ### Modes d'utilisation A common Vuls workflow is to create a `config.toml`, fetch or serve vulnerability dictionaries, scan target machines, and then generate reports for humans or automation. Remote mode uses SSH from a central machine; local and server modes reduce the need for inbound access to target hosts. Vuls does not update vulnerable packages itself. Its value is detection, prioritization, and reporting: it tells operators which servers and software are affected, adds severity and exploit context when available, and can send notifications through channels such as email or Slack. ### Pourquoi les passionnés de paquets s'y intéressent Vuls matters to package and security nerds because it turns package inventories, CVE identifiers, OVAL feeds, vendor advisories, CPE naming, and exploit metadata into a repeatable command-line workflow. It is especially relevant for people who care about the gap between distro package versions and upstream vulnerability identifiers. ### Chronologie - 2016: future-architect/vuls was created on GitHub on March 27, 2016. - 2017: FreeBSD ports carried Vuls as an agentless vulnerability scanner with SSH, TUI, notification, and multi-distribution support. - 2020: v0.14.0 was published on December 23, 2020, among the older releases still visible through the GitHub releases API page inspected for this run. - 2026: v0.39.3 was published on June 9, 2026, with signed release artifacts for multiple Vuls-related commands. ### Related projects - Vuls is related to go-cve-dictionary, goval-dictionary, go-cpe-dictionary, gost, go-exploitdb, vulsctl, VulsRepo, Trivy, OWASP Dependency-Check, NVD, JVN, OVAL, and distribution security trackers. ### Sources - - - - - - - ## Notes de sécurité escape, surveillance, or offensive capability signal. - **Risque Geiger:** red / moyen - escape, surveillance, or offensive capability signal ## 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: config.toml ## Autres enregistrements de gestionnaires de paquets - Nix - vuls: normalized package name match | nixpkgs package indexes: pkgs/by-name/vu/vuls/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Ubuntu apt - vuls - 0.6.1-5: normalized package name match | Ubuntu 24.04 LTS package indexes: vuls from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | Vulnerability scanner for Linux/FreeBSD, agentless, written in Go | https://github.com/future-architect/vuls ## Combined YAML source View the package source record on GitHub. [combined/vuls.yml](https://github.com/mxcl/pkgdb/blob/main/combined/vuls.yml) ## Sources - 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