shaobeichen/dsh-pocket - Open Source PR Review Scorecard

把 DeepSeek Harness 装进你的口袋:电脑上跑 dsh web,手机扫码即同步访问(局域网 + 公网,实时同屏)Put DeepSeek Harness in your pocket: run dsh web on your computer and access it synchronously by scanning a QR code on your phone (LAN + public network, real‑time screen mirroring)

C-Rank Grade: C (Moderate) - 39/100

External PR Merge Rate: 17%

Response Time: 8d

First Timer Success: -

Frequently Asked Questions

Is shaobeichen/dsh-pocket welcoming to first-time open-source contributors?

shaobeichen/dsh-pocket has a recorded first-timer success rate of 0.0%. Repositories ranked C 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 shaobeichen/dsh-pocket respond to incoming external pull requests in approximately 202.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 39.1 C-Rank™ score (C 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 39.1 places shaobeichen/dsh-pocket in the C tier.

What is the external contributor pull request merge rate for shaobeichen/dsh-pocket?

The external contributor pull request merge rate for shaobeichen/dsh-pocket is 16.7%, based on public PR activity from non-core contributors.

Are there Good First Issues available in shaobeichen/dsh-pocket?

shaobeichen/dsh-pocket does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

shaobeichen
shaobeichen/dsh-pocketC•Moderate1.6k
GitHub
Back to Explorer
shaobeichen

shaobeichen/dsh-pocket

1,621
InactiveC•Moderate(39/100)Low Sample (<20 PRs)JavaScript

把 DeepSeek Harness 装进你的口袋:电脑上跑 dsh web,手机扫码即同步访问(局域网 + 公网,实时同屏)Put DeepSeek Harness in your pocket: run dsh web on your computer and access it synchronously by scanning a QR code on your phone (LAN + public network, real‑time screen mirroring)

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Architecture Gatekeeper

Warmth Score
6.9/10
Patience Score
7.8/10
Nitpick Rate
30%

Strict review standards in shaobeichen/dsh-pocket. Ensure PR scope matches issue requirements closely before requesting review.

What Contributors Actually Say

Discussions in shaobeichen/dsh-pocket 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

  • •Call out API, migration, or compatibility impact clearly
  • •Link the issue and include reproduction context in the PR
  • •Add or update tests for changed behavior before requesting review

Top PR Friction Pitfalls (Don'ts)

  • •Do not hide breaking changes in implementation details
  • •Do not open context-free PRs
  • •Do not leave requested test coverage unresolved
Response Velocity
8 days+
Standard maintainer review cycle

Average Response Latency

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

Merge Efficiency
16.7%
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
3 core
Small core review team
Diagnostic Health HUD
16.7%
Merge Gauge
0.0%
1st-Timer
Community Vibe7/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for shaobeichen/dsh-pocket.

View all good first issues directly on GitHub

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 shaobeichen/dsh-pocket

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

Frequently Asked Questions - Contributing to shaobeichen/dsh-pocket

01

Is shaobeichen/dsh-pocket welcoming to first-time open-source contributors?

shaobeichen/dsh-pocket has a recorded first-timer success rate of 0.0%. Repositories ranked Moderate 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 ~8 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 39.1 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 39.1 places shaobeichen/dsh-pocket in the Moderate tier.

04

What is the external contributor pull request merge rate for shaobeichen/dsh-pocket?

The external pull request merge rate is 16.7%. 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 shaobeichen/dsh-pocket?

shaobeichen/dsh-pocket 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 shaobeichen/dsh-pocket 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.