Azure DevOps Artifacts

Route your registry traffic through Aikido's registry proxy by configuring Azure DevOps Artifacts as an intermediary. Artifacts pulls packages from Aikido instead of the public registries, so every package your team installs is checked for malware, age restrictions, and known vulnerabilities.

Azure DevOps Artifacts only supports custom upstream sources for NPM.

1

Get your Aikido proxy URL

Go to Settings > Registry Proxy, select NPM, and copy the upstream proxy URL.

2

Add Aikido as an upstream source

1. In Azure DevOps Project, go to Artifacts and open your feed.

2. Click Feed settings (the gear icon).

3. Go to the Upstream sources tab and click Add upstream.

4. Select Public source as the source type

5. Fill in the configuration:

   • Public source: Custom registry

   • Public source URL: paste your Aikido proxy URL from step 1

   • Package type: npm

   • Upstream source name: aikido

6. Enter @aikidosec/mcp in the Validation field and click Validate to confirm the connection works.

7. Click Validate, and then Add.

8. Click Save

3

Remove the default npm upstream source

To ensure all npm traffic goes through Aikido instead of the public registry directly:

1. In the same Upstream sources tab, find the existing npmjs upstream source.

2. Click the delete icon next to it and confirm removal.

4

Configure Developer Machines to use Azure Artifacts

Point each developer's npm client at the Artifacts feed. See Microsoft's documentation for the exact steps:

Connect to a feed as a developer (npm)

5

(Optional) Block the public registry with Device Protection

Once Artifacts is in place, developers can still bypass it by pointing npm directly at the public registry. Deploy Aikido Device Protection to enforce that all traffic goes through your private registry.

Block Public Package Registries