V library to develop Artificial Intelligence and High-Performance Scientific Computations
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 11%
Response Time: 10h
First Timer Success: -
vlang/vsl 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.
Maintainers in vlang/vsl respond to incoming external pull requests in approximately 9.6 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 48.6 places vlang/vsl in the B tier.
The external contributor pull request merge rate for vlang/vsl is 10.5%, based on public PR activity from non-core contributors.
vlang/vsl currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in vlang/vsl welcoming community pull requests and bug fixes.
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/vlang/vsl?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 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (13% approval). Large PRs (>500 lines) take ~46 hours (15% approval). Keep your diff compact for rapid review.
No security policy exists in the repo despite wrapping native C libraries (OpenBLAS, LAPACKE, CUDA, Vulkan, HDF5, MPI). Task Create SECURITY.md with: Supported versions (latest release) Reporting process (email or GitHub Security Advisory) Response timeline expectation File New SECURITY.md
compute/ is the recommended dispatch surface for backend-agnostic GPU computing but has no README. All other GPU-related modules (vcl, cuda, vulkan) have READMEs. Task Create compute/README.md explaining: The compute abstraction layer How it dispatches to vcl/cuda/vulkan backends Available operations (element-wise, BLAS, reduce) Basic usage example Verification README links correctly to backend-specific docs
errors/errno.v, errors/errors.v, errors/strerrno.v have no test coverage. Task Add errors/errno_test.v mapping known errno integers to their string representations, and verifying error code constants are consistent. Verification v test vsl/errors passes
Three articles in docs/advanced/ are stubs: 01-mpi-parallel.md — 308 bytes 03-hdf5-io.md — 285 bytes 04-library-integration.md — 502 bytes Examples for each topic already exist (mpi, inout, external library use). Task Write real walkthroughs for each article using the existing examples as reference. Verification Follow the steps in each article to run the example Articles follow the depth of 02-opencl-gpu.md
Three modules have minimal READMEs: dist/README.md — 112 bytes noise/README.md — 2 sentences roots/README.md — 1 sentence Task Expand each README with: Module purpose and capabilities Public API listing with usage snippets Links to examples and related docs Use metrics/README.md as reference for the expected quality level. Verification Each README covers the module's full public API
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 vlang/vsl, 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 vlang/vsl acknowledge new external contributions in approximately 9 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 10.5% were successfully merged into the primary branch.
vlang/vsl 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.
The initial maintainer response time averages ~9 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 48.6 places vlang/vsl in the Solid tier.
The external pull request merge rate is 10.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, vlang/vsl currently has 8 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for vlang/vsl 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.