Stellar Sentinel web experience: product landing page and planned risk dashboard for Stellar and Soroban.
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 100%
Response Time: -
First Timer Success: 100%
Stellar-Sentinel/sentinel-frontend has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Stellar-Sentinel/sentinel-frontend 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 58.0 places Stellar-Sentinel/sentinel-frontend in the A tier.
The external contributor pull request merge rate for Stellar-Sentinel/sentinel-frontend is 100.0%, based on public PR activity from non-core contributors.
Stellar-Sentinel/sentinel-frontend currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Stellar Sentinel web experience: product landing page and planned risk dashboard for Stellar and Soroban.
Collaborative maintainer environment in Stellar-Sentinel/sentinel-frontend. Reviews community pull requests with focus on project quality.
Discussions in Stellar-Sentinel/sentinel-frontend focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/Stellar-Sentinel/sentinel-frontend?utm_source=github&utm_medium=badge)
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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 16:00 to 20:00 UTC (16:00 - 20:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (45% approval). Keep your diff compact for rapid review.
Goal Make dashboard behavior changes safer by adding automated coverage for its main API-driven interactions. Scope Introduce a lightweight client-component test setup for the Next.js dashboard. Mock backend responses so tests do not depend on Horizon, Soroban RPC, or a running API. Cover screening submission, network status, event loading, and navigation state. Acceptance criteria A documented test command runs in local development and CI. Tests cover successful screening, API failure, empty event feed, event pagination, and active section navigation. Network requests are mocked and tests are deterministic. CI runs the new test command alongside the existing lint and build checks. Document how to add tests for dashboard components.
Goal Give users a chronological view of the Stellar operations behind an account screening result. Scope Add an activity timeline to the account assessment view using the cursor-paginated account activity endpoint tracked in sentinel-backend issue #1. Show operation type, time, counterparty, asset/amount, and transaction link when provided. Preserve asset identity and avoid presenting issued-asset values as XLM. Acceptance criteria Timeline loads from the selected account's API response and supports older-page loading. Loading, empty, upstream-error, and pagination-error states are clear. Existing screening metrics and signal explanations remain available. Operation values render safely when optional fields are absent. Add UI tests using mocked API responses and update the README/API shape notes.
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 Stellar-Sentinel/sentinel-frontend, 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 Stellar-Sentinel/sentinel-frontend acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
Stellar-Sentinel/sentinel-frontend has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming 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 58.0 places Stellar-Sentinel/sentinel-frontend in the Welcoming tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Stellar-Sentinel/sentinel-frontend 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 Stellar-Sentinel/sentinel-frontend 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.