crowdin/crowdin-api-client-js - Open Source PR Review Scorecard

JavaScript client library for Crowdin API

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

External PR Merge Rate: -

Response Time: 17d

First Timer Success: -

Frequently Asked Questions

Is crowdin/crowdin-api-client-js welcoming to first-time open-source contributors?

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

What does the 12.4 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 12.4 places crowdin/crowdin-api-client-js in the D tier.

What is the external contributor pull request merge rate for crowdin/crowdin-api-client-js?

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

Are there Good First Issues available in crowdin/crowdin-api-client-js?

crowdin/crowdin-api-client-js does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

crowdin
crowdin/crowdin-api-client-jsD•Risky139
GitHub
Back to Explorer
crowdin

crowdin/crowdin-api-client-js

139
InactiveD•Risky(12/100)Low Sample (<20 PRs)TypeScript

JavaScript client library for Crowdin API

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 crowdin/crowdin-api-client-js. Reviews community pull requests with focus on project quality.

What Contributors Actually Say

Discussions in crowdin/crowdin-api-client-js 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
16 days+
Standard maintainer review cycle

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
1 core
Single maintainer review bottleneck
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 crowdin/crowdin-api-client-js
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/crowdin/crowdin-api-client-js)](https://getmerged.abhishekco.de/crowdin/crowdin-api-client-js?utm_source=github&utm_medium=badge)

Active Good First Issues (3)

View on GitHub

The Distribution Release model returned by Get Distribution Release (GET /projects/{projectId}/distributions/{hash}/release, api.projects.distributions.release.get) and Release Distribution (POST, api.projects.distributions.release.post) now includes an optional error object: error — object with message (string); present only when the release status is failed This applies to both file-based and string-based distribution releases, in both Crowdin and Crowdin Enterprise. Client libraries should add the field to the distribution release response models so consumers can surface release failures. References: Release Distribution Get Distribution Release Crowdin Enterprise: Get Distribution Release

📅 Opened Sep 14, 2026💬 0 comments
Quality: 90/100Contribute

The Apply Pre-Translation method (POST /projects/{projectId}/pre-translations, api.projects.pre-translations.post) now supports pre-translating whole directories and branches in file-based projects, in both Crowdin and Crowdin Enterprise: New optional request fields directoryIds (array of integers) and branchIds (array of integers) — all nested files are included. fileIds is no longer required — it must be provided only when neither directoryIds nor branchIds is set. The pre-translation status/response attributes now also include directoryIds and branchIds. Additionally, the path parameter of Get Pre-Translation Status, Edit Pre-Translation, and Get Pre-Translation Report was renamed from preTranslationId to jobIdentifier (/projects/{projectId}/pre-translations/{jobIdentifier}). This is not a wire change, but generated clients and method signatures may reflect the new name. Client libraries should make fileIds optional and expose the new directoryIds/branchIds request and respons

📅 Opened Sep 14, 2026💬 0 comments
Quality: 90/100Contribute

Several updates landed on the Tasks API models that typed client libraries should pick up: New response fields: originalWordsCount (integer) on the Task model — the number of words when the task was created, preserved when source strings are later removed (wordsCount reflects the current count). Both Crowdin and Crowdin Enterprise. syncScope (nullable object: syncedWords, pendingWords, skippedWords — all integers) on the Enterprise task models (project tasks, organization task list, user tasks). It is null when the task is fully synced, not shared, or the counterpart is unavailable — Crowdin Enterprise only. Type fixes: Task creatorId corrected from string to integer. Enterprise Add Task forms: status corrected from integer to string enum (todo, in_progress). Edit Project Task (Enterprise): the inter-organizational task patch path enum gains /generateCostEstimate, /generateTranslationCost, and /reportSettingsTemplateId. Affected endpoints: List/Add/Get/Edit Project Task (api.

📅 Opened Sep 14, 2026💬 0 comments
Quality: 90/100Contribute
Looking for more TypeScript beginner tasks?Explore TypeScript 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 crowdin/crowdin-api-client-js

When evaluating whether to contribute to crowdin/crowdin-api-client-js, 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 crowdin/crowdin-api-client-js acknowledge new external contributions in approximately 16 days+. 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 crowdin/crowdin-api-client-js

01

Is crowdin/crowdin-api-client-js welcoming to first-time open-source contributors?

crowdin/crowdin-api-client-js 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 ~16 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 12.4 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 12.4 places crowdin/crowdin-api-client-js in the Risky tier.

04

What is the external contributor pull request merge rate for crowdin/crowdin-api-client-js?

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 crowdin/crowdin-api-client-js?

crowdin/crowdin-api-client-js does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for crowdin/crowdin-api-client-js 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.