Rich-powered CLI that breaks each HTTP request into DNS, connect, TLS, wait, and transfer phases with waterfall timelines, compact summaries, or metrics-only output.
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: 61%
Response Time: 10d
First Timer Success: -
ozeranskii/httptap has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ozeranskii/httptap respond to incoming external pull requests in approximately 235.6 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 45.9 places ozeranskii/httptap in the B tier.
The external contributor pull request merge rate for ozeranskii/httptap is 61.1%, based on public PR activity from non-core contributors.
ozeranskii/httptap does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Active maintainer team in ozeranskii/httptap welcoming community pull requests and bug fixes.
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/ozeranskii/httptap?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~153 hours (76% approval). Large PRs (>500 lines) take ~1131 hours (28% approval). Keep your diff compact for rapid review.
Feature Category Testing/Development (testing tools, dev experience) Problem Statement astral-sh/ruff-action in ci.yml:31-38 has no version, so it resolves ruff>=0.16.4 from pyproject.toml to the latest release (CI log: "Found version for ruff ... >=0.16.4", downloads 0.16.8). With select = ["ALL"], a new ruff release can fail CI without repository changes and diverge from the locked ruff. Proposed Solution Pin version to the locked ruff (kept in sync by Dependabot), or run uv run ruff so CI uses uv.lock. Alternatives Considered No response Examples - uses: astral-sh/ruff-action@<sha> with: version: "0.16.8" args: check --output-format=github . Priority Would improve my workflow Contribution I would be willing to submit a PR for this feature I need guidance on how to implement this I can help test this feature Checklist I have searched existing issues and discussions This feature aligns with httptap's purpose (HTTP diagnostics/performance analysis)
Documentation Type CONTRIBUTING.md Issue Type Outdated/incorrect information Description Release steps describe manual tagging and uv build && uv publish, but releases are automated by .github/workflows/release.yml. docs/development/release.md keeps a manual git tag / uv publish section next to the automated flow. Coverage is stated as "~90%"; actual coverage is 100%. check-yaml hook and BOM removal are mentioned but not configured in .pre-commit-config.yaml. Location File: CONTRIBUTING.md, lines 72, 89, 167, 397-399 File: docs/development/release.md, lines 234-248 Suggested Improvement Point release instructions to the Release workflow, remove the manual publish steps, update the coverage figure and the hook list. Contribution I would be willing to submit a PR to fix this documentation Checklist I have checked the latest version of the documentation
Documentation Type SECURITY.md Issue Type Outdated/incorrect information Description The supported versions table lists 0.4.x as the only supported series, while the current release is 0.6.1. Location File: SECURITY.md, lines 7-10 Suggested Improvement List the current minor series (0.6.x) as supported and older ones as unsupported. Contribution I would be willing to submit a PR to fix this documentation Checklist I have checked the latest version of the documentation
Bug Description pyproject.toml addopts always enable --cov, --cov-branch, html/xml reports and junit. .github/workflows/codspeed.yml:52 runs pytest tests/test_benchmarks.py --codspeed without --no-cov, so benchmarks are measured with the coverage tracer active, which skews results. Steps to Reproduce Compare [tool.pytest.ini_options].addopts in pyproject.toml with the run step in .github/workflows/codspeed.yml. Expected Behavior Benchmarks run without coverage (--no-cov) and without writing reports. Actual Behavior run: uv run --no-dev --group test pytest tests/test_benchmarks.py --codspeed addopts = ["--strict-markers", "--strict-config", "--cov=httptap", "--cov-report=term-missing", "--cov-report=html", "--cov-report=xml", "--cov-branch", "--junitxml=junit.xml", ...] Environment httptap version: main @ 3591f89 Python version: N/A OS: GitHub Actions (ubuntu-latest) Installation method: N/A Additional Context No response Checklist I have searched existing issues to avo
Bug Description .github/workflows/docs.yml:4-15 triggers only on docs/**, mkdocs.yml and the workflow file. mkdocstrings renders the API reference from httptap/**, and docs dependencies live in pyproject.toml/uv.lock, so docstring changes are never redeployed and Dependabot bumps of mkdocs packages are never built with --strict. Steps to Reproduce Open .github/workflows/docs.yml, on.push.paths / on.pull_request.paths. Expected Behavior Paths include httptap/**, pyproject.toml, uv.lock. Actual Behavior paths: - 'docs/**' - 'mkdocs.yml' - '.github/workflows/docs.yml' Environment httptap version: main @ 3591f89 Python version: N/A OS: GitHub Actions (ubuntu-latest) Installation method: N/A Additional Context No response Checklist I have searched existing issues to avoid duplicates I have provided all requested information above This is not a security vulnerability (use Security Advisories for that)
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 ozeranskii/httptap, 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 ozeranskii/httptap acknowledge new external contributions in approximately 9 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 61.1% were successfully merged into the primary branch.
ozeranskii/httptap has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 days+. 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 45.9 places ozeranskii/httptap in the Solid tier.
The external pull request merge rate is 61.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
ozeranskii/httptap does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for ozeranskii/httptap 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.