An open-source activism platform
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 67%
Response Time: 2d
First Timer Success: 77%
activist-org/activist has a recorded first-timer success rate of 76.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in activist-org/activist respond to incoming external pull requests in approximately 59.4 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 61.9 places activist-org/activist in the A tier.
The external contributor pull request merge rate for activist-org/activist is 67.2%, based on public PR activity from non-core contributors.
activist-org/activist currently has 11 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in activist-org/activist. Maintains strict focus on technical quality and test standards.
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/activist-org/activist?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~39 hours (84% approval). Large PRs (>500 lines) take ~285 hours (30% approval). Keep your diff compact for rapid review.
Terms I have searched open and closed feature requests I agree to follow activist's Code of Conduct Description As discussed in #2436, we'd like to switch the way that custom CSS is applied to the frontend to use only rem and not px, as the former scales better. There may be cases where px should be used, so we should discuss before a PR. What's included: Updating the style guide with Make the needed changes to all instances of px to convert them to rem Contribution Happy to support this and review a PR! 🎨
Terms I have searched open and closed feature requests I agree to follow activist's Code of Conduct Description Caution This issue is blocked by #849, with the work being done in #2400. Once #2400 is merged we want to split the supported organizations and events on the home page into two different grids. The grids should be roughly four elements or so across and have a Load more button under them so that the events header and grid is above the page fold. The cards in the grid should be similar to the cards we use for mobile, with these having a line clamp of two lines on their descriptions. Contribution Happy to support and review a PR! 😊
Terms I have searched open and closed feature requests I agree to follow activist's Code of Conduct Description As discussed in the most recent dev sync, we want the user to be routed over to the /sign-in route if they visit the /home route when signed out. We don't show the home page to signed out users and don't have any functionality there for them as the purpose of the page is showing supported organizations and events. Signed out users can't support, so there's no point in them going to this route. Contribution Happy to support and review a PR! 😊
Dependency Update Report - September 15, 2026 🤖⬆️ NoteAll tests should pass for PRs that are updating dependencies. See the local testing section of the contributing guide for more information on how to run tests before your PR. Please also limit the number of dependencies that are being updated in each PR to make it easy for maintainers to merge. WarningNote that the following dependencies have maximum versions set in the dependency_update_check.yaml workflow: Frontend: [email protected] Please check whether maximum version restrictions can be removed and rerun the workflow without them if they can be. Available Dependency Updates Package Name Old Version New Available Version Type anyio 4.12.1 4.15.1 Backend asgiref 3.11.1 3.12.1 Backend ast-serialize 0.6.0 0.11.2 Backend attrs 25.4.0 26.1.0 Backend certifi 2026.2.25 2026.7.22 Backend charset-normalizer 3.4.4 3.5.1 Backend complexipy 7.0.1 8.0.1 Backend coverage 7.13.4 7.16.1 Backend django 6.1 6.1.1
Dependency Audit Report - September 15, 2026 🤖🔍 NoteMerging all dependabot PRs will solve the pressing vulnerabilities that are easy to resolve. Others should be discussed. Backend dependency Audit Report Frontend dependency Audit Report ├─ @tiptap/core │ ├─ ID: 1158508 │ ├─ Issue: Tiptap: mergeAttributes() turns an own proto key into inherited executable DOM attributes │ ├─ URL: GHSA-cp6q-959q-f8rh │ ├─ Severity: moderate │ ├─ Vulnerable Versions: >=2.0.0-alpha.0 <3.30.4 │ │ │ ├─ Tree Versions │ │ └─ 3.27.1 │ │ │ └─ Dependents │ └─ activist@workspace:. │ ├─ @tiptap/core │ ├─ ID: 1193728 │ ├─ Issue: Tiptap: Quadratic ReDoS in block and inline Markdown attribute parsing │ ├─ URL: GHSA-j95f-988m-3j2f │ ├─ Severity: high │ ├─ Vulnerable Versions: >=3.7.0 <3.30.5 │ │ │ ├─ Tree Versions │ │ └─ 3.27.1 │ │ │ └─ Dependents │
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 activist-org/activist, 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 activist-org/activist acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 67.2% were successfully merged into the primary branch.
activist-org/activist has a recorded first-timer success rate of 76.9%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 61.9 places activist-org/activist in the Welcoming tier.
The external pull request merge rate is 67.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, activist-org/activist currently has 11 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for activist-org/activist 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.