# dependency-check mit Homebrew, scoop installieren

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

## Installation

```sh
sudo av install brew:dependency-check
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install dependency-check
```

  Evidenz: local Homebrew formula metadata

### Windows

- Scoop (92%):

```sh
scoop install main/dependency-check
```

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

## Paketfakten

- **Paketschlüssel:** brew:dependency-check
- **Paketmanager:** Homebrew
- **Version:** 12.2.2
- **Quellzusammenfassung:** OWASP dependency-check
- **Homepage:** <https://owasp.org/www-project-dependency-check/>
- **Repository:** <https://github.com/dependency-check/DependencyCheck>
- **Zuletzt aktualisiert:** 2026-06-23T11:38:03-04:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- dependency-check (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 12.2.2
## 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

- <https://owasp.org/www-project-dependency-check/>
- <https://github.com/dependency-check/DependencyCheck#readme>
- <https://dependency-check.github.io/DependencyCheck/dependency-check-cli/>
- <https://api.github.com/repos/dependency-check/DependencyCheck>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

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

## Andere Paketmanager-Einträge

- Scoop - main/dependency-check: normalized package name match | Scoop official bucket manifest trees: bucket/dependency-check.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/dependency-check.yml](https://github.com/mxcl/pkgdb/blob/main/combined/dependency-check.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph