Appearance
SEC454 / MD-NPM-HTTP-SOURCE
SEC454 flags AI-native markdown when an npm, pnpm, yarn, or bun install example fetches a package directly from http://....
Why It Matters
A direct http:// package source removes transport integrity from the package payload itself. In shared AI-native instructions, that turns an insecure supply-chain fetch into copy-pastable setup guidance.
Trigger Shape
The rule triggers only when all of these are true:
- the file is an AI-native markdown instruction surface
- a parsed markdown region contains
npm install,npm i,pnpm install,pnpm add,yarn add, orbun add - the same region also contains a direct
http://package source argument
Clean Cases
These stay clean:
- package install examples that fetch the source over
https:// --registry http://...forms, because those are covered bySEC450- unrelated
http://text outside a matching install form
Example Trigger
bash
npm install http://registry.example.test/demo.tgzSafer Example
bash
npm install https://registry.example.test/demo.tgzHow To Fix
Replace the insecure direct http:// source with a normal TLS-verified https:// source.