[BUG] Using `--install-strategy = "linked"` ignores the `strict-ssl` config

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

Running npm i with the following configuration:

Global configuration since we're running behind a restrictive firewall:

npm config set strict-ssl false

Config file in our project .npmrc:

install-strategy = "linked"

The command output gives us a c:

npm error: Error: self-signed certificate in certificate chain
///
npm error:  code: 'SELF_SIGNED_CERT_IN_CHAIN'

Running the install script using the default strategy works fine (no cert error)

Expected Behavior

The strict-ssl config param should work the same way no matter which install-strategy is selected

Steps To Reproduce

1. Install packages with self-signed cetificates
2. Set strict-ssl to false
3. Set install-strategy to linked
4. Run npm install
5. Get error SELF_SIGNED_CERT_IN_CHAIN

Environment

• npm: 11.4.1
• Node.js: 20.18.1
• OS Name: Windows 11
• npm config:

cafile = // File path
prefix = // Appdata path
registry = // Company registry
strict-ssl = false
unsafe-perm = true

Reproduce the installation with a project .npmrc containing install-strategy="linked" and strict-ssl=false, then compare it with the default strategy. Trace the linked installation path and verify that npm install accepts the self-signed certificate when strict-ssl is disabled, while preserving the existing default-strategy behavior.