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

pyln-proto: temporarily switch to coincurve-cp314-fix

Public commit record

What the developer wrote

Authored by daywalker90

73/100 · Adequate
pyln-proto: temporarily switch to coincurve-cp314-fix

Using `uv.sources` / `uv.index` does not work when publishing to pypi.

Instead i forked coincurve master, published all the wheels as coincurve-cp314-fix
v22 with fixes to make it work on python 3.14

Changelog-None
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This change swaps the project's Python cryptography dependency from the well-known 'coincurve' package to a temporary fork called 'coincurve-cp314-fix' published by an individual contributor (daywalker90). The stated reason is to fix Python 3.14 compatibility while still being publishable to PyPI. Because the new package is a fork maintained outside the original project, users now depend on a less-trusted supply chain. There is no direct evidence of malicious code in the commit, but the change increases supply-chain risk.

Recommended action

Verify the fork's source against upstream coincurve master and confirm the only changes are Python 3.14 compatibility fixes. Pin the dependency to an exact version, monitor upstream coincurve for an official release that supports Python 3.14, and revert to the official package as soon as possible. Review the fork's publishing credentials and PyPI ownership.

Security signals we found

01

Dependency switched from established package to a temporary fork with a different publisher

02

Custom PyPI package name 'coincurve-cp314-fix' is not the upstream project

03

Fork publisher is an individual GitHub user (daywalker90), not the original coincurve maintainers

04

No source code of the fork is included in the commit; only lockfile hashes are present

05

Changelog-None indicates this is treated as a routine packaging fix

Risk score

Why this scored 32/100

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