Graphify-Labs/graphify - Open Source PR Review Scorecard

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

C-Rank Grade: B (Solid) - 52/100

External PR Merge Rate: 8%

Response Time: 8h

First Timer Success: 9%

Frequently Asked Questions

Is Graphify-Labs/graphify welcoming to first-time open-source contributors?

Graphify-Labs/graphify has a recorded first-timer success rate of 9.2%. Repositories ranked B 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 Graphify-Labs/graphify respond to incoming external pull requests in approximately 8.2 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 51.7 C-Rank™ score (B 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 51.7 places Graphify-Labs/graphify in the B tier.

What is the external contributor pull request merge rate for Graphify-Labs/graphify?

The external contributor pull request merge rate for Graphify-Labs/graphify is 7.8%, based on public PR activity from non-core contributors.

Are there Good First Issues available in Graphify-Labs/graphify?

Graphify-Labs/graphify currently has 21 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

Graphify-Labs
Graphify-Labs/graphifyB•Solid123.6k
GitHub
Back to Explorer
Graphify-Labs

Graphify-Labs/graphify

123,600
InactiveB•Solid(52/100)Python

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Quality Architect

Warmth Score
6.6/10
Patience Score
7.2/10
Nitpick Rate
43%

Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in Graphify-Labs/graphify.

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
8 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
7.8%
Selective PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
9.2%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
172 core
Highly collaborative maintainer core
Diagnostic Health HUD
7.8%
Merge Gauge
9.2%
1st-Timer
Community Vibe30/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Good first issue. #4007 added invokes edges for interpreter runs; add explicit coverage that source lib.sh / . ./env.sh still produce the existing imports_from edge and are not mistaken for invokes. Where: tests/test_extract.py (bash section) What: add a script that sources another and assert the imports_from edge, and that no invokes edge is emitted for the source form. Acceptance: new test passes.

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

Good first issue (small feature). #4038 resolves context bounds on methods (def f[A: Ordering]); class-level bounds (class Foo[A: Ordering]) are not yet walked. Where: graphify/extractors/engine.py Scala branch (mirror the method context-bound handling for class_definition/trait_definition type_parameters) What: emit a references/type_bound edge from the class to each context-bound type. Acceptance: a new test asserts class Foo[A: Ordering] → references Ordering.

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

Good first issue. #3965 extracts @Ann(x = Foo::class) references; the fully-qualified-strip (com.example.Foo::class) and builtin-filter (String::class → no edge) branches rest on code logic without asserts. Where: tests/test_kotlin_grammar.py What: add asserts for (1) com.example.Customer::class → an edge to Customer, and (2) String::class → no edge. Acceptance: new asserts pass.

📅 Opened Oct 4, 2026💬 0 comments
Quality: 75/100Contribute

Good first issue. #4006's --previous restores previous merged communities; the removed-node case (a node in the previous merge but gone from current inputs must not be resurrected) is guaranteed by the loop but untested. Where: tests/test_merge_graphs_cli.py What: build a previous merged graph with an extra node, re-merge inputs that no longer contain it, assert the node is absent from the output. Acceptance: new test passes.

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

Good first issue. #3976 resolves recv?.M(); the this-receiver arm (this?.M()) isn't directly asserted. Where: tests/test_csharp_member_calls.py What: add a case with this?.Save() inside a class and assert it resolves like this.Save(). Acceptance: new test passes.

📅 Opened Oct 4, 2026💬 0 comments
Quality: 75/100Contribute
Looking for more Python beginner tasks?Explore Python 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 Graphify-Labs/graphify

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

Frequently Asked Questions - Contributing to Graphify-Labs/graphify

01

Is Graphify-Labs/graphify welcoming to first-time open-source contributors?

Graphify-Labs/graphify has a recorded first-timer success rate of 9.2%. Repositories ranked Solid 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 ~8 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 51.7 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 51.7 places Graphify-Labs/graphify in the Solid tier.

04

What is the external contributor pull request merge rate for Graphify-Labs/graphify?

The external pull request merge rate is 7.8%. 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 Graphify-Labs/graphify?

Yes, Graphify-Labs/graphify currently has 21 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 Graphify-Labs/graphify 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.