AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 20 Bitcoin

tests: pin all Python test dependencies to exact versions

Public commit record

What the developer wrote

Authored by Salvatore Ingala

83/100 · Strong
tests: pin all Python test dependencies to exact versions

requirements.txt used version ranges (with no upper bound for speculos
and ragger), so every CI run could install a newly published release
of any direct or transitive dependency without review.

Move the ranges to requirements.in, and generate requirements.txt from
it with uv, pinning every package to an exact version:

uv pip compile requirements.in --universal --python-version 3.9 -o requirements.txt

--python-version 3.9 matches the oldest Python in CI (the speculos:0.25.5
image of the legacy app job); --universal keeps the lock valid for the
newer versions in ledger-app-dev-tools.

Hashes are intentionally not generated: pip rejects the editable
./bitcoin_client requirement in hash-checking mode, which would require
installing the client separately in every job and in the setup script.

The published ledger_bitcoin package is not affected, as its
dependencies come from bitcoin_client/setup.cfg.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit pins the exact versions of Python testing tools used by the project's automated tests. Previously, the test setup allowed any newly released version of those tools to be installed automatically, which could introduce unexpected changes or malicious code from a compromised dependency into the CI/test environment. Pinning versions is a routine supply-chain hygiene improvement; it does not fix a known vulnerability in the app itself.

Recommended action

No immediate security action required. Treat as routine hardening. If stronger supply-chain assurance is needed, consider installing the editable bitcoin_client separately so the remaining pinned dependencies can be verified with hashes, and review the locked versions for known CVEs before merging.

Security signals we found

01

Supply-chain risk reduction for test/CI dependencies

02

Prevents unreviewed automatic upgrades of speculos and ragger

03

No change to firmware or published package code

04

No hashes generated due to editable local package constraint

Risk score

Why this scored 20/100

Our methodology →
Potential impact 2/30
Exploitability 2/25
Stealth signal 1/15
Affected reach 3/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.