A commissioning tool for pico-fido firmware based hardware keys.
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 88%
Response Time: 2d
First Timer Success: 100%
librekeys/picoforge has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in librekeys/picoforge respond to incoming external pull requests in approximately 39.7 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 56.7 places librekeys/picoforge in the A tier.
The external contributor pull request merge rate for librekeys/picoforge is 88.2%, based on public PR activity from non-core contributors.
librekeys/picoforge currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Rust project in librekeys/picoforge welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/librekeys/picoforge?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (40% approval). Keep your diff compact for rapid review.
NotePlease read our Contributing Guidelines to understand how to get involved. For new features, it is highly recommended to discuss the implementation details in our communication channels before submitting a PR. Before submitting a feature request, check the following checklist: I have searched the existing issues/discussions to ensure this hasn't been proposed before I have confirmed this feature is within the scope of PicoForge/LibreKeys I am using the latest version of PicoForge Proposed Feature Ask the user to setup a pin when changing settings that need authentication if they haven't set one up yet. Or when they connect their key with the ability to dismiss. Is your feature request related to a problem? When attempting to authenticate to change settings on my device it does not ask me to setup a pin for the device and instead expects that there's a pin setup on the key already. Describe the solution you'd like Ask the user to setup a pin on their device when changing setti
Before submitting an issue, check the following checklist: [+ ] I have checked the Troubleshooting Guide [+ ] I have searched the existing issues to ensure this has not already been reported [+ ] I am using the latest version of PicoForge [+ ] I am using the the latest supported version of picofido/picofido2 The Problem The app won't start. What are the steps to reproduce this issue? git clone cargo build --release ./target/release/picoforge Expected Results RFC 1925, (1) It Has To Work. Actual Results % RUST_BACKTRACE=full ./target/release/picoforge [2026-05-30 20:34:09 +03:30 ERROR blade_graphics::hal::surface] No composite alpha flag for transparency: OPAQUE [2026-05-30 20:34:09 +03:30 INFO picoforge::device::rescue] Reading full device details [2026-05-30 20:34:09 +03:30 INFO picoforge::device::rescue] No Smart Card Reader found [2026-05-30 20:34:09 +03:30 WARN picoforge::device::io] Rescue method failed: No device found. Falling back to FIDO... [2026-05-30 20:34:09 +03:30 INF
Proposed Feature It is not possible to use picoforge to configure a key if 2 keys are plugged-in at the same time or if a smart-card reader is plugged-in at the same time as the key. Is your feature request related to a problem? Some computers have an integrated smart car reader that cannot be un-plugged. On these, picoforg is completely unusable. See details in #68. Describe the solution you'd like picoforge should detect that multiple security devices are present and popup a dialog for the user to select the one he wants to connect to. Describe alternatives you've considered When the conflicting devices is external it can be temporarily unplugged to resolve the conflict. But that is not ideal. And when the device is integrated to the computer it is not possible to unplug it. How would this improve the user experience? should be clear with what I wrote above Implementation Details (Optional) Proposed Hardware/Firmware Impact none needed Additional Context Visual Aids (Optional)
We need to document our findings regarding the issues that occurs when switching from EDDSA to non EDDSA firmware into the troubleshooting section of the wiki. Here is a test I just did : Flash a virgin raspberry pico2 with [pico-fido-pico2.uf2](https://github.com/librekeys/pico-fido-firmwares/releases/download/picofido-7.4.2-librekeys%2B1/pico-fido-pico2.uf2) 2.Test unlock storage => OK Flash [pico-fido-pico2-eddsa.uf2](https://github.com/librekeys/pico-fido-firmwares/releases/download/picofido-7.4.2-librekeys%2B1/pico-fido-pico2-eddsa.uf2) onto it Use https://webauthn.io/ to create a sign-in data onto the key. Test unlock storage => OK Flash back [pico-fido-pico2.uf2](https://github.com/librekeys/pico-fido-firmwares/releases/download/picofido-7.4.2-librekeys%2B1/pico-fido-pico2.uf2) Test unlock storage => Error ... I've made more tests with EDDSA and non EDDSA firmwares which confirm this. unlocking storage fails with non EDDSA firmware if the key contains a passkey that was created
As per discussion on discord : 12b Have you used the pico-openpgp firmware? I tried to use it with gpg but all I get is $ gpg --card-status gpg: selecting card failed: No such device — lockedmutex — No I have not, I was actually going to flash pico-fido2 first, but PH closed sourced it, so I just gave up on openpgp part. I kept openpgp and hsm for later, after picoforge implementation completely works with pico-fido. I will setup a github project later, to track ongoing issues, planned features and features currently being worked on. @onegrit have u tried picoopenpgp or picohsm? — 12b — gpg --card-status is working on macOS, using Yubico VID:PID (1050:0407) It must be something missing or not configured correctly on my linux system. Or it is not working at all under Linux. If anybody could test on Linux to confirm that would be nice. — 12b — Nevermind, I found what was missing. I needed to add a config file to disable gpg scdaemon internal CCID driver and use pcsc : $ cat
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to librekeys/picoforge, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of librekeys/picoforge acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 88.2% were successfully merged into the primary branch.
librekeys/picoforge has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 56.7 places librekeys/picoforge in the Welcoming tier.
The external pull request merge rate is 88.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, librekeys/picoforge currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for librekeys/picoforge are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.