Appearance
SEC459 / MD-JS-PACKAGE-CONFIG-HTTP-REGISTRY
SEC459 flags AI-native markdown when an npm config set, pnpm config set, or yarn config set command points registry at http://....
Why It Matters
Changing package-manager config to an insecure registry makes later installs trust an unencrypted dependency source. In shared AI-native instructions, that turns a persistent supply-chain downgrade into copy-pastable setup guidance.
What Triggers It
- AI-native markdown surface
- the same parsed markdown region contains:
npm config setpnpm config set- or
yarn config set
- the same region also contains one of:
registry http://registry=http://
The finding points to http://.
What Does Not Trigger It
https://registry config- install-time
--registry http://...examples, because those are covered bySEC450 - unrelated prose that mentions
http://without a matching package-manager config command
Example
Bad:
bash
npm config set registry http://registry.example.test/Better:
bash
npm config set registry https://registry.example.test/Remediation
Replace the insecure http:// registry config with a normal TLS-verified https:// source.