Native Safari browser automation for AI agents. 97 tools via AppleScript — zero overhead, keeps logins, runs silently in background. Drop-in alternative to Chrome DevTools MCP with 40-60% less CPU/heat on Apple Silicon.
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
achiya-automation/safari-mcp has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in achiya-automation/safari-mcp 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 8.0 places achiya-automation/safari-mcp in the D tier.
The external contributor pull request merge rate for achiya-automation/safari-mcp is 0.0%, based on public PR activity from non-core contributors.
achiya-automation/safari-mcp currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Native Safari browser automation for AI agents. 97 tools via AppleScript — zero overhead, keeps logins, runs silently in background. Drop-in alternative to Chrome DevTools MCP with 40-60% less CPU/heat on Apple Silicon.
Growing JavaScript project in achiya-automation/safari-mcp 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/achiya-automation/safari-mcp?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in JavaScript.
📝 Algorithms and data structures implemented in JavaScript with explanations and links to further readings
Clean Code concepts adapted for JavaScript
Resumes generated using the GitHub informations
The README covers installation and basic usage, but common questions keep coming up. Adding an FAQ section would reduce confusion and help new users get started faster. Questions to document Does it work with Safari Technology Preview? Can it handle private/incognito tabs? Does it work with multiple Safari windows? What macOS versions are supported? Can I run multiple instances simultaneously? Do I need to keep Safari in the foreground? How does it interact with Safari extensions? What happens if JavaScript from Apple Events is not enabled? Format suggestion Use a collapsible <details> block for each question to keep the README clean: ## FAQ <details> <summary>Does it work with Safari Technology Preview?</summary> Answer here... </details> Acceptance criteria FAQ section added to README.md At least 6 questions covered Answers are accurate (test on your machine if possible, or note "untested") Uses collapsible sections for readability Getting started Install the package and t
Safari MCP currently only works on macOS because it relies on AppleScript and the Safari Web Extension APIs. This limits the user base to macOS developers. The challenge Explore feasibility of supporting Linux/WSL via one of these approaches: GNOME Web (Epiphany) — WebKit-based browser on Linux, supports WebDriver WebKitGTK automation — Direct WebKit engine automation via GObject introspection Playwright WebKit — Playwright ships a WebKit browser that works on Linux Research questions Which approach provides the closest feature parity to the macOS Safari tools? Can we abstract the browser interaction layer so macOS uses AppleScript and Linux uses an alternative? What's the minimum viable feature set for a Linux version? (e.g., navigation, clicking, filling forms, reading content) Suggested architecture src/ engines/ macos-safari.js # Current AppleScript + Extension engine linux-webkit.js # New Linux engine engine-interface.js # Shared interface both
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 achiya-automation/safari-mcp, 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 achiya-automation/safari-mcp acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
achiya-automation/safari-mcp has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 8.0 places achiya-automation/safari-mcp in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, achiya-automation/safari-mcp currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for achiya-automation/safari-mcp 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.