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

clnrest: do not install dependencies from git url

Public commit record

What the developer wrote

Authored by ShahanaFarooqui

88/100 · Strong
clnrest: do not install dependencies from git url

This reverts [commit](https://github.com/ElementsProject/lightning/pull/8536/commits/cd1ec7216b66bb2f84244ab8c186a003b49d55d6), as an alternative fix has already been introduced in PR [#8547](https://github.com/ElementsProject/lightning/pull/8547) to restore reproducible builds.

This reversion is necessary because otherwise Docker image building will fail with GitHub Actions or via build-release.sh. The issue arises from Cargo’s inability to resolve the git URL dependencies for clnrest’s utoipa and utoipa-swagger-ui packages within these build contexts. While direct `docker buildx` commands succeeds, Github Action or build-release.sh modifies the build context in a way that prevents Cargo from locating the specific git commit for these dependencies.

References:
https://github.com/ElementsProject/lightning/pull/8530#issuecomment-3248713576
https://github.com/ElementsProject/lightning/actions/runs/17435823432
Added fixed SOURCE_DATE_EPOCH flag for reproducible ubuntu builds [8547](https://github.com/ElementsProject/lightning/pull/8547)

Changelog-None.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit changes how the clnrest plugin pulls in two Rust helper libraries (utoipa and utoipa-swagger-ui). Previously they were downloaded directly from a personal GitHub fork; now they come from the official crates.io registry. The change was made to fix broken Docker and release builds, not because of a known security flaw. Using registry versions is generally safer and more reproducible than an unreviewed git fork, but the commit itself does not claim to fix any vulnerability.

Recommended action

Treat as a routine build/maintenance improvement. Verify that the new registry versions of utoipa and utoipa-swagger-ui do not introduce API incompatibilities in clnrest. No urgent security action is required based on the supplied materials.

Security signals we found

01

Dependency source changed from personal git fork to official registry

02

Build reproducibility and supply-chain consistency improved by using versioned crates with checksums

03

No security bug, CVE, or exploit path described in commit or references

Risk score

Why this scored 16/100

Our methodology →
Potential impact 2/30
Exploitability 1/25
Stealth signal 1/15
Affected reach 2/15
Confidence 7/10
Evidence quality 3/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.