Blacklist policy

Prevents blacklisted packages and package versions from being added to a registry

Use the Blacklist policy to prevent specific packages or package versions from being added to a registry. This is done by creating a blacklist definition list per registry where the policy has been enabled.

The policy works the opposite of the Whitelist policy.

Each blacklist is linked to a specific registry, allowing custom lists for different scenarios.

The policy does not prevent dependencies of blacklisted packages from being added to the registry (unless you have also explicitly added these to the blacklist).

Blacklist policy settings

The Blacklist settings allow users to define and store their specific composition of packages and versions that should be prevented from being added to a registry.

Blacklist definitions can consist of either a package name, a specific package versions or ranges of package versions:

Blacklist definitions

The blacklist definition is validated while typing and the result is shown as Valid or Invalid

To store any changes and exit the settings, simply click on the Save configuration button.

Use cases

  • Block all versions of packages - Blacklist all versions of a package by adding a package name definition to the blacklist without specifying any version. Useful when making sure certain packages (regardless of versions) are not added to the registry and therefore not available from the registry.
  • Block specific package versions or ranges - Blacklist a specific package version or range of versions. Allowing users to make sure specific versions are not added to the registry.