🩺⚡ Runtime Doctrine ORM analysis integrated into Symfony Web Profiler. Detect N+1 queries, security vulnerabilities, and performance issues during query execution.
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 40%
Response Time: -
First Timer Success: 100%
ahmed-bhs/doctrine-doctor has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ahmed-bhs/doctrine-doctor 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 51.4 places ahmed-bhs/doctrine-doctor in the B tier.
The external contributor pull request merge rate for ahmed-bhs/doctrine-doctor is 40.0%, based on public PR activity from non-core contributors.
ahmed-bhs/doctrine-doctor currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in ahmed-bhs/doctrine-doctor. Prompt code reviews with positive guidance for new contributors.
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/ahmed-bhs/doctrine-doctor?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 Tuesday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (50% approval). Large PRs (>500 lines) take ~115 hours (18% approval). Keep your diff compact for rapid review.
Goal Separate per-request query analysis from project checks that do not depend on the current request. Runtime profiler: analyze SQL captured for this request. Static CI: inspect source code and Doctrine mappings without querying the live database. Database audit: check live configuration/schema in CI when a database is available. Split the one hybrid analyzer into runtime and static services. The profiler must run only runtime analyzers. Add a CI command (for example doctrine:doctor:analyze). AJAX is out of scope. Inventory below covers 99 collector analyzer services: 39 runtime, 51 static CI, 8 database-backed CI, and 1 hybrid. Classification is based on the data each analyzer actually reads, not its interface name alone. The three runtime analyzers that inspect schema/execute EXPLAIN still require live database access: MissingIndexAnalyzer, StructuralMissingIndexAnalyzer, and OrderByNullableLeadingColumnAnalyzer. Current execution cost DoctrineDoctorDataCollector calls every ana
Summary Detect entities with soft-delete fields (deletedAt, isDeleted, isArchived) that have no corresponding Doctrine SQL Filter configured, risking accidental exposure of deleted records. Problem Soft delete is a common pattern, but without a global SQL Filter, developers must remember to add WHERE deleted_at IS NULL to every query. Missing this filter in even one repository method exposes "deleted" records to users. The existing SoftDeleteableTraitAnalyzer checks for Gedmo trait usage issues. This analyzer is complementary: it detects soft-delete fields that lack global filter protection, regardless of whether Gedmo is used. Problematic state: #[ORM\Entity] class Product { #[ORM\Column(type: 'datetime_immutable', nullable: true)] private ?\DateTimeImmutable $deletedAt = null; // No SQL Filter configured -- every query must manually exclude deleted records } Detection approach Type: Metadata-based + Configuration (Configuration) Method: Scan entity metadata for fields m
The data collector already exposes getIssues(), getStats(), and getGroupedQueriesByTime() but there's no way to export this from the profiler panel. An "Export JSON" button in the profiler would let developers save and share reports, or track issues over time.
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 ahmed-bhs/doctrine-doctor, 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 ahmed-bhs/doctrine-doctor 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.
ahmed-bhs/doctrine-doctor has a recorded first-timer success rate of 100.0%. Repositories ranked Solid 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 51.4 places ahmed-bhs/doctrine-doctor in the Solid tier.
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.
Yes, ahmed-bhs/doctrine-doctor currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ahmed-bhs/doctrine-doctor 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.