g0h4n/RustHound-CE - Open Source PR Review Scorecard

Active Directory data ingestor for BloodHound Community Edition written in Rust. 🦀

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

External PR Merge Rate: 87%

Response Time: 11h

First Timer Success: 100%

Frequently Asked Questions

Is g0h4n/RustHound-CE welcoming to first-time open-source contributors?

g0h4n/RustHound-CE 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.

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

Maintainers in g0h4n/RustHound-CE respond to incoming external pull requests in approximately 11.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 63.0 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 63.0 places g0h4n/RustHound-CE in the A tier.

What is the external contributor pull request merge rate for g0h4n/RustHound-CE?

The external contributor pull request merge rate for g0h4n/RustHound-CE is 87.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in g0h4n/RustHound-CE?

g0h4n/RustHound-CE does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

g0h4n
g0h4n/RustHound-CEA•Welcoming609
GitHub
Back to Explorer
g0h4n

g0h4n/RustHound-CE

609
InactiveA•Welcoming(63/100)Rust

Active Directory data ingestor for BloodHound Community Edition written in Rust. 🦀

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Constructive Code Reviewer

Warmth Score
7.4/10
Patience Score
7.8/10
Nitpick Rate
33%

Balanced & professional review environment in g0h4n/RustHound-CE. Maintains strict focus on technical quality and test standards.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Run repository linter and code formatters locally before pushing
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
11 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
87.0%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
2 core
Small core review team
Diagnostic Health HUD
87.0%
Merge Gauge
100.0%
1st-Timer
Community Vibe86/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

Summary Add Kerberos (pass-the-ticket) authentication to the SMB transport in transport/smb.rs, so the sessions module (SRVSVC / WKSSVC / WINREG over IPC$) and GPO SYSVOL collection can authenticate with a Kerberos ticket, in addition to the existing password and pass-the-hash paths. Motivation transport::smb currently supports two SESSION_SETUP paths via SmbAuth: SmbAuth::Password (NTLMv2) SmbAuth::Hash (pass-the-hash) The LDAP side of RustHound-CE already speaks Kerberos (GSSAPI), so an operator running with a TGT/ccache can collect over LDAP but then falls back to NTLM/PtH for the SMB/RPC paths. This is inconsistent, and NTLM is increasingly disabled in hardened environments. A Kerberos path would let the whole collection run under one authentication mechanism and work where NTLM is turned off. Proposed change smb2-client already exposes SmbClient::login_kerberos(gss_blob, session_key), which performs the SESSION_SETUP from a prebuilt SPNEGO AP-REQ and its 16-byte GSS session key.

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

Feature description It would be very useful to add support for certificate-based authentication using a PFX file in RustHound-CE, leveraging a Pass-the-Certificate technique via Schannel. This feature would allow operators to authenticate to Active Directory using an exported certificate (PFX) without requiring a password, NT hash, or Kerberos ticket, similarly to existing techniques like Pass-the-Hash or Pass-the-Ticket. Motivation / Use case Certificate-based authentication is increasingly common in modern Active Directory environments (AD CS, smartcard logon, machine certs, etc.) and is often overlooked by traditional detection. Expected behavior Ability to authenticate using a PFX certificate + private key Authentication performed via Schannel No password, NTLM hash, or Kerberos ticket required Compatible with existing RustHound-CE enumeration logic once authenticated Example: # from .pfx rusthound-ce \ --domain essos.local \ --pfx user.pfx \ --pfx-pass "<Optionnal>

📅 Opened Feb 4, 2026💬 0 comments
Quality: 70/100Contribute
Looking for more Rust beginner tasks?Explore Rust 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 g0h4n/RustHound-CE

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

Frequently Asked Questions - Contributing to g0h4n/RustHound-CE

01

Is g0h4n/RustHound-CE welcoming to first-time open-source contributors?

g0h4n/RustHound-CE 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.

02

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

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

03

What does the 63.0 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 63.0 places g0h4n/RustHound-CE in the Welcoming tier.

04

What is the external contributor pull request merge rate for g0h4n/RustHound-CE?

The external pull request merge rate is 87.0%. 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 g0h4n/RustHound-CE?

g0h4n/RustHound-CE does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for g0h4n/RustHound-CE 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.