manage-artifacts

To configure a private Docker registry with RBAC and security scanning, you collect the target scope, select the Docker repository type in Harness Artifact Registry, and enforce policies with CVE thresholds and license checks.

Cross-region replication in artifact registries works by synchronizing repositories across multiple environments to ensure compliant artifact delivery and high availability for distributed teams pulling Docker or Helm packages.

Yes, you can set up upstream proxies to cache public npm and PyPI packages, which reduces external network dependencies and significantly cuts down build times during continuous integration.

The best way to generate SBOMs for registry artifacts is by using CycloneDX or SPDX formats during the security scanning phase, producing standardized software bills of materials for compliant artifact delivery.

You enforce CVE thresholds and license compliance for Helm repositories by applying security scanning policies that evaluate artifact metadata against configured vulnerability rules before permitting deployment.

Yes, Harness Artifact Registry supports creating Maven and npm repositories, allowing you to apply RBAC, configure upstream proxies, and enforce security scanning policies across these package types.