daijro/camoufox - Open Source PR Review Scorecard

🦊 Anti-detect browser

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

External PR Merge Rate: 40%

Response Time: -

First Timer Success: 30%

Frequently Asked Questions

Is daijro/camoufox welcoming to first-time open-source contributors?

daijro/camoufox has a recorded first-timer success rate of 30.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 daijro/camoufox 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 61.8 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 61.8 places daijro/camoufox in the A tier.

What is the external contributor pull request merge rate for daijro/camoufox?

The external contributor pull request merge rate for daijro/camoufox is 40.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in daijro/camoufox?

daijro/camoufox does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

daijro
daijro/camoufoxA•Welcoming12.5k
GitHub
Back to Explorer
daijro

daijro/camoufox

12,497
Active (30d)A•Welcoming(62/100)Python

🦊 Anti-detect browser

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Strict Quality Architect

Warmth Score
7.2/10
Patience Score
7.7/10
Nitpick Rate
35%

Balanced & professional review environment in daijro/camoufox. Maintains strict focus on technical quality and test standards.

Top PR Submission Do's

  • •Add unit tests with >80% coverage for modified code paths
  • •Use conventional commit messages and clean branch names
  • •Link relevant GitHub issue ID in PR description pre-flight checklist

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without referencing an existing issue
  • •Do not mix refactoring and feature logic into a single commit
  • •Do not ping maintainers repeatedly within 24 hours of opening
Response Velocity
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
40.0%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
30.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
32 core
Highly collaborative maintainer core
Diagnostic Health HUD
40.0%
Merge Gauge
30.0%
1st-Timer
Community Vibe25/100

Embed C-Rank Badge

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

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

Active Good First Issues (2)

View on GitHub

## Environment - OS: Windows 11 Pro 10.0.26100 (x64) - Camoufox binary: 135.0.1-beta.24 - Python camoufox package - Error: `spawn UNKNOWN` from Playwright when launching camoufox.exe ## Problem `camoufox.exe` fails to start on Windows. The process exits immediately with no output. Windows Application Event Log shows: > Fehler beim Generieren des Aktivierungskontextes für "camoufox.exe". > Die abhängige Assemblierung "mozglue,language="*",type="win32", > version="1.0.0.0"" konnte nicht gefunden werden. (English: "Error generating activation context. The dependent assembly 'mozglue' could not be found.") ## Root Cause The embedded XML manifest inside `camoufox.exe` declares `mozglue.dll` as a **Windows SxS (Side-by-Side) assembly dependency**: ```xml <dependency> <dependentAssembly> <assemblyIdentity type="win32" name="mozglue" version="1.0.0.0" language="*" /> </dependentAssembly> </dependency> This is incorrect. SxS is for shared system ass

📅 Opened Jun 19, 2026💬 1 comment
Quality: 50/100Contribute

tl;dr Add mkdir ~/.camoufox to some installation steps or at least log it with error when camoufox-bin fails to create this directory. Describe the bug: I've tried to run camoufox through scrapling library StealthFetcher in GKE pod with read-only filesystem to scrape some URLs. It failed every time as the browser process hung and was killed after 180 second timeout. The logs coming out of that process wrapped by playwright weren't helpful at all in solving the main issue. The solution is simple (tl;dr) but required a lot of headache and uncommon ways of debugging to get to. BEWARE! The logs (from example code): Fetch failed for URL <https://example.com/>: <BrowserType.launch_persistent_context: Timeout 180000ms exceeded. Call log: - <launching> /home/someuser/.cache/camoufox/camoufox-bin -no-remote -headless -profile /tmp/playwright_firefoxdev_profile-eevuTY -juggler-pipe about:blank - <launched> pid=30 - [pid=30][err] *** You are running in headless mode. - [pid=30][out] Crash

📅 Opened Apr 13, 2026💬 1 comment
Quality: 30/100Contribute
Looking for more Python beginner tasks?Explore Python 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 daijro/camoufox

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

Frequently Asked Questions - Contributing to daijro/camoufox

01

Is daijro/camoufox welcoming to first-time open-source contributors?

daijro/camoufox has a recorded first-timer success rate of 30.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 61.8 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 61.8 places daijro/camoufox in the Welcoming tier.

04

What is the external contributor pull request merge rate for daijro/camoufox?

The external pull request merge rate is 40.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 daijro/camoufox?

daijro/camoufox 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 daijro/camoufox 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.