lintai docs

Appearance

Rule Reference

SEC416lintai-ai-securitypreviewmarkdownwarn

AI markdown: Claude bare pip install

AI-native markdown models Claude package installation with bare `pip install` despite explicit `uv` preference guidance

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

Activation Model

Preset Membership

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

previewmembership
skillsmembership

Lifecycle

Preview Lifecycle Contract

State

preview_blocked

Promotion blocker

This rule depends on transcript-shaped markdown plus explicit `uv` preference context in the same AI-native document, so the first release stays guidance-only while broader ecosystem usefulness is measured.

Promotion requirements

Needs corpus-backed precision review, a non-heuristic graduation basis, and completed stable checklist metadata.

Canonical note

Heuristic preview rule; not a stable contract and may evolve as false-positive tuning improves.

Nearby Signals

Related Rules

SEC101HTML comment: dangerous instructionsHidden HTML comment contains dangerous agent instructionsmarkdownpreview
SEC102Markdown: remote execution instructionMarkdown contains remote download-and-execute instruction outside code blocksmarkdownpreview
SEC103HTML comment: remote execution instructionHidden HTML comment contains remote download-and-execute instructionmarkdownpreview
SEC104Markdown: base64 executable payloadMarkdown contains a base64-decoded executable payload outside code blocksmarkdownpreview
SEC105Markdown: parent-directory file accessMarkdown instructions reference parent-directory traversal for file accessmarkdownpreview
SEC313Shell example: remote content piped to shellFenced shell example pipes remote content directly into a shellmarkdownpreview

SEC416 / MD-CLAUDE-PIP-INSTALL ​

SEC416 flags AI-native markdown when the same document explicitly says to prefer uv over pip, but still models Claude package installation with bare pip install.

Why It Matters ​

If a project teaches agents to prefer uv, transcript examples that still show Claude using bare pip install create contradictory guidance. These examples are easy to copy into real agent workflows and make package-management behavior less consistent and less reproducible.

Trigger Shape ​

The rule triggers only when all of these are true:

  • the file is an AI-native markdown surface such as CLAUDE.md, AGENTS.md, SKILL.md, Cursor rules, or plugin agent docs
  • the document contains an explicit uv-over-pip preference marker such as use uv not pip or Always use \uv` instead of `pip``
  • a prose, blockquote, or fenced transcript region contains a Claude: line with bare pip install or python -m pip install
  • the matched Claude: line does not already use uv pip install

Clean Cases ​

These stay clean:

  • Claude: uv pip install pytest
  • bare pip install examples without any explicit uv not pip preference context
  • generic package installation prose that is not framed as a Claude: transcript

Example Trigger ​

text
- Always use `uv` instead of `pip` for Python packages

Claude: pip install pytest

Safer Example ​

text
- Always use `uv` instead of `pip` for Python packages

Claude: uv pip install pytest

How To Fix ​

Replace bare pip install Claude transcript examples with uv pip install, or clearly mark them as intentionally incorrect pre-correction behavior if the document is demonstrating a before-and-after learning flow.