> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/artifact-registry/3.0/artifacts/re-evaluate-a-version.md).

# Re-evaluate a version against current policy

Re-run Dependency Firewall policy evaluation against a cached artifact version, without pulling or pushing again, to get an up-to-date verdict.

When a dependency is first fetched through an upstream proxy registry, Harness evaluates it against your Dependency Firewall policy sets and assigns a verdict: **Passed**, **Warning**, or **Blocked**. That verdict reflects the state of your policies and threat intelligence at that moment.

Re-evaluation lets you re-run that check without fetching or pushing the package again. Use it when the picture has changed: a policy threshold was tightened, a CVE was added or patched in the threat intelligence database, or a Package Age cooldown period has passed.

## Before you begin

Re-evaluation is available only on **upstream proxy registries with Dependency Firewall enabled**. It does not apply to standard registries; artifacts you push directly to a registry are not evaluated by the Dependency Firewall.

To confirm Dependency Firewall is enabled on your proxy, go to [Dependency Firewall overview](https://developer.harness.io/artifact-registry/3.0/dependency-firewall/overview.md).

## When to re-evaluate

| Situation                                                                       | Why re-evaluate helps                                                                 |
| ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| You updated a policy threshold                                                  | Re-evaluation applies the new threshold immediately without waiting for the next pull |
| A CVE was patched in a new upstream release and you updated the dependency      | Confirms the cached version is now clean without re-pulling                           |
| A Package Age cooldown window has passed                                        | Checks whether the package now passes the age policy                                  |
| A previously Blocked version was present before Dependency Firewall was enabled | Gets an accurate current verdict for versions that pre-date the firewall              |
| Threat intelligence data has refreshed                                          | Clears a false positive that was resolved in an updated advisory database             |

## Re-evaluate from the Artifacts list

The quickest way to re-evaluate a single version:

1. In the navigation menu, select **Artifacts**.
2. Find the artifact in an upstream proxy registry. The **Evaluation Status** column shows the current verdict.
3. Click **Show more actions** (**⋮**) on the row.
4. Select **Re-Evaluate**.

The verdict updates in real time. If the package now passes all policy sets, the **Evaluation Status** changes to **Passed** and the version moves off the Violations tab.

## Re-evaluate from the Versions tab

When you are already inspecting an artifact's versions:

1. Open the artifact.
2. Select the **Versions** tab.
3. Click **Show more actions** (**⋮**) next to the version you want to check.
4. Select **Re-Evaluate**.

The same real-time update applies.

## Re-evaluate from the Violations tab

If you are reviewing violations in the Dependency Firewall dashboard, you can re-evaluate directly from the Details sidebar without navigating back to the artifact:

1. Go to **Dependency Firewall > Violations**.
2. Select a row to open the Details sidebar.
3. At the bottom of the sidebar, select **Re-Evaluate**.

Go to [View and triage violations](https://developer.harness.io/artifact-registry/3.0/dependency-firewall/view-and-triage-violations.md) for the full violations workflow.

## What re-evaluation checks

Re-evaluation runs the version through all policy sets currently attached to the upstream proxy registry. This includes:

* **CVSS Threshold**: compares the highest CVE score against your configured maximum.
* **OSS Risk Level**: checks the package's overall risk rating from the threat intelligence database.
* **Malicious Package**: checks whether the package has been flagged as malicious in any source.
* **Package Age**: checks whether the package was published within the configured cooldown window.

Go to [Built-in policy templates](https://developer.harness.io/artifact-registry/3.0/dependency-firewall/built-in-policy-templates.md) for details on each policy type.

## What re-evaluation does not do

* **It does not re-trigger a vulnerability scan**. Security scanning (Aqua Trivy or Grype) runs at push time and is separate from Dependency Firewall policy evaluation. To get updated scan results for a container image, re-push the image.
* **It does not apply to standard registries**. Only upstream proxy registries evaluate Dependency Firewall policies.
* **It does not change a Blocked verdict permanently**. If the package still fails a policy after re-evaluation, the verdict stays Blocked. Use an exception request for temporary access while you work on the underlying issue. Go to [Request an exception](https://developer.harness.io/artifact-registry/3.0/dependency-firewall/request-an-exception.md).

## Troubleshooting

<details>

<summary>Re-Evaluate is not in the row menu</summary>

Confirm you are viewing an upstream proxy registry. The Re-Evaluate option only appears on versions cached from an upstream source. Also confirm Dependency Firewall is enabled on the upstream proxy. Go to [Dependency Firewall overview](https://developer.harness.io/artifact-registry/3.0/dependency-firewall/overview.md) to check.

</details>

<details>

<summary>The verdict did not change after re-evaluation</summary>

Re-evaluation applies the current policy rules and threat intelligence. If the verdict is unchanged, the package still fails at least one policy under the current configuration. Open the Details sidebar on the Violations tab to see which specific policy is triggering, then decide whether to update the dependency, adjust the policy threshold, or submit an exception request.

</details>

<details>

<summary>A version shows Passed after re-evaluation but is still blocked in my build</summary>

Re-evaluation updates the stored verdict but does not automatically release a version that was previously cached as Blocked. If the version was quarantined, go to [Quarantine](https://developer.harness.io/artifact-registry/3.0/security-and-compliance/quarantine.md) to release it manually. If it was never cached, your build tool needs to pull it fresh through the upstream proxy; now that it passes, the pull should succeed.

</details>

## Next steps

* [View and triage violations](https://developer.harness.io/artifact-registry/3.0/dependency-firewall/view-and-triage-violations.md): investigate packages that did not pass after re-evaluation
* [Request an exception](https://developer.harness.io/artifact-registry/3.0/dependency-firewall/request-an-exception.md): get temporary access to a version that still fails
* [Built-in policy templates](https://developer.harness.io/artifact-registry/3.0/dependency-firewall/built-in-policy-templates.md): adjust thresholds that are producing unexpected results

{% @harness-feedback/feedback %}
