Cognee is the open-source AI memory platform for agents. Give your AI agents persistent long-term memory with small models for free
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 45%
Response Time: 21h
First Timer Success: 25%
topoteretes/cognee has a recorded first-timer success rate of 25.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in topoteretes/cognee respond to incoming external pull requests in approximately 20.9 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 64.2 places topoteretes/cognee in the A tier.
The external contributor pull request merge rate for topoteretes/cognee is 44.7%, based on public PR activity from non-core contributors.
topoteretes/cognee currently has 60 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in topoteretes/cognee. 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/topoteretes/cognee?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~14 hours (56% approval). Large PRs (>500 lines) take ~100 hours (20% approval). Keep your diff compact for rapid review.
Problem Statement cognee has five data-source connectors today (confluence, gmail, google-drive, notion, slack) against roughly 120 planned. Data sources are the thinnest surface in the project. Calendly is on the roadmap and has no connector. Proposed Solution Add a calendly connector under packages/connector/calendly/ in cognee-community, following the shape of the five existing connectors. Auth: Personal access token Ingest: scheduled events, invitee questions, and notes Incremental sync: min_start_time window Forget-on-delete: deleting upstream must remove the record from the graph on the next sync Watch out for Invitee question responses carry the context; the event slot alone says nothing. Package layout to follow packages/connector/calendly/ ├── README.md ├── cognee_community_connector_calendly/ │ ├── __init__.py │ └── calendly.py ├── examples/ ├── tests/ └── pyproject.toml Read packages/connector/notion/ first — it is the c
Problem Statement cognee has five data-source connectors today (confluence, gmail, google-drive, notion, slack) against roughly 120 planned. Data sources are the thinnest surface in the project. Todoist is on the roadmap and has no connector. Proposed Solution Add a todoist connector under packages/connector/todoist/ in cognee-community, following the shape of the five existing connectors. Auth: API token Ingest: tasks, comments, and projects Incremental sync: sync API sync_token Forget-on-delete: deleting upstream must remove the record from the graph on the next sync Watch out for The incremental sync API returns exactly what changed — one of the cleanest cursors on this list. Package layout to follow packages/connector/todoist/ ├── README.md ├── cognee_community_connector_todoist/ │ ├── __init__.py │ └── todoist.py ├── examples/ ├── tests/ └── pyproject.toml Read packages/connector/notion/ first — it is the closest working ref
Problem Statement cognee has five data-source connectors today (confluence, gmail, google-drive, notion, slack) against roughly 120 planned. Data sources are the thinnest surface in the project. Zotero is on the roadmap and has no connector. Proposed Solution Add a zotero connector under packages/connector/zotero/ in cognee-community, following the shape of the five existing connectors. Auth: API key Ingest: references, notes, and attachment text Incremental sync: library version header Forget-on-delete: deleting upstream must remove the record from the graph on the next sync Watch out for Version-based sync is exact rather than timestamp-approximate. Follow it properly and sync is cheap. Package layout to follow packages/connector/zotero/ ├── README.md ├── cognee_community_connector_zotero/ │ ├── __init__.py │ └── zotero.py ├── examples/ ├── tests/ └── pyproject.toml Read packages/connector/notion/ first — it is the closest workin
Problem Statement cognee has five data-source connectors today (confluence, gmail, google-drive, notion, slack) against roughly 120 planned. Data sources are the thinnest surface in the project. Raindrop.io is on the roadmap and has no connector. Proposed Solution Add a raindrop connector under packages/connector/raindrop/ in cognee-community, following the shape of the five existing connectors. Auth: Test token / OAuth Ingest: bookmarks, collections, and annotations Incremental sync: lastUpdate sort Forget-on-delete: deleting upstream must remove the record from the graph on the next sync Watch out for Optionally fetch the linked page content, but make that opt-in — it multiplies ingest cost. Package layout to follow packages/connector/raindrop/ ├── README.md ├── cognee_community_connector_raindrop/ │ ├── __init__.py │ └── raindrop.py ├── examples/ ├── tests/ └── pyproject.toml Read packages/connector/notion/ first — it is the c
Problem Statement cognee has five data-source connectors today (confluence, gmail, google-drive, notion, slack) against roughly 120 planned. Data sources are the thinnest surface in the project. Readwise is on the roadmap and has no connector. Proposed Solution Add a readwise connector under packages/connector/readwise/ in cognee-community, following the shape of the five existing connectors. Auth: Access token Ingest: highlights, notes, and sources across books and articles Incremental sync: updatedAfter filter Forget-on-delete: deleting upstream must remove the record from the graph on the next sync Watch out for Highlights are pre-curated — someone already decided this mattered. Unusually high signal per token. Package layout to follow packages/connector/readwise/ ├── README.md ├── cognee_community_connector_readwise/ │ ├── __init__.py │ └── readwise.py ├── examples/ ├── tests/ └── pyproject.toml Read packages/connector/notion/
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 topoteretes/cognee, 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 topoteretes/cognee acknowledge new external contributions in approximately 20 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 44.7% were successfully merged into the primary branch.
topoteretes/cognee has a recorded first-timer success rate of 25.3%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~20 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 64.2 places topoteretes/cognee in the Welcoming tier.
The external pull request merge rate is 44.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, topoteretes/cognee currently has 60 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for topoteretes/cognee 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.