mholt/archives - Open Source PR Review Scorecard

Cross-platform library to create & extract archives, compress & decompress files, and walk virtual file systems across various formats

C-Rank Grade: D (Risky) - 8/100

External PR Merge Rate: -

Response Time: -

First Timer Success: -

Frequently Asked Questions

Is mholt/archives welcoming to first-time open-source contributors?

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

What does the 7.5 C-Rank™ score (D 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 7.5 places mholt/archives in the D tier.

What is the external contributor pull request merge rate for mholt/archives?

The external contributor pull request merge rate for mholt/archives is 0.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in mholt/archives?

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

mholt
mholt/archivesD•Risky446
GitHub
Back to Explorer
mholt

mholt/archives

446
InactiveD•Risky(8/100)Low Sample (<20 PRs)Go

Cross-platform library to create & extract archives, compress & decompress files, and walk virtual file systems across various formats

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Empathetic Technical Mentor

Warmth Score
7.5/10
Patience Score
8.2/10
Nitpick Rate
20%

Collaborative maintainer environment in mholt/archives. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in mholt/archives 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

  • •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
-
No reviewer activity recorded

Average Response Latency

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

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

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

What would you like to have changed? Add support for unzipping archive files (other than RAR) that are split into multiple parts Why is this feature a useful, necessary, and/or important addition to this project? Usually, zip files that are sent over emails are split into multiple part in order to avoid size limit on attachments. In order to unzip them, we need to put all of the parts together. Usually these files are ordered by their number on their extension, for example: .zip, .z01, .z02, etc. What alternatives are there, or what are you doing in the meantime to work around the lack of this feature? For now, I use MacOS's native zip and unzip command, which is provided by libzip. I usually use these command in order to unzip them: zip -s- img-pt.zip -O combined.zip unzip combined.zip Also, I found an alternative command using 7zip: 7z x img-pt.zip Please link to any relevant issues, pull requests, or other discussions. I notice that we already supports unarchiving RAR files that a

📅 Opened Apr 24, 2026💬 3 comments
Quality: 45/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 mholt/archives

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

Frequently Asked Questions - Contributing to mholt/archives

01

Is mholt/archives welcoming to first-time open-source contributors?

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

03

What does the 7.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 7.5 places mholt/archives in the Risky tier.

04

What is the external contributor pull request merge rate for mholt/archives?

The external pull request merge rate is 0.0%. 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 mholt/archives?

Yes, mholt/archives currently has 1 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 mholt/archives 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.