fedify-dev/hollo - Open Source PR Review Scorecard

Federated single-user microblogging software

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

External PR Merge Rate: 95%

Response Time: 9d

First Timer Success: 100%

Frequently Asked Questions

Is fedify-dev/hollo welcoming to first-time open-source contributors?

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

What does the 46.1 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 46.1 places fedify-dev/hollo in the B tier.

What is the external contributor pull request merge rate for fedify-dev/hollo?

The external contributor pull request merge rate for fedify-dev/hollo is 94.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in fedify-dev/hollo?

fedify-dev/hollo currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

fedify-dev
fedify-dev/holloB•Solid492
GitHub
Back to Explorer
fedify-dev

fedify-dev/hollo

492
InactiveB•Solid(46/100)TypeScript

Federated single-user microblogging software

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
6.0/10
Patience Score
6.7/10
Nitpick Rate
52%

Rigorous architecture standards (80% critical review signals). Ensure PRs strictly follow guidelines before requesting review in fedify-dev/hollo.

Top PR Submission Do's

  • •Verify all existing package test suites run cleanly
  • •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 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
94.7%
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
CRITICAL BUS FACTOR
Single maintainer
No active GitHub maintainers found (may review internally on Gerrit or internal tools)
Diagnostic Health HUD
94.7%
Merge Gauge
100.0%
1st-Timer
Community Vibe68/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

With Hollo 0.70, search has been greatly expanded, and includes search filters similar to what Mastodon has available when Elastisearch has been installed on the server, including has:media, is:sensitive and others. There's a few more filters that Hollo should consider incorporating. These exist as well with Mastodon, just not as well known since they don't appear in the Web UI's search instructions. See the Search Options in Mastodon here: https://github.com/mastodon/mastodon/blob/29ec2cd18678d2ca2d68f831c1d6252ceb94c363/app/models/concerns/status/search_concern.rb#L35 This includes these filters to consider adding: has:image has:video has:audio has:link has:embed is:quote Note that is:quote doesn't seem to do what you'd expect right now on mastodon.social, at least it's not bringing back true post quotes that Mastodon added in recent versions. And, since Hollo doesn't generate link previews (right?) I'm not sure has:embed or has:link would work (maybe on external posts?) I have a re

📅 Opened Jan 25, 2026💬 2 comments
Quality: 70/100Contribute

Hollo can't get follower-only post from Misskey instance. Not only notification but also timeline cannot retrive that post. Searching exact post url also doesn't work. hollo 0.6.19 Misskey 2025.10.2 custom

📅 Opened Jan 23, 2026💬 2 comments
Quality: 55/100Contribute
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 fedify-dev/hollo

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

Frequently Asked Questions - Contributing to fedify-dev/hollo

01

Is fedify-dev/hollo welcoming to first-time open-source contributors?

fedify-dev/hollo has a recorded first-timer success rate of 100.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 ~8 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 46.1 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 46.1 places fedify-dev/hollo in the Solid tier.

04

What is the external contributor pull request merge rate for fedify-dev/hollo?

The external pull request merge rate is 94.7%. 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 fedify-dev/hollo?

Yes, fedify-dev/hollo currently has 2 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 fedify-dev/hollo 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.