Guardrails / python

Python dependencies are locked

python/lockfile-committed@v1

The project commits a lock file, so an install of the same commit resolves the same versions.

Id	python/lockfile-committed
Version	v1
Category	python
Default severity	warning
Interpreter	python3
Timeout	30 seconds
Violations tolerated	0
Collects	python

Collectors

This guardrail doesn't gather anything itself. It relies on the collectors below, which the CLI runs once per build before any check, and reads what they found from GUARDRAIL_FACTS. If a collector collects nothing, this guardrail is skipped, not failed.

Collector	Gathers	Inputs it is given
python	The Python project in the project directory: its manifest and build backend, the Python version it asks for, the requirements it declares and which of them are pinned, and the lock files committed beside them.	projectDir

The inputs above are this guardrail's own inputs, passed straight through to the collector. Setting one in buildnote.json changes what is collected, and two guardrails configured the same way share a single collection.

Configuration

{
  "guardrails": {
      "failOn": "error",
      "checks": [
          {
              "use": "python/lockfile-committed@v1",
              "severity": "warning",
              "with": {
                  "projectDir": "."
              },
              "exemptions": []
          }
      ]
  }
}

Inputs

Input	Description	Default	Environment variable
projectDir	Directory holding the project, relative to the directory the CLI runs in.	.	GUARDRAIL_INPUT_PROJECTDIR

How to fix

Commit the lock file your installer writes:

uv lock          # writes uv.lock
poetry lock      # writes poetry.lock
pip-compile      # writes requirements.txt from requirements.in

A >= or ~= requirement resolves to whatever the index serves that day, so without a lock file the build that shipped is not the build that was reviewed.

More in python

• python/build-backend-declared. A packaged project names its build backend in [build-system], so it builds the same way everywhere.
• python/single-lockfile. The project commits at most one lock file, so two installers don't both try to manage the environment.
• python/version-declared. The project declares the Python version it is built and run against, and that version is no older than the configured floor.

All 4 python guardrails