felinics/Memoh - Open Source PR Review Scorecard

✨ The open-source multi-agent platform. Every agent gets its own computer, desktop, network, and long-term memory. You can bring your own key, or host your coding agent like Claude Code, Codex and so on.

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

External PR Merge Rate: 14%

Response Time: 23h

First Timer Success: -

Frequently Asked Questions

Is felinics/Memoh welcoming to first-time open-source contributors?

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

What does the 53.5 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 53.5 places felinics/Memoh in the B tier.

What is the external contributor pull request merge rate for felinics/Memoh?

The external contributor pull request merge rate for felinics/Memoh is 14.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in felinics/Memoh?

felinics/Memoh does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

felinics
felinics/MemohB•Solid2.7k
GitHub
Back to Explorer
felinics

felinics/Memoh

2,656
Active (30d)B•Solid(53/100)Low Sample (<20 PRs)Go

✨ The open-source multi-agent platform. Every agent gets its own computer, desktop, network, and long-term memory. You can bring your own key, or host your coding agent like Claude Code, Codex and so on.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Architecture Gatekeeper

Warmth Score
7.2/10
Patience Score
8.0/10
Nitpick Rate
25%

Strict review standards in felinics/Memoh. Ensure PR scope matches issue requirements closely before requesting review.

What Contributors Actually Say

Discussions in felinics/Memoh focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Add or update tests for changed behavior before requesting review
  • •Link the issue and include reproduction context in the PR
  • •Call out API, migration, or compatibility impact clearly

Top PR Friction Pitfalls (Don'ts)

  • •Do not leave requested test coverage unresolved
  • •Do not open context-free PRs
  • •Do not hide breaking changes in implementation details
Response Velocity
22 hours
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
14.3%
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
6 core
Highly collaborative maintainer core
Diagnostic Health HUD
14.3%
Merge Gauge
0.0%
1st-Timer
Community Vibe18/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for felinics/Memoh.

View all good first issues directly on GitHub

Looking for more Go beginner tasks?Explore Go 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 felinics/Memoh

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

Frequently Asked Questions - Contributing to felinics/Memoh

01

Is felinics/Memoh welcoming to first-time open-source contributors?

felinics/Memoh has a recorded first-timer success rate of 0.0%. 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 ~22 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 53.5 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 53.5 places felinics/Memoh in the Solid tier.

04

What is the external contributor pull request merge rate for felinics/Memoh?

The external pull request merge rate is 14.3%. 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 felinics/Memoh?

felinics/Memoh 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 felinics/Memoh 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.