lintai docs

Appearance

Rule Reference

SEC454lintai-ai-securitysupply-chainhardeningstablemarkdownwarn

AI markdown: npm http source

AI-native markdown installs JavaScript packages from an insecure direct `http://` source

Public lane
supply-chain
Category
hardening
Provider
lintai-ai-security
Scope
per-file
Surface
markdown
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message only
How to read this lane

Reproducibility, provenance, and dependency hardening review.

How to read this category

Least-privilege, provenance, or operational hygiene signal.

Activation Model

Preset Activation

These presets explain where this rule appears in the product experience.

supply-chainsidecar lane

Lifecycle

Stable Lifecycle Contract

State

stable

Graduation rationale

Checks AI-native markdown for `npm`, `pnpm`, `yarn`, and `bun` install examples that fetch a direct package source over `http://`.

Deterministic signal basis

MarkdownSignals exact `npm install`, `npm i`, `pnpm add/install`, `yarn add`, or `bun add` token analysis with direct `http://` source detection inside parsed markdown regions, excluding `--registry http://` forms already covered by SEC450.

Malicious corpus
skill-npm-http-source
Benign corpus
skill-npm-https-source-safe
structured evidence required remediation reviewed
Canonical note

Structural stable rule positioned as a supply-chain hardening control: high-precision and actionable, but not a blanket claim of direct repository compromise.

Nearby Signals

Related Rules

SEC417AI markdown: unpinned pip git installAI-native markdown installs Python packages from an unpinned `git+https://` sourcesupply-chainhardeningmarkdown
SEC448AI markdown: pip trusted-hostAI-native markdown installs Python packages with `--trusted-host`supply-chainhardeningmarkdown
SEC449AI markdown: pip http indexAI-native markdown installs Python packages from an insecure `http://` package indexsupply-chainhardeningmarkdown
SEC450AI markdown: npm http registryAI-native markdown installs JavaScript packages from an insecure `http://` registrysupply-chainhardeningmarkdown
SEC451AI markdown: cargo http git installAI-native markdown installs Rust packages from an insecure `http://` git sourcesupply-chainhardeningmarkdown
SEC452AI markdown: cargo http indexAI-native markdown installs Rust packages from an insecure `http://` indexsupply-chainhardeningmarkdown

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, or bun 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 by SEC450
  • unrelated http:// text outside a matching install form

Example Trigger ​

bash
npm install http://registry.example.test/demo.tgz

Safer Example ​

bash
npm install https://registry.example.test/demo.tgz

How To Fix ​

Replace the insecure direct http:// source with a normal TLS-verified https:// source.