📚 The open-source, offline-first Notion, Obsidian & Confluence alternative. Advanced Markdown, multi-tenant teams, OIDC/SSO, and local S3 backups. Deploy in one command.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 76%
Response Time: 9h
First Timer Success: 57%
Smaug6739/Alexandrie has a recorded first-timer success rate of 57.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Smaug6739/Alexandrie respond to incoming external pull requests in approximately 9.1 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 68.5 places Smaug6739/Alexandrie in the A tier.
The external contributor pull request merge rate for Smaug6739/Alexandrie is 75.6%, based on public PR activity from non-core contributors.
Smaug6739/Alexandrie currently has 11 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in Smaug6739/Alexandrie. Prompt code reviews with positive guidance for new contributors.
Discussions in Smaug6739/Alexandrie 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/Smaug6739/Alexandrie?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (94% approval). Large PRs (>500 lines) take ~44 hours (34% approval). Keep your diff compact for rapid review.
Describe the bug S3 Integration: Native compatibility with decentralized modern object stores (such as RustFS, Garage, MinIO, or AWS). This project is expected to support Garage. However, the backend aborts with s3 | Failed to set bucket policy: Unimplemented action: PutBucketPolicy when I use Garage as S3 storage. To Reproduce Steps to reproduce the behavior: Create bucket and generate access key / secret key in Garage Set up Alexandrie Start Alexandrie See error Expected behavior The backend server does not fail if the S3 storage is Garage. Screenshots If applicable, add screenshots to help explain your problem. Sep 22 05:01:59 alexandrie docker[46052]: Container alexandrie-mysql Healthy Sep 22 05:01:59 alexandrie docker[46052]: Container alexandrie-backend Starting Sep 22 05:02:00 alexandrie docker[46052]: Container alexandrie-backend Started Sep 22 05:02:00 alexandrie docker[46052]: Container alexandrie-frontend Starting Sep 22 05:02:00 alexandrie docker[46052]: alexandrie-
Describe the bug The document overview offers Kanban in the view selector even when no concrete workspace/container is selected. Selecting it in All workspaces displays: DEBUG: View is unrecognized or undefined. Current value: kanban The page then renders the fallback document list rather than a Kanban board. The message is misleading: kanban is a recognized view, but this context has no parent required by the board. To Reproduce Prerequisite: at least one document must be visible in the overview. With an empty document list, the component takes its no-content branch instead. Open the document overview at /dashboard/docs. Select All workspaces so no concrete parent workspace/container is selected. Select Kanban in the view selector. Observe the DEBUG message above the fallback document list. Reload the page. The stored Kanban selection can restore the same unsupported state. Also check navigation from a concrete workspace with Kanban selected back to All workspaces. Expected behavio
Currently categories are displayed as a small tree and with limited context (workspaces and categories). Teams are displayed as simple workspaces without any child. The goal of this issue is to modernize this interface and add a "graph" view. There is no specific target interface; the goal is simply to improve the current experience and make it more usable. For the graphical view, the aim is to avoid using an external library that would bloat the app for the sake of just one page. We should add a view switcher in the top-right corner, similar to the existing ones for map, list, and kanban views.
We should imporve the admin dashboard to add security stats and allow admins to detect and handle problems. Admins should be allowed to change users passwords Admins should be allowed to see and close sessions Admins should be able to suspend / ban accounts
Currelty backups export documents in a big JSON file. We should add an option to allow exports as markdown file Documents should be markdown files Categories should be folders We should keep the tree structure during export
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 Smaug6739/Alexandrie, 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 Smaug6739/Alexandrie acknowledge new external contributions in approximately 9 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.6% were successfully merged into the primary branch.
Smaug6739/Alexandrie has a recorded first-timer success rate of 57.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 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 68.5 places Smaug6739/Alexandrie in the Welcoming tier.
The external pull request merge rate is 75.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Smaug6739/Alexandrie 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 Smaug6739/Alexandrie 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.