> For the complete documentation index, see [llms.txt](https://docs.nullify.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nullify.ai/configuration/configuration-dependencies.md).

# Dependency Configuration

## Overview

Software Composition Analysis (SCA) covers both **dependencies** and **container** findings. Dependency findings are configured from the Nullify dashboard — there is no checked-in config file. Query them with `GET /sca/dependencies/findings` (and `/detailed`, `/preview`); fetch or update a single finding with `GET,PATCH /sca/dependencies/findings/{findingId}`.

## Autofix

Nullify drafts dependency upgrade pull requests automatically. Autofix is enabled per tenant; Manager campaign planning currently applies these PR-volume limits:

* **3** open Nullify pull requests per repository at a time.
* **5** new pull requests per remediation plan.

## Pull request gate

Whether a dependency finding can fail CI is controlled from **Settings → Repository scans** (legacy **Configure → Pull Requests**) or `PUT /admin/pr-gate-settings`, including the rule that blocks a new CVE at or above a CVSS cutoff without AI triage. See [Repository Scans](https://docs.nullify.ai/configuration/configuration-pull-requests.md).

## Licenses and release cooldown

**Settings → Repository scans → Dependencies** (`GET`/`PUT /scpm/settings`) sets the supply-chain policy for dependencies that pull requests add or upgrade:

* **Allowed licenses** — comma-separated SPDX identifiers. An empty list uses the default restrictions on copyleft and source-available licenses; dependencies outside the list are reported for triage.
* **Enable cooldown** (on by default) — flag a dependency whose version was published more recently than the cooldown window. **Report only** shows cooldown findings on the check without failing it.
* **Default window (days)** — 0 to 365, 7 by default, with optional per-ecosystem overrides for npm, PyPI, Go, Maven, NuGet, RubyGems and Cargo.

See [Dependency cooldowns](https://docs.nullify.ai/capabilities/scpm.md#dependency-cooldowns) for how these findings are raised.

## Ignore findings

Suppress a known advisory or defer remediation by allowlisting the specific finding — per-finding from the dashboard or via the API:

```
POST /sca/dependencies/findings/{findingId}/allowlist
```

Request body:

```json
{
  "allowlistReason": "Library only used in test harnesses",
  "allowlistType": "UserAssumeRisk"
}
```

`allowlistType` is one of `AI`, `UserFixed`, `UserAssumeRisk`, `UserFalsePositive`, or `UserOther`.

Use campaigns to track deferred work and prevent forgotten exceptions. Container hardening findings are configured separately — see [Configuration – Containers](https://docs.nullify.ai/configuration/configuration-containers.md).

The documented limits of 3 open PRs per repository and 5 new PRs per plan apply to Manager campaign planning. They are not a global cap on manually triggered dashboard, API, or CLI autofix requests.
