Skip to content

Rule Reference

SEC459lintai-ai-securitystablemarkdownwarn

AI markdown: js package config http registry

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

Provider
lintai-ai-security
Surface
markdown
Scope
per_file
Tier
stable
Severity
warn
Confidence
high
Detection
structural
Remediation
message_only

Activation Model

Preset Membership

This rule is part of the builtin activation graph through these preset memberships.

Lifecycle

Stable Lifecycle Contract

State

stable_gated

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 intended as a high-precision check with deterministic evidence.

Nearby Signals

Related Rules

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.