Your Personal AI OS
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 83%
Response Time: 12h
First Timer Success: 75%
RedPlanetHQ/core has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in RedPlanetHQ/core respond to incoming external pull requests in approximately 12.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 63.5 places RedPlanetHQ/core in the A tier.
The external contributor pull request merge rate for RedPlanetHQ/core is 83.3%, based on public PR activity from non-core contributors.
RedPlanetHQ/core currently has 73 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in RedPlanetHQ/core 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/RedPlanetHQ/core?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (96% approval). Large PRs (>500 lines) take ~58 hours (38% approval). Keep your diff compact for rapid review.
Description Add a Zerodha Kite (Kite Connect) integration so CORE can read a user’s trading account (holdings/positions/orders) and track meaningful events over time. This is a strong candidate for an integration because Zerodha provides an official developer platform (Kite Connect) and also maintains an official MCP server. Reference Implementations Kite Connect (official docs): https://kite.trade/docs/connect/v3/ Kite Connect API reference: https://kite.trade/docs/connect/v3/user/ Official SDKs (examples): https://kite.trade/docs/connect/v3/libraries/ Zerodha Kite MCP server (official): https://github.com/zerodha/kite-mcp-server Hosted MCP endpoint (if available): https://mcp.kite.trade (verify) Required Files Structure packages/core/src/integrations/zerodha-kite/ index.ts client.ts types.ts mappers.ts auth.ts README.md packages/core/src/integrations/zerodha-kite/__tests__/ zerodha-kite.test.ts Kite Integration Auth OAuth-like flow with request token → access to
Description Add a Groww integration so CORE can read (and optionally act on) a user’s portfolio + trading activity, and log high-signal events into memory. This is primarily a read-first integration (portfolio + orders + transactions + holdings). If Groww’s trading APIs allow it, we can extend later to actions (place/cancel orders). Reference Implementations Groww product: https://groww.in/ Groww Trade API docs (unofficial / community references): https://github.com/zerodha/pykiteconnect (reference for patterns; not Groww) https://github.com/ (TBD — add any reliable Groww API reference you find) Groww MCP (hosted): https://mcp.groww.in (if still active / publicly reachable) Note: Groww does not have a widely-adopted, fully-public “official” developer platform like Zerodha Kite Connect. We should treat this integration as: (1) MCP-first if Groww’s MCP is usable, otherwise (2) browser/session-based data extraction with explicit user consent, or (3) defer until an offici
Description Add New Relic integration to sync observability data, alerts, incidents, deployments, and application performance metrics into CORE. Reference Implementations Existing Integrations (use as templates) integrations/github/ - Developer tooling with event tracking integrations/linear/ - Issue/incident management patterns integrations/slack/ - For reference Required Files Structure integrations/new-relic/ ├── src/ │ ├── index.ts # Main entry, API spec │ ├── schedule.ts # Sync logic │ ├── utils.ts # New Relic API utilities │ ├── account-create.ts # Auth setup │ └── create-activity.ts # Activity formatting ├── package.json ├── tsup.config.ts └── README.md New Relic API Integration OAuth Setup Use API Key authentication (User Key) New Relic provides multiple key types: User API Key: Primary key for NerdGraph and REST API access (header: Api-Key) License Key: For sending telemetry
Description Add Datadog integration to sync monitoring alerts, events, dashboards, incidents, and observability data into CORE. Reference Implementations Existing Integrations (use as templates) integrations/github/ - Developer tooling with event tracking integrations/linear/ - For incident/issue patterns integrations/slack/ - For reference Required Files Structure integrations/datadog/ ├── src/ │ ├── index.ts # Main entry, API spec │ ├── schedule.ts # Sync logic │ ├── utils.ts # Datadog API utilities │ ├── account-create.ts # Auth setup │ └── create-activity.ts # Activity formatting ├── package.json ├── tsup.config.ts └── README.md Datadog API Integration OAuth Setup Use API Key + Application Key authentication API Key header: DD-API-KEY Application Key header: DD-APPLICATION-KEY Base URL varies by region: US1: https://api.datadoghq.com/api/ US3: https://api.us3.datadoghq.com/api/ US
Description Add Prisma Data Platform integration to sync database projects, workspace activity, and Prisma Postgres database management events into CORE. Reference Implementations Existing Integrations (use as templates) integrations/github/ - Developer tooling integration integrations/linear/ - Project management patterns integrations/slack/ - For reference Required Files Structure integrations/prisma/ ├── src/ │ ├── index.ts # Main entry, OAuth spec │ ├── schedule.ts # Sync logic │ ├── utils.ts # Prisma API utilities │ ├── account-create.ts # OAuth setup │ └── create-activity.ts # Activity formatting ├── package.json ├── tsup.config.ts └── README.md Prisma API Integration OAuth Setup Use OAuth 2.0 or Bearer Token authentication The @prisma/management-api-sdk provides built-in OAuth with automatic token refresh Token endpoint for OAuth: Prisma Platform OAuth flow Required scope: offli
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 RedPlanetHQ/core, 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 RedPlanetHQ/core acknowledge new external contributions in approximately 11 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.3% were successfully merged into the primary branch.
RedPlanetHQ/core has a recorded first-timer success rate of 75.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~11 hours. 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 63.5 places RedPlanetHQ/core in the Welcoming tier.
The external pull request merge rate is 83.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, RedPlanetHQ/core currently has 73 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for RedPlanetHQ/core 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.