adoresever/graph-memory - Open Source PR Review Scorecard

Deepseek Harness、Openclaw知识图谱记忆插件。2026年4月受邀发布在清华大学讨论会。Knowledge Graph + Memory;Knowledge Graph Context Engine for OpenClaw — extracts structured triples from conversations, compresses context 75%, enables cross-session experience reuse

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

External PR Merge Rate: 36%

Response Time: 3h

First Timer Success: 25%

Frequently Asked Questions

Is adoresever/graph-memory welcoming to first-time open-source contributors?

adoresever/graph-memory has a recorded first-timer success rate of 25.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 adoresever/graph-memory respond to incoming external pull requests in approximately 3.5 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 57.4 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 57.4 places adoresever/graph-memory in the A tier.

What is the external contributor pull request merge rate for adoresever/graph-memory?

The external contributor pull request merge rate for adoresever/graph-memory is 36.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in adoresever/graph-memory?

adoresever/graph-memory does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

adoresever
adoresever/graph-memoryAWelcoming562
GitHub
Back to Explorer
adoresever

adoresever/graph-memory

562
AWelcoming(57/100)TypeScript

Deepseek Harness、Openclaw知识图谱记忆插件。2026年4月受邀发布在清华大学讨论会。Knowledge Graph + Memory;Knowledge Graph Context Engine for OpenClaw — extracts structured triples from conversations, compresses context 75%, enables cross-session experience reuse

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%

Growing TypeScript project in adoresever/graph-memory welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • Ensure code complies with TypeScript style conventions
  • Keep PRs scoped 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
3 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
36.4%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
25.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
3 core
Small core review team
Diagnostic Health HUD
36.4%
Merge Gauge
25.0%
1st-Timer
Community Vibe49/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for adoresever/graph-memory.

View all good first issues directly on GitHub

Looking for more TypeScript beginner tasks?Explore TypeScript 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 adoresever/graph-memory

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

Frequently Asked Questions - Contributing to adoresever/graph-memory

01

Is adoresever/graph-memory welcoming to first-time open-source contributors?

adoresever/graph-memory has a recorded first-timer success rate of 25.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 ~3 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 57.4 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 57.4 places adoresever/graph-memory in the Welcoming tier.

04

What is the external contributor pull request merge rate for adoresever/graph-memory?

The external pull request merge rate is 36.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 adoresever/graph-memory?

adoresever/graph-memory 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 adoresever/graph-memory 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.