Dapr SDK for Javascript
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 22%
Response Time: -
First Timer Success: 50%
dapr/js-sdk has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in dapr/js-sdk 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.
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 47.6 places dapr/js-sdk in the B tier.
The external contributor pull request merge rate for dapr/js-sdk is 22.2%, based on public PR activity from non-core contributors.
dapr/js-sdk currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in dapr/js-sdk. Reviews community pull requests with focus on project quality.
Discussions in dapr/js-sdk focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/dapr/js-sdk?utm_source=github&utm_medium=badge)
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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (28% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Summary The Dapr runtime has promoted the BulkPublishEventAlpha1 RPC to the stable BulkPublishEvent endpoint. The JS SDK still targets the alpha1 variant in both its gRPC and HTTP implementations. We need to migrate to the stable API while maintaining backward compatibility during a deprecation period. Current State The SDK currently uses the alpha1 endpoints: gRPC client (src/implementation/Client/GRPCClient/pubsub.ts): calls client.bulkPublishEventAlpha1(...) via ConnectRPC HTTP client (src/implementation/Client/HTTPClient/pubsub.ts): hits the v1.0-alpha1/publish/bulk/{pubSubName}/{topic} endpoint Proto definition (src/proto/dapr/proto/runtime/v1/dapr.proto): defines both BulkPublishEventAlpha1 (alpha) and BulkPublishEvent (stable) ConnectRPC stubs (src/proto/dapr/proto/runtime/v1/dapr_connect.js): only exposes bulkPublishEventAlpha1 The stable BulkPublishEvent RPC is already defined in the proto but is not yet wired up in the ConnectRPC service definition or called from the SDK. P
Summary The Dapr runtime exposes a DeleteBulkState RPC that allows deleting multiple state keys in a single call, but the JavaScript SDK does not currently expose this capability. Users must loop and call delete() individually for each key — losing atomicity and incurring extra round-trips. Motivation Proto parity: The DeleteBulkState RPC is defined in dapr.proto and the DeleteBulkStateRequest message is fully generated in both the ConnectRPC and legacy gRPC stubs. Consistency: We already expose getBulk for batch reads; a symmetric deleteBulk for batch deletes matches user expectations. Performance: Batch deletion in a single RPC call reduces latency and allows the state store to optimise the operation. Other SDKs: The Go, Python, .NET, and Java Dapr SDKs all expose bulk-delete methods. Proposed API Surface // IClientState interface addition: deleteBulk( storeName: string, keys: KeyValuePairType[], // key + optional etag/metadata per item options?: StateDeleteBulkOptions ):
Update the Conversation (Alpha2) client to support the latest API surface so it matches the Conversation API reference. For the request add: responseFormat – Optional. Structured output via a JSON Schema object promptCacheRetention – Optional. Prompt cache retention. For the response add: model – Optional. Model identifier used for the completion. usage – Optional. Token usage Reference: Proto/API definitions: Check the ai.proto file changes in this PR https://github.com/dapr/dapr/pull/9316/changes#diff-cc02342970a5222eef2c5aee936883611b8457feb8d3afd80763c3ebd93e3c5e Docs PR: dapr/docs#5027 Go SDK: dapr/go-sdk#801 Python SDK: dapr/python-sdk#902
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 dapr/js-sdk, 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 dapr/js-sdk acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 22.2% were successfully merged into the primary branch.
dapr/js-sdk has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 47.6 places dapr/js-sdk in the Solid tier.
The external pull request merge rate is 22.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, dapr/js-sdk currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for dapr/js-sdk 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.