Skip to content

Rule Reference

SEC457lintai-ai-securitysupply-chainhardeningstablemarkdownwarn

AI markdown: js package strict-ssl false

AI-native markdown disables strict SSL verification for JavaScript package manager config

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.

Lifecycle

Stable Lifecycle Contract

State

stable

Graduation rationale

Checks AI-native markdown for JavaScript package-manager config commands that explicitly disable strict SSL verification.

Deterministic signal basis

MarkdownSignals exact `npm config set`, `pnpm config set`, or `yarn config set` token analysis with `strict-ssl false` or `strict-ssl=false` detection inside parsed markdown regions.

Malicious corpus
skill-js-package-strict-ssl-false
Benign corpus
skill-js-package-strict-ssl-true-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

SEC457 / MD-JS-PACKAGE-STRICT-SSL-FALSE

SEC457 flags AI-native markdown when an npm config set, pnpm config set, or yarn config set command disables strict SSL verification with strict-ssl false or strict-ssl=false.

Why It Matters

Disabling strict SSL verification removes normal certificate checks for package-manager network traffic. In shared AI-native instructions, that turns a TLS-bypass 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:
    • strict-ssl false
    • or strict-ssl=false

The finding points to the strict-ssl false token.

What Does Not Trigger It

  • strict-ssl true
  • unrelated prose that mentions SSL without a matching package-manager config command

Example

Bad:

bash
npm config set strict-ssl false

Better:

bash
npm config set strict-ssl true

Remediation

Remove the strict-ssl disable and keep normal certificate verification enabled for package-manager config.