Step 1: Identify npm Registry Timeout Symptoms

Check the Code Insight agent log (agent.log) for repeated timeout warnings similar to the following:

WARN c.f.c.util.HttpUtils Http URL connection time out: https://registry.npmjs.org/@jupyterlab%2fapplication

If you see many timeout entries for npm packages, Code Insight is attempting to resolve transitive Node.js dependencies through the npm registry.

Step 2: Confirm That "node_modules" Directory Exists in the Image

Verify whether the Docker image includes the node_modules directory. This is common when:

• Node.js dependencies are bundled with the application.
• Dependencies are installed during the container build process.
• Node.js packages are included in the base image or OS layer.

When node_modules is present, all required dependencies and their package.json files are already present in the container.

Step 3: Update the Dependency Setting in the Scan Profile

For Docker images that already include Node.js dependencies, avoid using a scan profile that resolves transitive dependencies. Instead, configure the scan profile dependency setting to one of the following:

• No dependencies (recommended best practice for container scans).
• First‑level dependencies only.

These settings scan artifacts directly from the container, avoiding recursive calls to the npm registry.

NOTE: Scan profile names (for example, “Basic”) can be customized. Always verify the dependency setting configured in the profile rather than relying on the profile name alone.

Step 4: Re‑Run the Docker Scan

Re‑run the Code Insight remote Docker scan using the updated scan profile. The scan completes much faster because Code Insight no longer attempts to resolve npm transitive dependencies over the network.

After updating the scan profile dependency setting:

• Docker image scans complete in a reasonable amount of time.
• npm registry timeout warnings no longer appear in the agent logs.
• The generated inventory and SBOM remain accurate for container scans.

https://docs.codeinsight.revenera.com/installation-guide/configure/managing-scan-profiles/description-of-the-scan-profile-settings