lintai docs

Appearance

Rule Reference

SEC461lintai-ai-securitysupply-chainhardeningstablemarkdownwarn

AI markdown: pip config trusted-host

AI-native markdown configures Python package resolution with `trusted-host`

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 `pip config set` commands that configure trusted-host bypass behavior.

Deterministic signal basis

MarkdownSignals exact `pip config set`, `pip3 config set`, or `python -m pip config set` token analysis with `global.trusted-host` detection inside parsed markdown regions.

Malicious corpus
skill-pip-config-trusted-host
Benign corpus
skill-pip-config-unrelated-key-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

SEC461 / MD-PIP-CONFIG-TRUSTED-HOST ​

SEC461 flags AI-native markdown when a pip config set, pip3 config set, or python -m pip config set command sets global.trusted-host.

Why It Matters ​

Setting trusted-host weakens normal trust checks for package resolution. In shared AI-native instructions, that turns a persistent verification bypass into copy-pastable setup guidance.

What Triggers It ​

  • AI-native markdown surface
  • the same parsed markdown region contains:
    • pip config set
    • pip3 config set
    • or python -m pip config set
  • the same region also contains:
    • global.trusted-host ...
    • or global.trusted-host=...

The finding points to the global.trusted-host token.

What Does Not Trigger It ​

  • unrelated pip config keys like global.timeout
  • install-time --trusted-host examples, because those are covered by SEC448
  • unrelated prose that mentions trust or hosts without a matching pip config command

Example ​

Bad:

bash
pip config set global.trusted-host pypi.example.test

Better:

bash
pip config set global.index-url https://pypi.example.test/simple

Remediation ​

Remove the trusted-host config and rely on normal TLS-verified Python package sources instead.