stdlib-js/stdlib - Open Source PR Review Scorecard

✨ The fundamental numerical library for JavaScript and TypeScript. ✨                   ⭐️ Star to support our work!

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

External PR Merge Rate: 72%

Response Time: -

First Timer Success: 64%

Frequently Asked Questions

Is stdlib-js/stdlib welcoming to first-time open-source contributors?

stdlib-js/stdlib has a recorded first-timer success rate of 63.9%. 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 stdlib-js/stdlib 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 69.3 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 69.3 places stdlib-js/stdlib in the A tier.

What is the external contributor pull request merge rate for stdlib-js/stdlib?

The external contributor pull request merge rate for stdlib-js/stdlib is 72.2%, based on public PR activity from non-core contributors.

Are there Good First Issues available in stdlib-js/stdlib?

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

stdlib-js
stdlib-js/stdlibA•Welcoming6.0k
GitHub
Back to Explorer
stdlib-js

stdlib-js/stdlib

5,998
Active (30d)A•Welcoming(69/100)JavaScript

✨ The fundamental numerical library for JavaScript and TypeScript. ✨                   ⭐️ Star to support our work!

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
6.2/10
Patience Score
6.9/10
Nitpick Rate
49%

Established JavaScript ecosystem in stdlib-js/stdlib. Maintains structured code review standards for external contributors.

Top PR Submission Do's

  • •Ensure code complies with JavaScript style conventions
  • •Keep PRs scoped and well-documented
  • •Include relevant test coverage for changes

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
  • •Do not mix unrelated refactors with feature work
Response Velocity
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
72.2%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
63.9%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
34 core
Highly collaborative maintainer core
Diagnostic Health HUD
72.2%
Merge Gauge
63.9%
1st-Timer
Community Vibe48/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

JavaScript Linting Failures Linting failures were detected in the automated JavaScript lint workflow run. Workflow Details Run: https://github.com/stdlib-js/stdlib/actions/runs/38007375027 Type: JavaScript Linting Date: 2026-10-10 00:20:23 UTC Error Details make[1]: Entering directory '/home/runner/work/stdlib/stdlib' Linting file: lib/node_modules/@stdlib/ndarray/base/count-falsy/lib/10d.js Linting file: lib/node_modules/@stdlib/ndarray/base/unary-reduce-strided1d-by/lib/2d.js Linting file: lib/node_modules/@stdlib/math/base/special/kernel-betaincinv/lib/polyval_co12.js Linting file: lib/node_modules/@stdlib/blas/ext/base/ctriu2tril/lib/main.js Linting file: lib/node_modules/@stdlib/ndarray/base/assert/is-boolean-index-data-type/lib/main.js Linting file: lib/node_modules/@stdlib/lapack/base/shared/lib/main.js Linting file: lib/node_modules/@stdlib/stats/base/dists/anglit/skewness/lib/index.js Linting file: lib/node_modules/@stdlib/string/right-pad/lib/index.js Linting file:

📅 Opened Oct 10, 2026💬 2 comments
Quality: 85/100Contribute

C Linting Failures Linting failures were detected in the automated lint workflow run. Workflow Details Run: https://github.com/stdlib-js/stdlib/actions/runs/37862817489 Type: C Linting Date: 2026-10-09 00:26:11 UTC Error Details lib/node_modules/@stdlib/number/int32/base/mul/test/fixtures/c/runner.c:143:36: style: Parameter 'x' can be declared as pointer to const [constParameterPointer] void i32_to_f64( double *out, int *x, unsigned int len ) { ^ lib/node_modules/@stdlib/number/int32/base/mul/test/fixtures/c/runner.c:158:36: style: Parameter 'x' can be declared as pointer to const [constParameterPointer] void f64_to_i32( int *out, double *x, unsigned int len ) { ^ lib/node_modules/@stdlib/number/int32/base/mul/test/fixtures/c/runner.c:262:21: style: Parameter 'a' can be declared as pointer to const [constParameterPointer] void generate( int *a, int *b, const unsigned int len, const char *name ) {

📅 Opened Oct 9, 2026💬 1 comment
Quality: 75/100Contribute

JavaScript Linting Failures Linting failures were detected in the automated JavaScript lint workflow run. Workflow Details Run: https://github.com/stdlib-js/stdlib/actions/runs/37862817489 Type: JavaScript Linting Date: 2026-10-09 00:21:12 UTC Error Details make[1]: Entering directory '/home/runner/work/stdlib/stdlib' Linting file: lib/node_modules/@stdlib/strided/base/mskunary-dtype-signatures/examples/index.js Linting file: lib/node_modules/@stdlib/math/base/special/hacoversin/examples/index.js hacoversin(4.9631) = 0.9844 hacoversin(6.0915) = 0.5953 hacoversin(2.3838) = 0.1563 hacoversin(3.5994) = 0.7210 hacoversin(3.9334) = 0.8558 hacoversin(4.7448) = 0.9997 hacoversin(5.1497) = 0.9529 hacoversin(1.6682) = 0.0024 hacoversin(0.9702) = 0.0875 hacoversin(2.0651) = 0.0598 hacoversin(4.9790) = 0.9823 hacoversin(0.2761) = 0.3637 hacoversin(2.2398) = 0.1078 hacoversin(4.6990) = 1.0000 hacoversin(3.3736) = 0.6150 hacoversin(3.1808) = 0.5196 hacoversin(2.8966) = 0.3787 hacoversin(5.3726)

📅 Opened Oct 9, 2026💬 3 comments
Quality: 85/100Contribute

JavaScript Linting Failures Linting failures were detected in the automated JavaScript lint workflow run. Workflow Details Run: https://github.com/stdlib-js/stdlib/actions/runs/37705703501 Type: JavaScript Linting Date: 2026-10-08 00:15:22 UTC Error Details make[1]: Entering directory '/home/runner/work/stdlib/stdlib' Linting file: lib/node_modules/@stdlib/repl/server/lib/defaults.js /home/runner/work/stdlib/stdlib/lib/node_modules/@stdlib/repl/server/lib/defaults.js 47:15 error The 'repl.REPL_MODE_SLOPPY' is still an experimental feature and is not supported until Node.js 4.0.0. The configured version range is '>=0.12.18' n/no-unsupported-features/node-builtins ✖ 1 problem (1 error, 0 warnings) Linting failed. Linting file: lib/node_modules/@stdlib/constants/float16/sqrt-two-pi/lib/index.js Linting file: lib/node_modules/@stdlib/blas/ext/base/swxdy/lib/ndarray.native.js Linting file: lib/node_modules/@stdlib/assert/is-iterator-like/lib/index.js Linting file: lib/node_mo

📅 Opened Oct 8, 2026💬 1 comment
Quality: 50/100Contribute

JavaScript Linting Failures Linting failures were detected in the automated JavaScript lint workflow run. Workflow Details Run: https://github.com/stdlib-js/stdlib/actions/runs/37549938275 Type: JavaScript Linting Date: 2026-10-07 00:18:24 UTC Error Details make[1]: Entering directory '/home/runner/work/stdlib/stdlib' Linting file: lib/node_modules/@stdlib/blas/ext/base/gsum/lib/index.js Linting file: lib/node_modules/@stdlib/strided/napi/zmap/lib/main.js Linting file: lib/node_modules/@stdlib/random/streams/triangular/lib/validate.js Linting file: lib/node_modules/@stdlib/ndarray/base/unary-by/lib/6d_accessors.js Linting file: lib/node_modules/@stdlib/math/base/special/trunc2f/lib/main.js Linting file: lib/node_modules/@stdlib/stats/base/ndarray/midrange-by/lib/main.js Linting file: lib/node_modules/@stdlib/ndarray/concat1d/lib/resolve_dtypes.js Linting file: lib/node_modules/@stdlib/number/float64/base/add/lib/main.js Linting file: lib/node_modules/@stdlib/assert/is-boolea

📅 Opened Oct 7, 2026💬 1 comment
Quality: 50/100Contribute
Looking for more JavaScript beginner tasks?Explore JavaScript 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 stdlib-js/stdlib

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

Frequently Asked Questions - Contributing to stdlib-js/stdlib

01

Is stdlib-js/stdlib welcoming to first-time open-source contributors?

stdlib-js/stdlib has a recorded first-timer success rate of 63.9%. 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 ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 69.3 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 69.3 places stdlib-js/stdlib in the Welcoming tier.

04

What is the external contributor pull request merge rate for stdlib-js/stdlib?

The external pull request merge rate is 72.2%. 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 stdlib-js/stdlib?

Yes, stdlib-js/stdlib currently has 21 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 stdlib-js/stdlib 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.