A flight-compliant WebAssembly interpreter.
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 83%
Response Time: 14h
First Timer Success: 70%
nasa/spacewasm has a recorded first-timer success rate of 70.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in nasa/spacewasm respond to incoming external pull requests in approximately 14.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 70.9 places nasa/spacewasm in the S tier.
The external contributor pull request merge rate for nasa/spacewasm is 83.2%, based on public PR activity from non-core contributors.
nasa/spacewasm currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in nasa/spacewasm. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/nasa/spacewasm?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~9 hours (96% approval). Large PRs (>500 lines) take ~69 hours (37% approval). Keep your diff compact for rapid review.
A 15-byte malformed module panics the decoder on 32-bit targets. Verified on a clean checkout of main @ 096c71cfa. Reader::read_vec_in (src/reader.rs:459) passes a module-supplied vector length straight to the allocator: let len = self.read_u32()?; let mut out = Vec::new_in(alloc, len)?; Vec::new_in (src/util/vec.rs:137) then unwraps the layout: unsafe { alloc.alloc(Layout::array::<T>(capacity as usize).unwrap())? } On 32-bit isize::MAX is 2147483647, so a declared length of 0xFFFFFFFF overflows the layout for any element type and the unwrap panics. It runs before alloc.alloc, so a size-limited allocator does not protect against it. The stack-based sibling already guards this: read_vec_stack (src/reader.rs:436-438) checks len and returns ValidationError::VecTooLong, which already exists and is already wired through the C API and the spec-test harness. Only the heap path skips it. read_vec feeds the type, import, function and global sections, code locals, FuncType signatures and export
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to nasa/spacewasm, 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 nasa/spacewasm acknowledge new external contributions in approximately 14 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.2% were successfully merged into the primary branch.
nasa/spacewasm has a recorded first-timer success rate of 70.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~14 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 70.9 places nasa/spacewasm in the Elite tier.
The external pull request merge rate is 83.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, nasa/spacewasm currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for nasa/spacewasm 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.