Han-1413141/dsh-cost-meter - Open Source PR Review Scorecard

DeepSeek Harness session cost meter plugin: session/daily cost, budget, history, OpenCode Go quota, official & custom-provider balance, Codex-like token heatmap, peak/off-peak pricing with pre-switch popup & system-notification alerts, official price sync, 90+ model pricing catalog, Coding Plan quota queries (7 vendors), bilingual zh/en UI

C-Rank Grade: B (Solid) - 59/100

External PR Merge Rate: 75%

Response Time: <1h

First Timer Success: 100%

Frequently Asked Questions

Is Han-1413141/dsh-cost-meter welcoming to first-time open-source contributors?

Han-1413141/dsh-cost-meter has a recorded first-timer success rate of 100.0%. Repositories ranked B 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 Han-1413141/dsh-cost-meter respond to incoming external pull requests in approximately 0.4 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 59.1 C-Rank™ score (B 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 59.1 places Han-1413141/dsh-cost-meter in the B tier.

What is the external contributor pull request merge rate for Han-1413141/dsh-cost-meter?

The external contributor pull request merge rate for Han-1413141/dsh-cost-meter is 75.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in Han-1413141/dsh-cost-meter?

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

Han-1413141
Han-1413141/dsh-cost-meterBSolid198
GitHub
Back to Explorer
Han-1413141

Han-1413141/dsh-cost-meter

198
BSolid(59/100)JavaScript

DeepSeek Harness session cost meter plugin: session/daily cost, budget, history, OpenCode Go quota, official & custom-provider balance, Codex-like token heatmap, peak/off-peak pricing with pre-switch popup & system-notification alerts, official price sync, 90+ model pricing catalog, Coding Plan quota queries (7 vendors), bilingual zh/en UI

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.8/10
Patience Score
8.8/10
Nitpick Rate
25%

Highly welcoming maintainers in Han-1413141/dsh-cost-meter. Prompt code reviews with positive guidance for new contributors.

What Contributors Actually Say

Discussions in Han-1413141/dsh-cost-meter 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

  • Link the issue and include reproduction context in the PR
  • Call out API, migration, or compatibility impact clearly
  • Update docs or README when behavior changes

Top PR Friction Pitfalls (Don'ts)

  • Do not open context-free PRs
  • Do not hide breaking changes in implementation details
  • Do not ship user-facing changes without matching docs
Response Velocity
<1 hour
⚡ Fast reviewer response

Average Response Latency

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

Merge Efficiency
75.0%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

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

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
1 core
Single maintainer review bottleneck
Diagnostic Health HUD
75.0%
Merge Gauge
100.0%
1st-Timer
Community Vibe90/100

Embed C-Rank Badge

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

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

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for Han-1413141/dsh-cost-meter.

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 Han-1413141/dsh-cost-meter

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

Frequently Asked Questions - Contributing to Han-1413141/dsh-cost-meter

01

Is Han-1413141/dsh-cost-meter welcoming to first-time open-source contributors?

Han-1413141/dsh-cost-meter has a recorded first-timer success rate of 100.0%. Repositories ranked Solid 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 ~<1 hour. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 59.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 59.1 places Han-1413141/dsh-cost-meter in the Solid tier.

04

What is the external contributor pull request merge rate for Han-1413141/dsh-cost-meter?

The external pull request merge rate is 75.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 Han-1413141/dsh-cost-meter?

Han-1413141/dsh-cost-meter 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 Han-1413141/dsh-cost-meter 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.