Reading the repo — stats and the shipped feed land in about ten seconds…
Pure Rust implementation of the PLONK ZKProof System done by the Dusk team
643 160 8 openLast shipped 6h ago
Pure Rust implementation of the PLONK ZKProof System done by the Dusk team
The team fixed issues with proof and key decoding that were causing failures in serialization and deserialization workflows. In parallel, they optimized circuit construction by removing unnecessary polynomial computations and cleaning up default trait requirements, reducing overhead and improving…
Get this in your inbox every Monday →A deterministic 0–100 hygiene score — README, license, CI, tests, docs, and freshness.
Who ships this repo — author concentration and the bus factor across the last 300 mainline commits.
How welcoming this repo is to contributors — issue throughput, close time, responsiveness, and good-first-issue count.
What this project is built on — dependency count by ecosystem, the license mix, and anything worth a legal look before you adopt it.
Whether this project's CI can be trusted — pass rate, run times, flaky runs, and which workflow is the weak link.
Grounded in plonk's README, structure, and recent commits — answers won't invent code they haven't seen.
A Monday email with what shipped, in plain English — no account needed.
Showing raw commit titles for the newest commits. Sign in to generate AI summaries.
Merge pull request #997 from dusk-network/neotamandua/avoid-unused-polynomial-power
A floor, not a guess: counts only commits whose author, co-author trailer, or message explicitly credits an AI tool (Claude, Copilot, Cursor, aider, Codex…). Based on 30 mainline commits. Unattributed AI code isn't counted here — the full audit estimates that separately.
