asciimoo/hister - Open Source PR Review Scorecard

Your own search engine

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

External PR Merge Rate: 70%

Response Time: 6d

First Timer Success: 100%

Frequently Asked Questions

Is asciimoo/hister welcoming to first-time open-source contributors?

asciimoo/hister 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 asciimoo/hister respond to incoming external pull requests in approximately 134.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 60.7 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 60.7 places asciimoo/hister in the A tier.

What is the external contributor pull request merge rate for asciimoo/hister?

The external contributor pull request merge rate for asciimoo/hister is 69.9%, based on public PR activity from non-core contributors.

Are there Good First Issues available in asciimoo/hister?

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

asciimoo
asciimoo/histerA•Welcoming5.8k
GitHub
Back to Explorer
asciimoo

asciimoo/hister

5,789
InactiveA•Welcoming(61/100)Go

Your own search engine

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.2/10
Patience Score
8.4/10
Nitpick Rate
35%

Highly welcoming maintainers in asciimoo/hister. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
5 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
69.9%
Moderate PR acceptance rate

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
30 core
Highly collaborative maintainer core
Diagnostic Health HUD
69.9%
Merge Gauge
100.0%
1st-Timer
Community Vibe58/100

Embed C-Rank Badge

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

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

Active Good First Issues (4)

View on GitHub

Looking for a logo/mascot for Hister that gives the project a unique personality. I prefer simple, minimal, vector style drawings - probably an adorable animal/creature would be a nice choice. Not sure which one, as far as I know neither is the symbol of Hister's unique values like self hosting or privacy. =] As reference, I find Radu Lucian's art amazing, especially the more simplistic drawings like https://dribbble.com/shots/19132537-Duck-Logo . I'd be grateful for contributions. I'm happy to reference the artist in the project README and on our website.

📅 Opened May 18, 2026💬 7 comments
Quality: 70/100Contribute

Hello, I've noticed there are a lot of issues when building a Docker image using GitHub. Over the past few months, GitHub's service has been deteriorating at an alarming rate. It might be a good idea to have a more reliable alternative—a Docker image containing all the commits you make to a Git repository. I don’t know of many alternatives besides hub.docker.com, but I’ve seen that Miniflux uses multiple image repositories (GitHub, Docker, Quay.io). I'm throwing out the idea. sources: https://github.com/asciimoo/hister/actions/workflows/docker-publish.yml?query=is%3Afailure+is%3Askipped+is%3Acancelled https://dbushell.com/2026/04/29/github-is-sinking/ https://miniflux.app/docs/docker.html

📅 Opened May 12, 2026💬 23 comments
Quality: 70/100Contribute

This is a meta issue raising awareness to contribute to existing extractors or add new ones Extractors are modules that provide custom, content-specific document parsing or rendering functions to enhance the data quality of Hister. Find more details about how extractors work here or check out our existing extractors. We need as many extractors as possible to enhance Histers data processing. Write a comment below either if you can recommend new extractors or want to work on one. I'll update the following list. Possible extractor ideas Video information extractor using yt-dlp (@FlameFlag) GitHub project information extractor General StackExchange question/answer extractor Reddit post extractor (@dinzz005) Atlassians Jira and Confluence ChatGPT (@alexferrari88) Discord extractor

📅 Opened Apr 9, 2026💬 24 comments
Quality: 70/100Contribute

This requires ~10 lines of configuration (see https://goreleaser.com/customization/homebrew/), but it does require configuring a new repo and a secret for GH actions. Distributing the binary via brew may help work around MacOS refusing to run the binary from the releases page without a signature.

📅 Opened Mar 4, 2026💬 0 comments
Quality: 15/100Contribute
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 asciimoo/hister

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

Frequently Asked Questions - Contributing to asciimoo/hister

01

Is asciimoo/hister welcoming to first-time open-source contributors?

asciimoo/hister 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 ~5 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 60.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 60.7 places asciimoo/hister in the Welcoming tier.

04

What is the external contributor pull request merge rate for asciimoo/hister?

The external pull request merge rate is 69.9%. 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 asciimoo/hister?

Yes, asciimoo/hister 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 asciimoo/hister 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.