Skip to content

Rule Reference

SEC464lintai-ai-securitysupply-chainhardeningstablemarkdownwarn

AI markdown: git http clone

AI-native markdown clones a Git repository from an insecure `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 `git clone` examples that fetch repositories directly from an insecure `http://` source.

Deterministic signal basis

MarkdownSignals exact `git clone` token analysis with direct `http://` source detection inside parsed markdown regions.

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

SEC464 / MD-GIT-HTTP-CLONE

SEC464 flags AI-native markdown when a git clone example fetches a repository directly from http://....

Why It Matters

An http:// clone source removes transport integrity from repository bootstrap. In shared AI-native instructions, that turns an insecure source fetch into copy-pastable setup guidance.

What Triggers It

  • AI-native markdown surface
  • the same parsed markdown region contains git clone
  • the same region also contains a direct http:// repository source

The finding points to the http:// token itself.

What Does Not Trigger It

  • git clone https://...
  • unrelated http:// prose outside a matching git clone form

Example

Bad:

bash
git clone http://git.example.test/demo.git

Better:

bash
git clone https://github.com/acme/demo.git

Remediation

Replace the insecure http:// clone source with a normal TLS-verified https:// repository URL.