temporalio/sdk-typescript - Open Source PR Review Scorecard

Temporal TypeScript SDK

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

External PR Merge Rate: 54%

Response Time: -

First Timer Success: 75%

Frequently Asked Questions

Is temporalio/sdk-typescript welcoming to first-time open-source contributors?

temporalio/sdk-typescript has a recorded first-timer success rate of 75.0%. 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 temporalio/sdk-typescript 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 63.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 63.3 places temporalio/sdk-typescript in the A tier.

What is the external contributor pull request merge rate for temporalio/sdk-typescript?

The external contributor pull request merge rate for temporalio/sdk-typescript is 54.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in temporalio/sdk-typescript?

temporalio/sdk-typescript currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

temporalio
temporalio/sdk-typescriptA•Welcoming936
GitHub
Back to Explorer
temporalio

temporalio/sdk-typescript

936
Active (30d)A•Welcoming(63/100)TypeScript

Temporal TypeScript SDK

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 temporalio/sdk-typescript 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
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
54.0%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
29 core
Highly collaborative maintainer core
Diagnostic Health HUD
54.0%
Merge Gauge
75.0%
1st-Timer
Community Vibe44/100

Embed C-Rank Badge

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

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

Active Good First Issues (1)

View on GitHub

What are you really trying to do? Our production system uses a workflow worker to run about 100 distinct workflow_types. We use zod schemas to validate inputs and outputs to workflows and activities. Many of these are defined at the top level of files, all of which appear to be instantiated and have their own allocation in memory for each workflow that is in the cache. We want our production system to be able to survive bursts of workflows starting without the workers crashing. Describe the bug The workflow cache size can grow and crash the process with an out of memory error. This can be achieved with the default workflow cache settings. Our production workers use a 6GB memory request/JS heap size and would regularly see crashes due to exhausting memory as the cache size grew. It is particularly noticeable if we received a large burst of new workflows since those would all start around the same time and crashes would happen before the workflows would have a chance to complete--o

📅 Opened Jul 21, 2026💬 13 comments
Quality: 40/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 temporalio/sdk-typescript

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

Frequently Asked Questions - Contributing to temporalio/sdk-typescript

01

Is temporalio/sdk-typescript welcoming to first-time open-source contributors?

temporalio/sdk-typescript has a recorded first-timer success rate of 75.0%. 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 63.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 63.3 places temporalio/sdk-typescript in the Welcoming tier.

04

What is the external contributor pull request merge rate for temporalio/sdk-typescript?

The external pull request merge rate is 54.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 temporalio/sdk-typescript?

Yes, temporalio/sdk-typescript currently has 1 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 temporalio/sdk-typescript 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.