pacifio/atlas - Open Source PR Review Scorecard

Source control for agents. Use multiple coding agents, track their changes and query them in one place

C-Rank Grade: S (Elite) - 71/100

External PR Merge Rate: 73%

Response Time: 5h

First Timer Success: 50%

Frequently Asked Questions

Is pacifio/atlas welcoming to first-time open-source contributors?

pacifio/atlas has a recorded first-timer success rate of 50.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in pacifio/atlas respond to incoming external pull requests in approximately 5.5 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 71.0 C-Rank™ score (S Tier) represent?

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 71.0 places pacifio/atlas in the S tier.

What is the external contributor pull request merge rate for pacifio/atlas?

The external contributor pull request merge rate for pacifio/atlas is 72.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in pacifio/atlas?

pacifio/atlas currently has 9 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

pacifio
pacifio/atlasS•Elite9.6k
GitHub
Back to Explorer
pacifio

pacifio/atlas

9,553
InactiveS•Elite(71/100)Rust

Source control for agents. Use multiple coding agents, track their changes and query them in one place

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in pacifio/atlas welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
5 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
72.6%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
16 core
Highly collaborative maintainer core
Diagnostic Health HUD
72.6%
Merge Gauge
50.0%
1st-Timer
Community Vibe70/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for pacifio/atlas
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/pacifio/atlas)](https://getmerged.abhishekco.de/pacifio/atlas?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Tell us more commands/memory_extract.rs routes extraction through the summariser preference. Signed out with no BYOK provider, "no pass, silently". I'm signed in on a Personal organisation without AI grants and have no provider key. Across 45 sessions on one project, the store has no extractor entries. From the user's side nothing says extraction isn't happening: The Memory panel shows sharing as on. The Raw / Provider / Local selector is presented as the handoff summariser, not as what decides whether durable memory gets extracted. So the natural conclusion is "memory doesn't work". Suggestion: show the extractor's state where sharing is configured, e.g. "Automatic extraction: off — needs AI grants or a provider key", linking to the provider picker. Also log when a pass is skipped or refused. Which area is this about? memory

📅 Opened Oct 1, 2026💬 1 comment
Quality: 90/100Contribute

What's going on? On Windows 11, cargo test -p atlas --lib compiles, but the test executable exits before running anything: process didn't exit successfully: `...\deps\atlas_lib-<hash>.exe state::atlas_config` (exit code: 0xc0000139, STATUS_ENTRYPOINT_NOT_FOUND) So none of src-tauri's unit tests can run on Windows, and Windows contributors can't check changes to e.g. state/atlas_config.rs locally. CI runs these tests on macOS only, so this is invisible there. I haven't confirmed the cause. A common one for Tauri apps on Windows is a test binary built without the application manifest, so it binds to comctl32 v5 and fails on an import that needs v6 (e.g. TaskDialogIndirect). Workarounds I used: pure logic in a separate crate (whose tests do run), and cargo check -p atlas --tests. Which area is this in? other (tests / Windows) How sure are you? Reproducible every time here; the root cause above is a guess.

📅 Opened Oct 1, 2026💬 0 comments
Quality: 100/100Contribute

What happens In the Timeline tab, a session row's model label overflows its grid column to the left and is painted over the agent icon. Both end up unreadable. Only long model names do it. Rows showing Opus 5 are fine; rows showing google/gemini-3.1-pro-preview or google/gemini-3.1-flash-lite collide with the icon. Why src/features/artifacts/components/session-list.tsx:155 gives the model a fixed 92px track: const ROW_GRID = "grid grid-cols-[22px_minmax(0,1fr)_28px_92px_68px] items-center gap-4 px-5"; // rail title agent model dur and session-list.tsx:254 renders into it: <span className="justify-self-end truncate font-mono text-[11px] text-[var(--text-tertiary)]"> {prettyModel(session.model) ?? ""} </span> truncate expands to overflow:hidden; text-overflow:ellipsis; white-space:nowrap. The nowrap raises the element's min-content width to the width of the entire string. justify-self-end takes the item out of stretch, so its used width is fit-

📅 Opened Sep 8, 2026💬 0 comments
Quality: 90/100Contribute

Getting started: read CONTRIBUTING.md, run bun install, then bun run dev:app (Tauri dev build). Rust commands need export SDKROOT="$(xcrun --show-sdk-path)" on macOS, and crates are path-linked (no workspace) — run cargo from inside the crate directory. bun run test + bun run typecheck must stay green. area:rust · cleanup · ~30 min artifacts_sessions (src-tauri/src/commands/capture.rs:1160) lost its only frontend caller when a memory view was removed; it’s now registered dead surface (verified — no TS caller, and tests/ipc-contract.test.ts guards the seam). Do: delete the command fn and its generate_handler! line in src-tauri/src/lib.rs. If helpers it calls inside capture.rs are shared with other commands, leave those. Done when: cargo check in src-tauri is warning-free and bun run test (which includes the IPC contract test) passes.

📅 Opened Aug 22, 2026💬 0 comments
Quality: 90/100Contribute

Getting started: read CONTRIBUTING.md, run bun install, then bun run dev:app (Tauri dev build). Rust commands need export SDKROOT="$(xcrun --show-sdk-path)" on macOS, and crates are path-linked (no workspace) — run cargo from inside the crate directory. bun run test + bun run typecheck must stay green. area:providers · ~1–2 h Three small, mirrored additions wire in a new OpenAI-compatible provider (pick one — e.g. Moonshot): src/features/settings/lib/providers.ts — catalog entry (id, name, env var, category, docs URL). src-tauri/src/commands/byok.rs — ENV_KEY_VARS row so the key is recognised in the user’s shell profile. src-tauri/src/commands/modelchat.rs — provider_endpoint() arm with the OpenAI-compatible base URL (only if the provider should be chat-capable). Done when: the provider row shows in Settings → API Keys, a key exported in your shell profile is detected, and (if chat-capable) a completion streams in a feature that uses BYOK (e.g. commit-message genera

📅 Opened Aug 22, 2026💬 0 comments
Quality: 90/100Contribute
Looking for more Rust beginner tasks?Explore Rust GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for pacifio/atlas

When evaluating whether to contribute to pacifio/atlas, 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 pacifio/atlas acknowledge new external contributions in approximately 5 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 72.6% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to pacifio/atlas

01

Is pacifio/atlas welcoming to first-time open-source contributors?

pacifio/atlas has a recorded first-timer success rate of 50.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~5 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 71.0 C-Rank™ score represent?

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 71.0 places pacifio/atlas in the Elite tier.

04

What is the external contributor pull request merge rate for pacifio/atlas?

The external pull request merge rate is 72.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in pacifio/atlas?

Yes, pacifio/atlas currently has 9 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for pacifio/atlas 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.