Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%

brew install dependency-check

local Homebrew formula metadata

Windows

Scoopverifiziert · 92%

scoop install main/dependency-check

Scoop official bucket manifest trees · bucket/dependency-check.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

OWASP dependency-check

Projektlinks

Befehle und Aliase

dependency-check

Verlauf

Projektgeschichte und Nutzung

OWASP Dependency-Check is a long-running software composition analysis tool that detects publicly disclosed vulnerabilities in project dependencies. It maps dependencies to CPE identifiers and reports related CVE entries, putting vulnerability intelligence into command-line, build-tool, and CI workflows.

Projektgeschichte

The official GitHub repository dates to 2012, and the OWASP project page describes Dependency-Check as an SCA tool suite for identifying dependencies and checking them against known public vulnerabilities. The project grew from a Java command-line scanner into a family of integrations for Maven, Gradle, Ant, Jenkins, and other build environments.

The README and generated CLI documentation show a project that has adapted to changes in vulnerability data distribution. Modern releases use the NVD API, recommend an NVD API key for acceptable update speed, and document analyzer behavior for ecosystems such as .NET, Go, npm, pnpm, yarn, Ruby, Maven, and Gradle.

Adoptionsgeschichte

Dependency-Check became a standard OWASP-branded option for teams that wanted vulnerability scanning without adopting a commercial SCA platform. Its availability as a standalone CLI, Maven plugin, Gradle plugin, Ant task, Jenkins plugin, GitHub releases, and Homebrew formula helped it travel through Java shops, CI servers, and security baselines.

Wie es verwendet wird

The common command-line shape is `dependency-check --project <name> --scan <path> --out <dir>`, producing reports that list dependencies, matching CPEs, and CVEs. Build integrations usually wire the same engine into verification phases or CI jobs, while larger installations may use a shared data directory or centralized database to avoid repeatedly downloading vulnerability data.

Warum Paket-Nerds sich dafür interessieren

Package nerds care about Dependency-Check because it sits at the messy join between language package metadata and vulnerability databases. Its CPE matching, analyzer requirements, NVD API migration, local data cache, and plugin ecosystem are all examples of the hard operational details behind a simple phrase like dependency vulnerability scan.

Zeitleiste

2012: Official DependencyCheck repository created.
2012: OWASP Dependency-Check copyright period begins in generated project documentation.
2024: Version 9.0.0 and later moved from NVD data feeds to the NVD API.
2026: CLI documentation published for version 12.2.2.

Related projects

Related official surfaces include dependency-check-core, dependency-check-cli, dependency-check-maven, dependency-check-gradle, dependency-check-ant, and the Jenkins plugin.

Quellen

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

narrow executable package without higher-risk signals

Signale

metadata:no-higher-risk-signals

Installationsverhalten

In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
Homebrew-Bottle-Metadaten sind für 1 Plattformziele verfügbar.
Installiert mit 1 Laufzeitabhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

Befehl	Art	Sichtbarkeit	Hinweis
`dependency-check`	cli	globales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25

Manager-Version12.2.2

Manager aktualisiert2026-06-23

lokale DatenOK

Upstreamnot checked

neueste erkannte Versionnicht erkannt

https://github.com/dependency-check/DependencyCheck

InfoNo cached GitHub release or tag data was available.https://github.com/dependency-check/DependencyChecknone Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüssel	brew:dependency-check
Version	12.2.2
Paketmanager	Homebrew
Paketmanager-Seite	https://formulae.brew.sh/formula/dependency-check
Homepage	https://owasp.org/www-project-dependency-check/
Repository	https://github.com/dependency-check/DependencyCheck
Upstream-Dokumentation	https://github.com/dependency-check/DependencyCheck#readme
Lizenz	Apache-2.0
Quellarchiv	https://github.com/dependency-check/DependencyCheck/releases/download/v12.2.2/dependency-check-12.2.2-release.zip
Zuletzt aktualisiert	2026-06-23T11:38:03-04:00
Pulse	updated
Abhängigkeiten	openjdk
Bottle	verfügbar (auf all)
Homebrew post-install	nicht definiert
Dienst	keiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	dependency-check
Version Scheme	0
Revision	0
Head Version	HEAD
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	head stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Scoop95%

main/dependency-check

scoop install main/dependency-check

normalized package name match
Abgeglichen nach: Dependency Check

Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/dependency-check.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Combined YAML source

View the package source record on GitHub.

combined/dependency-check.yml

Verwendete Quellen

Geiger risk classifier
Nucleus package database
av.db category and tag curation
cross-ecosystem install command graph
curated package history
external package-manager database matches
package relationship graph
package version freshness
package-page enrichment

dependency-check mit Homebrew, scoop installieren