lintai docs

Appearance

Rule Reference

SEC459lintai-ai-securitysupply-chainhardeningstablemarkdownwarn

AI markdown: js package config http registry

AI-native markdown configures a JavaScript package manager with an insecure `http://` registry

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 JavaScript package-manager config commands that point registry configuration at `http://` sources.

Deterministic signal basis

MarkdownSignals exact `npm config set`, `pnpm config set`, or `yarn config set` token analysis with `registry http://` or `registry=http://` detection inside parsed markdown regions.

Malicious corpus
skill-js-package-config-http-registry
Benign corpus
skill-js-package-config-https-registry-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

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 set
    • pnpm 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 by SEC450
  • 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.