linuxboot/heads - Open Source PR Review Scorecard

A minimal Linux that runs as a coreboot or LinuxBoot ROM payload to provide a secure, flexible boot environment for laptops, workstations and servers.

C-Rank Grade: A (Welcoming) - 56/100

External PR Merge Rate: 29%

Response Time: <1h

First Timer Success: -

Frequently Asked Questions

Is linuxboot/heads welcoming to first-time open-source contributors?

linuxboot/heads has a recorded first-timer success rate of 0.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in linuxboot/heads respond to incoming external pull requests in approximately 0.3 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 56.3 C-Rank™ score (A Tier) represent?

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.3 places linuxboot/heads in the A tier.

What is the external contributor pull request merge rate for linuxboot/heads?

The external contributor pull request merge rate for linuxboot/heads is 29.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in linuxboot/heads?

linuxboot/heads currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

linuxboot
linuxboot/headsA•Welcoming1.6k
GitHub
Back to Explorer
linuxboot

linuxboot/heads

1,584
InactiveA•Welcoming(56/100)Low Sample (<20 PRs)MAMakefile

A minimal Linux that runs as a coreboot or LinuxBoot ROM payload to provide a secure, flexible boot environment for laptops, workstations and servers.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in linuxboot/heads welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
<1 hour
⚡ Fast reviewer response

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
29.4%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
0.0%
No first-timer merges recorded in window

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
11 core
Highly collaborative maintainer core
Diagnostic Health HUD
29.4%
Merge Gauge
0.0%
1st-Timer
Community Vibe42/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for linuxboot/heads
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/linuxboot/heads)](https://getmerged.abhishekco.de/linuxboot/heads?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

@MrChromebox updated https://review.coreboot.org/c/coreboot/+/85278 Note that the coreboot matrix thread We understand that both can't be used at the same time INTEL_CHIPSET_LOCKDOWN=y vs # CONFIG_INTEL_CHIPSET_LOCKDOWN is not set + CONFIG_SOC_INTEL_COMMON_SPI_LOCKDOWN_SMM=y Other message in thread: Note that as of now, patches for different platforms grew in forks who use this, and afaik it's mostly heads So PR0 patches are Work for alder lake and meteorlake under dasharo fork (seems self-contained under Dasharo/coreboot@a4f9bd2) community attempt under ready to merge kano (26.03) under https://github.com/linuxboot/heads/pull/2133/changes#diff-f1f6f628ec68a607e292baa7e86c813f2d966fc7420b31b7f24ea7f346aed525 Starlabs patch on top of coreboot upstream 26.07.01 (untested yet AFAIK) https://github.com/linuxboot/heads/pull/2164/changes#diff-12e023b0ef7b98398ffcbd169c5a0f38520f4e87642cc55dd9ffecbadfb3e180 So upstream https://review.coreboot.org/c/coreboot/+/85278 still lack implementa

📅 Opened Sep 19, 2026💬 1 comment
Quality: 90/100Contribute

Skylake+ and possibly other platforms (t480*) From discussion on coreboot matrix thread Turns out the PCH-H datasheets are just wrong and the pad_cfg_lock_offset value for GPIO community 0 was wrong. I fixed it to match edk2-platforms and the Linux pin-ctrl driver and locking seems to be working with my original patch, though with the SBI method instead of the PCR method: https://review.coreboot.org/c/coreboot/+/90885 I will push some patches later Locking them in SMM as is done in the patch train of https://review.coreboot.org/c/coreboot/+/95545 does not appear to be working on Skylake even with the corrected offsets. AlderLake Also patchtrain for alderlake (nv4x_adl), would needs backporting https://review.coreboot.org/q/topic:%22tpm_gpio_pltrst_lock%22 to be applied downstream until next release of Dasahro+Heads Referred from Dasharo/coreboot#959 (comment) TODO update downstream forks used patchtrains test against nv4xadl update https://github.com/tlaurion/tpm-gpio-fail upda

📅 Opened Sep 19, 2026💬 1 comment
Quality: 90/100Contribute

For those who follows, its been a couple of PR that I try to save them, since there is 4kb left in master of freed ME space on those boards for maximized-hotp builds. I plan to merge #2206 soon, and the code comments alone of that pr are now consuming that 4kb compressedfreed space. It's your time to shine: you're technical, own a x220/t420, want to jump in under #1991 or any other quests under #590 to revive them, be my guest. Flagging this u=issue with help needed and pinning, Sorry folks, 8mb spi boards not a priority of mine. Is it one of yours? Shine :)

📅 Opened Sep 17, 2026💬 0 comments
Quality: 90/100Contribute

Before filing a bug report Follow-up to #2008 and #2186. #2186 merged in master. Hardware details Board: novacustom-v540tu (failing). Working: x230 (EOL_x230-maximized), novacustom-nv4x_adl. GPU: iGPU-only (Intel Meteor Lake, device ID 7d55). Heads/Dasharo: Dasharo Heads-v0.2.1-3144-g7850f7a (DMI BIOS string), vendor-installed by Novacustom. ROM: vendor (Dasharo) image, maximized. Please describe the problem Describe the bug #2186 ("initrd: boot dd-written hybrid ISOs in mount-usb and usb-autoboot") fixes #2008 ("kicksecure iso doesn't boot under Heads") on x230 and novacustom-nv4x_adl. On novacustom-v540tu the Kicksecure ISO fails to boot only in live-amnesic mode ("LIVE Mode | USER Session | disposable use"): the machine auto-reboots before/at the LXQt desktop. The failure is specific to the live-amnesic USER session. Non-live-amnesic modes boot fine on the same machine: "LIVE Mode | SYSMAINT Session" (sysmode) boots to console, and the other grub entries are unaffected. To Reprodu

📅 Opened Aug 19, 2026💬 4 comments
Quality: 90/100Contribute

This comes often from community members suggesting crypto donation ,latest today in qubes matrix room. But problem is burden on me, I would need to receive the donations, without the burden of converting to fiat and legal/accounting burden. Present thoughts (require time, not replicated by any other small team based teams AFAIK) Switch OpenCollective's Fiscal Host from Open Source Collective to Open Collective Europe which Could theoretically provide Tax deduction papers to donor (fiat donations) Could theoretically deal with crypto->fiat conversion to collective once converted, though they require collective to Have a minimum balance of €2,000. QubesOS/Whonix and other projects accepts crypto donations by providing direct wallet addresses. Issue there is as said prior: burden is for me to have legal/accounting burden. Others avenues not yet considered.

📅 Opened Jul 24, 2026💬 4 comments
Quality: 80/100Contribute
Looking for more Makefile beginner tasks?Explore Makefile GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for linuxboot/heads

When evaluating whether to contribute to linuxboot/heads, 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 linuxboot/heads acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 29.4% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to linuxboot/heads

01

Is linuxboot/heads welcoming to first-time open-source contributors?

linuxboot/heads has a recorded first-timer success rate of 0.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 56.3 C-Rank™ score represent?

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.3 places linuxboot/heads in the Welcoming tier.

04

What is the external contributor pull request merge rate for linuxboot/heads?

The external pull request merge rate is 29.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in linuxboot/heads?

Yes, linuxboot/heads currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for linuxboot/heads 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.