Vuls is an open-source vulnerability scanner, run agentless from the command line, that checks Linux, FreeBSD, Windows, and macOS hosts against CVE databases and reports which systems are affected. It's built for system administrators who otherwise have to manually track NVDNVDThe National Vulnerability Database, maintained by NIST, is the U.S. government repository of CVE records enriched with CVSS scores and metadata; cyber tools query it to drive vulnerability prioritization. entries and patch status across many servers, and it's designed to run on a schedule via cron so scanning happens automatically instead of relying on someone remembering to check. Its detection backend, vuls2, pulls from sources like ExploitDB, VulnCheck, the EU Vulnerability Database, and Red Hat's CVE data, and covers package scanning down to language-level dependency files such as Python lockfiles. First committed in 2016, it remains under active development, with 153 contributors and a release only 22 days old.
Vuls is an agentless vulnerability scanner for Linux/FreeBSD, written in Go, that automatically detects and reports vulnerabilities affecting servers.
Which of my servers are affected by a newly disclosed CVE?
checks installed package versions against CVE data pulled from ExploitDB, VulnCheck, the EU Vulnerability Database, and Red Hat's CVE data, and lists which hosts carry the vulnerable package
Have I missed a vulnerability because nobody checked NVD this week?
runs on a schedule via cron so every host is re-checked automatically instead of depending on someone remembering to look
Which of my language-level dependencies has a known flaw, not just my OS packages?
scans lockfiles such as Python's down to the dependency level, separately from OS package checks, and reports the affected library
Is a given CVE actually exploitable, or just theoretically present?
surfaces exploit data and verification status alongside each match, so a listed CVE can be told apart from one with a known working exploit
How close is an unpatched host to losing vendor support entirely?
tracks end-of-life dates for the operating systems it scans and reports how that affects risk from unpatched packages
Which dev-only dependencies are inflating my vulnerability report versus my actual production risk?
tags dependencies pulled in for development separately from production ones, so the two can be reported and filtered apart
42 capabilities
across 6 capability groups
· 2 backed by code, an API document or a real run
Built from Vuls's releases, docs, README and our own runs.
“Seen” marks the month we first spotted a release the vendor didn't date.
Group names and tags are our labels.
+vuls2 detection and enrichment engineshippedRoutes vulnerability detection through the vuls2 engine, sharing a single database session across detect and enrich phases to reduce overhead.17 releases · 1 other source · first seen May 2016▸
Reports NVD and VulnCheck CVSS scores per source rather than collapsing them into a single score — NVD's own analysis and the CNA's metrics are now both preserved and labelled via Optional['source'].
v0.41.0 · Sep 2026
· source
· release history
Shares a single vuls2 DB session across detect and enrich phases per server, reducing I/O overhead.
v0.40.0-rc.1 · Jul 2026
· source
· release history
Routes NVD CPE detection and enrichment through the vuls2 engine with cpematch-expanded criteria, replacing go-cve-dictionary's version-range-only matching.
v0.40.0-rc.1 · Jul 2026
· source
· release history
Supports CVSS v4.0 scores from NVD and Trivy sources.
v0.27.0 · Oct 2024
· source
· release history
Adds vendorSeverity and full CVSS vector strings to each object in the cveContents array
v0.25.4 · May 2024
· source
· release history
config.toml gains a new cidr field in the server block for network-based target selection
v0.19.8 · Jul 2022
· source
· release history
example
Scan only Docker containers without scanning the host OS.$ vuls scan --only-containers
0.1.7 · Nov 2016
· source
+Windows CVE detectionshippedDetects CVEs affecting Windows hosts using Microsoft sources and surfaces MSRC Exploit Status alongside results.6 releases · 2 other sources · first seen Jun 2019▸
Switches Windows KB-based CVE detection from gost to the vuls2 backend, now reading vuls.db built from microsoft-* sources (breaking change: gost is no longer used for Windows; a vuls.db containing microsoft-* data is required).
v0.39.3 · Jun 2026
· source
· release history
Surfaces MSRC Exploit Status under CveContent.Optional["exploit"] for Windows detections, maintaining parity with the previous gost output.
v0.39.3 · Jun 2026
· source
· release history
Supports Python uv and Poetry v2 lockfile formats for dependency vulnerability scanning.
v0.30.0 · Mar 2025
· source
· release history
Accepts X-Vuls-OS-Family: amazon header for plain-text package submission
v0.8.1 · Jun 2019
· source
· release history
Supports JSON body with Family: amazon field for structured package data ingestion
v0.8.1 · Jun 2019
· source
· release history
Adds amazon OS family support in server mode to detect vulnerabilities on Amazon Linux instances
v0.8.1 · Jun 2019
· source
· release history
example
Ingest Amazon Linux 2 package list via plain-text HTTP endpoint$ curl -X POST -H 'X-Vuls-OS-Family: amazon' -H 'Content-Type: text/plain' --data-binary "$(rpm -qa --queryformat "%{NAME} %{EPOCHNUM} %{VERSION} %{RELEASE} %{ARCH}\n")" http://<HOST_IP>:5515/vuls
v0.8.1 · Jun 2019
· source
Ingest Amazon Linux package data via JSON API$ curl -X POST -H 'Content-Type: application/json' -d '{"Family": "amazon", "Release": "2 (Karoo)", "Packages": {"kernel": {"Name": "kernel", "Version": "4.14.114"}}}' http://localhost:5515/vuls
v0.8.1 · Jun 2019
· source
+Vendor and OS advisory detection sourcesshippedDetects vulnerabilities from OpenSSH security advisories, Apple security releases, and Oracle Solaris family advisories through the vuls2 detection engine.7 releases · first seen Mar 2017▸
Detects OpenSSH security advisories through the vuls2 detection engine.
v0.41.0-rc.2 · Sep 2026
· source
· release history
Detects Apple security releases through the vuls2 detection engine.
v0.41.0-rc.2 · Sep 2026
· source
· release history
Detects vulnerabilities in the Oracle Solaris family through the vuls2 detection engine.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
v0.41.0-rc.2 · Sep 2026
· source
· release history
Adds support for server scanning on SUSE systems using the text/plain output format to extend coverage beyond standard package managers.
v0.19.6 · Apr 2022
· source
· release history
Replaces the NVD column with a packages-column in report output
v0.19.5 · Mar 2022
· source
· release history
Add lockfiles array (e.g. package-lock.json, yarn.lock) under [servers.abuntu] (or other server sections) to enable Smart Programming Language Library Scan.
v0.8.0 · Jun 2019
· source
· release history
+ENISA EUVD integrationshippedIncorporates the European Union Vulnerability Database as an enrichment source via the vuls2 pipeline.4 releases · 1 other source · first seen Feb 2019▸
Adds ENISA EUVD (European Union Vulnerability Database) as a vuls2 enrich data source.
v0.40.0-rc.1 · Jul 2026
· source
· release history
EUVD content is no longer sourced from go-cve-dictionary; it is now provided solely through the vuls2 enrich path.
v0.40.0-rc.1 · Jul 2026
· source
· release history
Supports the EU Vulnerability Database (EUVD) as a new CVE detection source.
v0.37.0 · Dec 2025
· source
· release history
Adds GitHub security alerts integration via the report subcommand
v0.6.3 · Feb 2019
· source
· release history
example
Automate scanning and reporting vulnerabilities to GitHub Security Advisories.$ vuls report --github
v0.6.3 · Feb 2019
· source
+Custom CVE database integrationshippedAllows the tool to fetch vulnerability details from a custom HTTP API or specify alternative CVE database backends instead of relying on default sources.3 releases · 1 other source · first seen Nov 2018▸
Adds Dev flag to trivy-to-vuls library conversion, surfacing dev dependencies when importing Trivy results.
v0.38.0 · Feb 2026
· source
· release history
Adds support for fetching CVE details via a custom HTTP URL using -cvedb-url
v0.6.1 · Nov 2018
· source
· release history
Adds -cvedb-type CLI argument to specify the CVE database backend type
v0.6.1 · Nov 2018
· source
· release history
example
Use a custom API to fetch CVE details instead of the default source.$ vuls scan -cvedb-type=http -cvedb-url="https://my-custom-cve-api.com/"
v0.6.1 · Nov 2018
· source
+Oracle and Alpine vulnerability detectionshippedDetects vulnerabilities on Oracle Linux and Alpine Linux operating systems using the vuls2 detection engine.2 releases · first seen Jun 2025▸
Oracle Linux and Alpine Linux now use the vuls2 detection engine (feat!(detector): detect oracle and alpine with vuls2), which may require a compatible vuls2 database and could change detection results on upgrade.
v0.33.0 · Jun 2025
· source
· release history
Detects Oracle Linux and Alpine Linux vulnerabilities via the vuls2 engine.
v0.33.0 · Jun 2025
· source
· release history
+Windows 11 version detection supportshippedDetects vulnerabilities on specific versions of Windows operating systems, including Windows 11 25H2.1 release · first seen Dec 2025▸
Adds detection support for Windows 11 25H2 in the Windows scanner.
v0.36.3 · Dec 2025
· source
· release history
+Library-only dependency scanningshippedDetects vulnerabilities in project dependencies (such as Go modules) via the library subsystem without performing full host or container scans.1 release · first seen Mar 2022▸
+Container-specific vulnerability filteringshippedProvides configuration keys to apply regular expression filters to ignore specific packages within individual containers during scanning.2 releases · first seen Aug 2018▸
Enables per-container cpeNames, owaspDCXMLPath, and ignoreCves configuration keys under [servers.<host>.containers.<name>] in config.toml
v0.5.0 · Aug 2018
· source
· release history
Adds ignorePkgsRegexp config key under [servers.*] for host-level or container-level package filtering using regular expressions
v0.5.0 · Aug 2018
· source
· release history
+Software Bill of Materials (SBOM) generationshippedGenerates standardized SBOM reports in CycloneDX format for supply chain integration.3 releases · 1 other source · first seen Nov 2022▸
Shared capability: SBOM generation
release
vuls scan results now include a PURL (Package URL) field for library scan findings
v0.25.1 · Mar 2024
· source
· release history
Includes dependencies into scan result and CycloneDX for supply chain security on Integration with GitHub Security Alerts
v0.22.1 · Mar 2023
· source
· release history
Adds --cyclonedx flag to enable CycloneDX output format for vulnerability reports
v0.21.0 · Nov 2022
· source
· release history
example
Generate a CycloneDX SBOM-style report for integration with downstream supply chain tools.$ vuls report --cyclonedx -o report.cdx.json
v0.21.0 · Nov 2022
· source
+SPDX JSON exportverifiedExports scan results in SPDX JSON format for use by downstream cyber tools.4 releases · 3 other sources · first seen Aug 2016▸
Shared capability: SPDX SBOM
Also counts toward: JSON data export, S3 export
release
Adds Ubuntu 24.10 (Oracular) as a supported scan target.
v0.28.0 · Dec 2024
· source
· release history
Adds Ubuntu 24.04 (Noble) as a supported distribution for vulnerability detection
v0.25.3 · May 2024
· source
· release history
Generate a JSON report for recently scanned vulnerabilities.$ vuls report -format-json
0.2.0 · Jan 2017
· source
Export scan results to XML for external processing.$ vuls scan -format-xml
0.1.7 · Nov 2016
· source
+Port scanning1 featureNetwork discovery and scanningsince 2021▸
+Nmap host scanningshippedUtilizes Nmap on the host machine to detect open ports during vulnerability scans.2 releases · 1 other source · first seen Jun 2021▸
Shared capability: Port scanning
release
Adds feat(scan): support external port scanner(nmap) in host machine to utilize Nmap for port detection.
v0.15.13 · Jul 2021
· source
· release history
Integrates external nmap port scanner to detect open ports on the host machine during scans
v0.15.12 · Jun 2021
· source
· release history
example
Configure Vuls to use an external nmap binary for host port detection.$ # Add the following to your config.toml [nmap] path = "/usr/bin/nmap"
v0.15.12 · Jun 2021
· source
+macOS vulnerability scanningshippedDetects vulnerabilities on macOS operating systems.1 release · first seen Sep 2023▸
Shared capability: Vulnerability scanning
release
Adds macOS support for vulnerability scanning on Apple operating systems
v0.24.0 · Sep 2023
· source
· release history
+Other / not yet classified29 featuresFeatures we have not matched to a capability yet. A suggested match is marked.▸
+Dependency diff comparisonverifiedCompares lockfile fixtures between Git references to identify dependency changes, with optional internet fetching of lockfile data.10 releases · 7 other sources · first seen Jan 2017▸
release
10 total
Adds pylock.toml (PEP 751) lockfile detection for Python dependency scanning.
v0.39.0 · May 2026
· source
· release history
sles15, sles12sp5, opensuse, and sled added as scan targets
v0.19.4 · Feb 2022
· source
· release history
Adds Fedora platform support for vulnerability scanning
v0.19.3 · Feb 2022
· source
· release history
Adds --diff option to the CLI to enable vulnerability difference reporting in both the TUI and text reports
v0.15.8 · Feb 2021
· source
· release history
Supports -diff on vuls report with existing formats (-format-list, -format-full-text, -format-one-line-text) to output patched item differences
v0.15.8 · Feb 2021
· source
· release history
Enables vuls tui --diff to display resolved (patched) CVEs visually against the previous JSON report
v0.15.8 · Feb 2021
· source
· release history
command line
--workdir — Working directory for temporary files
v0.39.0 · May 2026
· command-line history
--fetch — Download lockfile fixtures from the internet
v0.39.0 · May 2026
· command-line history
--log — Path to write detailed log (default: <workdir>/comparison.log)
v0.39.0 · May 2026
· command-line history
--base — Base Git ref to compare against
v0.39.0 · May 2026
· command-line history
--fixtures — Path to lockfile-fixtures.json
v0.39.0 · May 2026
· command-line history
example
Scan your infrastructure and immediately see which CVEs were resolved since the last run in the terminal UI.$ ./vuls tui --diff
v0.15.8 · Feb 2021
· source
Generate a diff report to identify patched vulnerabilities for integration with CI/CD pipelines or ticketing systems.$ ./vuls report --format-full-text --diff > vuls_diff.txt
v0.15.8 · Feb 2021
· source
+Reporting enrichment and display optionsshippedEnhances scan reports with CWE names, OWASP TOP 10 mappings, mitigation information, and TUI visualization improvements.13 releases · 3 other sources · first seen Aug 2018▸
release
13 total
Includes CWE Top 25 lists for 2023, 2024, and 2025, keeping weakness classifications current.
v0.38.0 · Feb 2026
· source
· release history
Adds cwe-id for category and view in reports
v0.22.1 · Mar 2023
· source
· release history
Adds cwe-id field to category and view output structures for vulnerability reports
v0.23.0-beta · Feb 2023
· source
· release history
Includes the CWE Top 25 2022 list for vulnerability classification
v0.20.0 · Aug 2022
· source
· release history
Introduces capability to parse the OS version directly from the result of a Trivy scan, enabling more accurate reporting without manual input.
v0.19.6 · Apr 2022
· source
· release history
Implements range notion calculation by severity when --no-cvss-score is used and CVSS score is missing
v0.15.4 · Jan 2021
· source
· release history
example
Check if a specific CVE includes CWE classification data in the report output.$ vuls report -format-json | jq '.cves[] | select(.cveId == "CVE-2023-1234") | .cweId'
v0.23.0-beta · Feb 2023
· source
Parse JSON reports to extract exact patch versions for remediation$ jq '.["CVE-2016-9840"].affectedPackages[].fixedIn' report.json
v0.9.2 · Apr 2020
· source
Scan a target and output detected vulnerabilities alongside their IP addresses.$ vuls scan --ips -config config.toml
v0.8.4 · Jul 2019
· source
+End-of-life (EOL) trackingshippedTracks end-of-life status for operating system versions using configurable EOL data.13 releases · first seen Jul 2022▸
release
13 total
Adds EOL data for newly released OS versions via updated GetEOL configuration.
v0.39.3 · Jun 2026
· source
· release history
Updates GetEOL with newly released OS versions for accurate end-of-life tracking.
v0.39.3 · Jun 2026
· source
· release history
Updates end-of-life (EOL) dates for tracked operating systems, improving accuracy of EOL-based risk reporting.
v0.38.1 · Feb 2026
· source
· release history
Updates end-of-life (EOL) data for tracked operating systems, keeping lifecycle-based risk assessments current.
v0.28.1 · Dec 2024
· source
· release history
Adds FreeBSD 14 EOL detection capability
v0.24.7 · Dec 2023
· source
· release history
Adds Windows 11 23H2 to the list of supported operating systems for vulnerability scanning
v0.24.5 · Nov 2023
· source
· release history
+Cloud and container platform scanningshippedsuggestedScans vulnerabilities on specific cloud and container platforms, including Amazon EC2 instances and Docker containers.12 releases · 1 other source · first seen Aug 2016▸
Suggested capability: Container image vulnerability scanning. This is our guess, not confirmed.
release
12 total
Supports Debian 13 (Trixie) in the GOST vulnerability data source.
v0.33.3 · Aug 2025
· source
· release history
Builds arm and 386 binaries alongside amd64 in release artifacts
v0.13.7 · Dec 2020
· source
· release history
Caches WpVulnDB for WordPress plugin detection
v0.9.8 · Jun 2020
· source
· release history
Added trivy parser to parse Trivy scan results
v0.9.8 · Jun 2020
· source
· release history
Adds -wp-ignore-inactive flag to skip inactive plugins or themes during WordPress scans
v0.9.7 · Jun 2020
· source
· release history
Adds suse platform support for vulnerability detection.
v0.4.1 · Oct 2017
· source
· release history
example
Scan SUSE Enterprise Linux hosts during vulnerability assessment.$ vuls scan --os-type suse <target>
v0.4.1 · Oct 2017
· source
+Attack pattern and threat intelligence enrichmentshippedAdds CAPEC, CWE, and MITRE ATT&CK context to vulnerabilities, exposing catalog dictionaries and per-vulnerability threat intelligence references.10 releases · first seen Sep 2016▸
release
10 total
Replaces go-cti with vuls2 attack/CAPEC/CWE datasources; adds ScanResult-level CWEDict, CAPECDict, and ATTACKDict catalog maps and a per-VulnInfo CTIs reference list.
v0.40.0-rc.1 · Jul 2026
· source
· release history
The [cti] config section is removed; CTI data is now sourced from vuls2 rather than go-cti.
v0.40.0-rc.1 · Jul 2026
· source
· release history
Surfaces RedHat CVE Mitigation data into VulnInfo via the vuls2 detector.
v0.39.0 · May 2026
· source
· release history
Adds a DataSources filter to the enrich function, letting users control which data sources are applied during enrichment.
v0.39.0 · May 2026
· source
· release history
Adds verified field to ExploitDB detections, surfacing exploit verification status in results.
v0.34.0 · Sep 2025
· source
· release history
Adds inthewild config key to detect inTheWild proof-of-concept exploits
v0.19.5 · Mar 2022
· source
· release history
+Vulnerability filtering and configuration validationshippedProvides options to ignore specific CVEs or those without scores, and includes commands to validate scan configurations.7 releases · 2 other sources · first seen May 2016▸
Also counts toward: Command-line interface
release
7 total
Supports disablerepo option for yum/dnf package scanning, allowing specific repositories to be excluded during vulnerability detection.
v0.39.2 · May 2026
· source
· release history
Default values for WordPress scanning to be set in config.toml
v0.15.3 · Jan 2021
· source
· release history
The structure of config.toml has been changed; some subcommand flags were removed (see PR #1122)
v0.15.0 · Jan 2021
· source
· release history
feat(redhat) enables ignoring will not fix vulnerabilities on Red Hat systems
v0.8.3 · Jul 2019
· source
· release history
ignoreCveIDs config key to filter specific vulnerabilities
0.1.7 · Nov 2016
· source
· release history
Adds configtest subcommand to validate configuration files before scanning.
0.1.5 · Aug 2016
· source
· release history
docs
Agent-less vulnerability scanner for Linux/FreeBSD/Windows/macOS that detects CVEs across OS packages, libraries, and WordPress.
example
Configure Vuls to skip reporting on will not fix vulnerabilities for Red Hat Enterprise Linux to reduce noise in your reports.$ # Configuration update in config.toml [servers] [servers.<server_name>] # ... other settings ... ignoreWillNotFix = true
v0.8.3 · Jul 2019
· source
+Vendor advisory data sourcesshippedsuggestedPulls detection and enrichment data from Cisco, Fortinet, Palo Alto, VulnCheck, and JVN vendor advisory sources.8 releases · first seen Nov 2018▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
8 total
Expands Fortinet CSAF vulnerability data with three new RangeType values: fortinet-fortisiem_cloud, fortinet-fortimonitoronsight, and fortinet-fortipam_chrome_extension.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
v0.42.0 · Oct 2026
· source
· release history
Routes Cisco, Fortinet, Palo Alto, VulnCheck, and JVN data sources through vuls2 for detection and enrichment.
v0.40.0-rc.1 · Jul 2026
· source
· release history
Uses JPCERT-AT reference_titles as JVN alert titles for more descriptive reporting.
v0.40.0-rc.1 · Jul 2026
· source
· release history
Supports VulnCheck as a data source via go-cve-dictionary integration.
v0.34.0 · Sep 2025
· source
· release history
Enables ingestion of the fortinet CVE data feed via the detector engine
v0.24.0 · Sep 2023
· source
· release history
The go-kev schema has changed in v0.1.0; existing Vuls databases must be recreated or scans may fail.
v0.19.1 · Jan 2022
· source
· release history
+Scan transparency and evaluation warningsshippedsuggestedSurfaces evaluation warnings from the vuls2 detector so operators can understand why specific detection decisions were made.4 releases · 2 other sources · first seen Apr 2019▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
Surfaces evaluation warnings from the vuls2 detector for improved scan transparency.
v0.40.0-rc.1 · Jul 2026
· source
· release history
Adds [servers.<name>.wordpress] configuration section in config.toml with keys cmdPath, osUser, docRoot, wpVulnDBToken, and ignoreInactive to define WordPress scan targets.
v0.7.0 · Apr 2019
· source
· release history
Adds integration with [WPVulnDB.com](https://wpvulndb.com/api) to detect vulnerabilities for identified WordPress components during the scan.
v0.7.0 · Apr 2019
· source
· release history
Enables vuls scan <server-name> to collect WordPress Core, plugin, and theme versions via wp-cli when a WordPress server config is present.
v0.7.0 · Apr 2019
· source
· release history
example
Run a scan on the configured WordPress server to detect core and extension vulnerabilities.$ vuls scan my-wordpress
v0.7.0 · Apr 2019
· source
Configure a server section in config.toml to target a specific WordPress installation, pointing Vuls to the WP-CLI binary and providing your API token.$ [servers.my-wordpress] user = "root" host = "10.10.10.10" port = "22" [servers.my-wordpress.wordpress] cmdPath = "/usr/local/bin/wp" osUser = "wordpress" docRoot = "/var/www/html" wpVulnDBToken =…
v0.7.0 · Apr 2019
· source
+CTI integration via go-kevshippedsuggestedIncorporates cyber threat intelligence and exploit status from the Kev database to enrich vulnerability detection.6 releases · first seen Jan 2022▸
Suggested capability: Vulnerability prioritization. This is our guess, not confirmed.
release
Adds VulnCheck KEV (Known Exploited Vulnerabilities) data to the vulnerability model.
v0.27.0 · Oct 2024
· source
· release history
VulnCheck KEV fields are added to the models (feat!(models): add vulncheck kev) — downstream consumers parsing Vuls output JSON may need to handle the new fields.
v0.27.0 · Oct 2024
· source
· release history
Mod updates ExploitDB sources and adds more URLs
v0.22.1 · Mar 2023
· source
· release history
Updates the ExploitDB detection engine (detector/exploitdb) with additional external URLs for more complete threat intelligence coverage
v0.23.0-beta · Feb 2023
· source
· release history
The go-kev schema has changed in v0.1.0; existing Vuls databases must be recreated or scans may fail.
v0.19.1 · Jan 2022
· source
· release history
Updates the go-kev dependency to v0.1.0, requiring a database recreation due to schema changes
v0.19.1 · Jan 2022
· source
· release history
+MITRE CVE enrichmentshippedsuggestedEnriches vulnerabilities with MITRE CVE v5 data via the vuls2 pipeline.5 releases · first seen Jun 2019▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
Enriches MITRE CVE v5 data via the vuls2 pipeline.
v0.40.0-rc.1 · Jul 2026
· source
· release history
Adds MITRE as a new CVE content source via go-cve-dictionary.
v0.27.0 · Oct 2024
· source
· release history
Adds new trivy:azure CVE content type for Azure-specific Trivy findings.
v0.27.0 · Oct 2024
· source
· release history
Supports scanning for vulnerabilities in the Amazon Linux 2 Extra Repository
v0.20.0 · Aug 2022
· source
· release history
Add type="pseudo" in [servers.image] to enable Container Image Scan for targets like GCR or local images.
v0.8.0 · Jun 2019
· source
· release history
+Scan result storage integrationshippedExports scan findings directly to cloud storage services like Amazon S3 and Azure Blob Storage.4 releases · 1 other source · first seen Aug 2016▸
release
reporter/s3 now supports Minio as a storage backend for vulnerability reports
v0.26.0 · Jun 2024
· source
· release history
Adds Telegram as a notification destination via new -to-telegram flag
v0.6.2 · Jan 2019
· source
· release history
Adds alerts array to scan result JSON output for structured alert data
v0.6.2 · Jan 2019
· source
· release history
Adds the -report-azure-blob option to send scan results directly to Azure Blob Storage.
0.1.5 · Aug 2016
· source
· release history
example
Send vulnerability scan alerts to a Telegram channel instead of email.$ vuls report -to-telegram <bot_token> <chat_id>
v0.6.2 · Jan 2019
· source
+Windows host version scanningshippedsuggestedDetects vulnerabilities on specific versions of Windows operating systems including recent updates.4 releases · first seen Dec 2024▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
Supports Windows vulnerability detection using the vuls2 detector engine.
v0.39.3 · Jun 2026
· source
· release history
Adds vendor field for Windows packages in the scanner, enriching package metadata for Windows targets.
v0.38.0 · Feb 2026
· source
· release history
Supports scanning Windows Server 2025 and Windows Server 2022 23H2.
v0.28.0 · Dec 2024
· source
· release history
+Network device CPE mappingshippedsuggestedMaps SNMP OIDs to CPE names for network devices and integrates them into the scanning pipeline.4 releases · first seen Apr 2023▸
Suggested capability: Attack surface inventory. This is our guess, not confirmed.
Also counts toward: CI/CD pipeline integration, Command-line interface
release
contrib/fvuls gains new subcommands for retrieving network device CPE information via snmp2cpe and uploading it to the Fvuls server.
v0.23.4 · Sep 2023
· source
· release history
contrib/snmp2cpe now includes additional Fortinet products in its CPE mapping data.
v0.23.4 · Sep 2023
· source
· release history
Adds the snmp2cpe subcommand in the contrib directory to map SNMP OIDs to CPE names
v0.23.0 · Apr 2023
· source
· release history
Enables Windows CPE detection in the CI pipeline (snmp2cpe integration)
v0.23.0 · Apr 2023
· source
· release history
+RedHat family vulnerability detectionshippedsuggestedDetects vulnerabilities on RedHat, CentOS, AlmaLinux, and Rocky Linux operating systems using the vuls2 detection engine.3 releases · first seen Feb 2025▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
Detects Debian vulnerabilities via the vuls2 detector.
v0.39.0 · May 2026
· source
· release history
Adds Amazon Linux support to the vuls2 detector backend.
v0.38.6 · Mar 2026
· source
· release history
Enables the vuls2 detection engine for RedHat, CentOS, AlmaLinux, and Rocky Linux vulnerability detection.
v0.29.0 · Feb 2025
· source
· release history
+Ubuntu vulnerability detectionshippedsuggestedDetects vulnerabilities on Ubuntu operating systems using the vuls2 detector engine.2 releases · first seen Jun 2025▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
Adds Ubuntu 26.04 as a supported OS target.
v0.39.0 · May 2026
· source
· release history
When scanning with the Trivy integration, the server name no longer includes the image tag — any pipeline, report, or downstream tooling that matched on the tag-suffixed server name will need to be updated.
v0.33.1 · Jun 2025
· source
· release history
+Library-only scanning modeshippedsuggestedEnables a specific scanning mode focused exclusively on library dependencies via CLI flag.2 releases · first seen Sep 2021▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
Also counts toward: Command-line interface
release
Adds dev flag to library scanning so development dependencies are tracked and reported separately from production packages.
v0.38.0 · Feb 2026
· source
· release history
Adds --library CLI argument to enable library-only vulnerability scanning.
v0.16.0 · Sep 2021
· source
· release history
+Fedora vulnerability detectionshippedsuggestedDetects vulnerabilities on Fedora operating systems using the vuls2 detector engine.2 releases · first seen Sep 2025▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
Adds Fedora vulnerability detection powered by the vuls2 detector engine.
v0.35.0 · Sep 2025
· source
· release history
Fedora detection now uses the vuls2 detector (feat! commit a6bee18); setups relying on the previous Fedora detection path may behave differently on upgrade.
v0.35.0 · Sep 2025
· source
· release history
+Operating system end-of-life data updatesshippedTracks end-of-life status for additional operating system versions, including RHEL 10, via configurable EOL data sources.2 releases · first seen Jun 2025▸
release
Adds EOL date tracking for additional operating systems.
v0.33.3 · Aug 2025
· source
· release history
Adds RHEL 10 end-of-life data to OS metadata.
v0.33.0 · Jun 2025
· source
· release history
+RPM source attributionshippedIncludes source RPM attribution in scan results via updated query formats.2 releases · first seen Dec 2024▸
release
The RPM scanner query format has changed to add sourcerpm; existing scan results or integrations parsing the raw RPM query output may receive differently structured data.
v0.28.0 · Dec 2024
· source
· release history
Changes RPM query format to include sourcerpm, enabling source-package attribution in scan results.
v0.28.0 · Dec 2024
· source
· release history
+Go dependency scanningshippedsuggestedDetects vulnerabilities in Go project dependencies by analyzing go.sum files.2 releases · first seen Jun 2021▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
Adds feat(lib): support of Go (go.sum) scan to detect vulnerabilities in Go project dependencies.
v0.15.13 · Jul 2021
· source
· release history
Adds go.sum support for detecting vulnerabilities in Go library dependencies
v0.15.12 · Jun 2021
· source
· release history
+False positive suppressionshippedFilters rejected and withdrawn CPE vulnerabilities from scan results to reduce false positives.1 release · first seen Jul 2026▸
release
Ignores rejected and withdrawn CPE vulnerabilities to reduce false positives.
v0.40.0-rc.1 · Jul 2026
· source
· release history
+Vulnerability database integrity verificationshippedSaves and tracks the digest of the vulnerability database to ensure data integrity.1 release · first seen Sep 2025▸
release
Saves and tracks the digest of the vuls2 vulnerability database for integrity verification.
v0.35.0 · Sep 2025
· source
· release history
+Exploit verification status enrichmentshippedsuggestedEnriches scan results with exploit verification status from ExploitDB sources.1 release · first seen Sep 2025▸
Suggested capability: Vulnerability prioritization. This is our guess, not confirmed.
release
Adds verified field to ExploitDB detections, surfacing exploit verification status in results.
v0.34.0 · Sep 2025
· source
· release history
+SNMP device port targetingshippedsuggestedAllows scanning of SNMP devices on non-default ports.1 release · first seen Dec 2024▸
Suggested capability: Attack surface inventory. This is our guess, not confirmed.
release
Adds --port/-P option to contrib/snmp2cpe for targeting SNMP devices on non-default ports.
v0.28.0 · Dec 2024
· source
· release history
+Alpine source package detectionshippedsuggestedUses source packages instead of binary packages for vulnerability detection on Alpine Linux.1 release · first seen Oct 2024▸
Suggested capability: Vulnerability database matching. This is our guess, not confirmed.
release
Alpine detection now uses source packages instead of binary packages (fix!(alpine): use source package for detection) — existing Alpine scan results may change on upgrade.
v0.27.0 · Oct 2024
· source
· release history
+SMTP notification TLS bypassshippedAllows SMTP alerts to be sent to mail servers with self-signed or invalid certificates.1 other source · first seen May 2024▸
example
Send SMTP alerts even when the mail server uses a self-signed or invalid certificate.$ vuls report --config=config.toml --tls-insecure-smtp
v0.25.3 · May 2024
· source
+Network-based target selectionshippedsuggestedAllows scanning of targets by specifying CIDR blocks in the configuration rather than explicit host lists.1 release · first seen Jul 2022▸
Suggested capability: Attack surface inventory. This is our guess, not confirmed.
release
config.toml gains a new cidr field in the server block for network-based target selection
v0.19.8 · Jul 2022
· source
· release history
+Structured JSON log outputshippedProvides a CLI option to direct scanning logs into a structured JSON format.1 release · first seen Oct 2021▸
release
Adds --log-json flag to enable structured JSON log output
v0.18.1 · Oct 2021
· source
· release history
+Google Chat reporting integrationshippedSends scan reports directly to Google Chat workspaces.1 release · first seen Jul 2021▸
release
Adds Feat report googlechat integration to send scan reports to Google Chat.
v0.15.13 · Jul 2021
· source
· release history
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
View
Source
No command matches.
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian time to a maintainer’s first reply
Nine scores for Vuls, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Vuls puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Future Architect's home page and 10 more pages as they looked each month from October 2021 to October 2026: 28 renders, 0 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
Show
85 entries
No entries match these filters.
October 20261
September 20262
July 20261
June 20262
May 20262
March 20261
February 20262
December 20252
September 20252
August 20251
June 20252
March 20251
February 20251
December 20242
October 20241
June 20241
May 20242
March 20242
December 20231
November 20231
October 20231
September 20232
July 20231
May 20231
April 20231
March 20231
February 20231
November 20221
August 20221
July 20221
April 20221
March 20221
February 20222
January 20221
November 20211
October 20211
September 20212
July 20211
June 20211
April 20211
February 20211
January 20214
December 20202
October 20201
August 20201
July 20201
June 20202
May 20201
April 20201
September 20191
July 20192
June 20192
April 20191
February 20191
January 20191
November 20181
August 20181
October 20171
August 20171
March 20171
January 20171
November 20161
September 20161
August 20161
May 20161
Project health
Issue, contributor and maintainer activity in future-architect/vuls, 2023-12 – 2026-11,
as of 2026-11-03. Twelve-month figures first; the trend lines run
the whole window.
Contributors8−2 vs prior 12 months
Maintainers2+0 joined · −0 left, last 12 months
Bus factor2committers behind half the commits
Community-filed68%of issues opened, last 12 months
Median time to close4.6 daysfirst maintainer reply 2.8 days
Open backlog68of 669 issues ever filed
Issues opened / month2 · 0communitymaintainers
Open backlog68
Contributors / month0
Commits / month0
Stars12,278
Issue themes, last 12 months
bugs 25%
features 5%
questions 14%
other 56%
Counts from the project's public repository and git history; no individuals
are identified. Maintainers are the committers covering 80% of the last year's
commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.
None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can
follow every release here.