Skip to content

Rule Reference

SEC455lintai-ai-securitysupply-chainhardeningstablemarkdownwarn

AI markdown: pip http git install

AI-native markdown installs Python packages from an insecure `git+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.

Lifecycle

Stable Lifecycle Contract

State

stable

Graduation rationale

Checks AI-native markdown for `pip install` examples that fetch Python packages from an insecure `git+http://` source.

Deterministic signal basis

MarkdownSignals exact `pip install` token analysis with `git+http://` detection inside parsed markdown regions.

Malicious corpus
skill-pip-http-git-install
Benign corpus
skill-pip-https-git-install-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

SEC455 / MD-PIP-HTTP-GIT-INSTALL

SEC455 flags AI-native markdown when a pip install example uses git+http://....

Why It Matters

git+http:// removes normal TLS protection from the package source 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 pip install, pip3 install, or python -m pip install
  • the same region also contains git+http://...

The finding points to http://.

Clean Cases

These stay clean:

  • pip install git+https://...
  • direct http://... pip source examples already covered by SEC453
  • unpinned git+https://... examples already covered by SEC417

Trigger Example

bash
pip install git+http://git.example.test/demo.git

Safer Example

bash
pip install git+https://git.example.test/demo.git

How To Fix

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