z00m128/sjasmplus - Open Source PR Review Scorecard

Command-line cross-compiler of assembly language for Z80 CPU.

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

External PR Merge Rate: 51%

Response Time: 7h

First Timer Success: -

Frequently Asked Questions

Is z00m128/sjasmplus welcoming to first-time open-source contributors?

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

What does the 47.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 47.5 places z00m128/sjasmplus in the B tier.

What is the external contributor pull request merge rate for z00m128/sjasmplus?

The external contributor pull request merge rate for z00m128/sjasmplus is 51.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in z00m128/sjasmplus?

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

z00m128
z00m128/sjasmplusB•Solid462
GitHub
Back to Explorer
z00m128

z00m128/sjasmplus

462
Active (30d)B•Solid(48/100)ASAssembly

Command-line cross-compiler of assembly language for Z80 CPU.

GitHub
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%

Active maintainer team in z00m128/sjasmplus welcoming community pull requests and bug fixes.

Top PR Submission Do's

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

Average Response Latency

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

Merge Efficiency
51.4%
Moderate 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
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
51.4%
Merge Gauge
0.0%
1st-Timer
Community Vibe45/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

The main goal is to have official package in Debian distro (and other Debian-based Linux distros over time) This is follow up on work done in #267 Current status: .deb files can be built, pass lintian checks, salsa CI builds and runs all jobs of its pipeline, packaging how-to and helper files are established and it should be reasonably easy to keep the package up to date in future. To test current .deb package you can download it from salsa CI build or build yourself from salsa repository (or mentors site if it's still available there). Initial non-formal feedback from one of Debian Developers was "RTFM, start from scratch" - which I have still not a slightest idea why/what/how to change. So this is stalled until we get better info what could be improved or decide to go ahead with current state and try harder to find mentor/sponsor. TODO: get Debian mentor who will review and provide constructive feedback how to make the package acceptable get Debian sponsor for upload (open "reques

📅 Opened Jun 8, 2026💬 0 comments
Quality: 80/100Contribute

figure out what is the current best practice to sign releases on GitHub check also Debian's wiki and finalize plan some reddit list of key servers in case we will publish keys there prepare tooling/how-to sign next release adjust debian packaging repo (file debian/watch) to check signatures

📅 Opened Jun 7, 2026💬 1 comment
Quality: 65/100Contribute
Looking for more Assembly beginner tasks?Explore Assembly 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 z00m128/sjasmplus

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

Frequently Asked Questions - Contributing to z00m128/sjasmplus

01

Is z00m128/sjasmplus welcoming to first-time open-source contributors?

z00m128/sjasmplus 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 ~7 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 47.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 47.5 places z00m128/sjasmplus in the Solid tier.

04

What is the external contributor pull request merge rate for z00m128/sjasmplus?

The external pull request merge rate is 51.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 z00m128/sjasmplus?

Yes, z00m128/sjasmplus 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 z00m128/sjasmplus 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.