astrid-runtime/astrid - Open Source PR Review Scorecard

Astrid is a portable, capability-secure operating system for composable software.

C-Rank Grade: A (Welcoming) - 63/100

External PR Merge Rate: 63%

Response Time: -

First Timer Success: 100%

Frequently Asked Questions

Is astrid-runtime/astrid welcoming to first-time open-source contributors?

astrid-runtime/astrid has a recorded first-timer success rate of 100.0%. Repositories ranked A 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 astrid-runtime/astrid 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.

What does the 63.1 C-Rank™ score (A 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 63.1 places astrid-runtime/astrid in the A tier.

What is the external contributor pull request merge rate for astrid-runtime/astrid?

The external contributor pull request merge rate for astrid-runtime/astrid is 62.5%, based on public PR activity from non-core contributors.

Are there Good First Issues available in astrid-runtime/astrid?

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

astrid-runtime
astrid-runtime/astridA•Welcoming10.3k
GitHub
Back to Explorer
astrid-runtime

astrid-runtime/astrid

10,281
InactiveA•Welcoming(63/100)Rust

Astrid is a portable, capability-secure operating system for composable software.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

High-Friction Gatekeeper

Warmth Score
6.2/10
Patience Score
6.9/10
Nitpick Rate
49%

Established Rust ecosystem in astrid-runtime/astrid. Maintains structured code review standards for external contributors.

Top PR Submission Do's

  • •Ensure code complies with Rust style conventions
  • •Keep PRs scoped and well-documented
  • •Include relevant test coverage for changes

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
  • •Do not mix unrelated refactors with feature work
Response Velocity
-
No reviewer activity recorded

Average Response Latency

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

Merge Efficiency
62.5%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
4 core
Small core review team
Diagnostic Health HUD
62.5%
Merge Gauge
100.0%
1st-Timer
Community Vibe55/100

Embed C-Rank Badge

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

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

Active Good First Issues (5)

View on GitHub

Summary crates/astrid-hooks/src/handler/agent.rs contains a fully stubbed AgentHandler that: execute() always returns HookExecutionResult::Skipped is_available() always returns false Has an unused AgentConfig with a hardcoded "claude-3-haiku" model string The HookHandler::Agent variant exists in the enum but does nothing Why remove it Hooks are for deterministic, fast interception: shell scripts, HTTP webhooks, WASM modules. Routing a hook through an LLM adds latency, non-determinism, and cost to every intercepted event. If someone wants LLM-based decision making on events, that belongs in an orchestrator capsule, not the hook system. The stub was written speculatively and never implemented. It adds dead code surface area, a HookHandler variant that confuses the API, and an AgentFailed error variant in HandlerError that can never be returned. Changes Delete crates/astrid-hooks/src/handler/agent.rs Remove AgentHandler from handler/mod.rs Remove HookHandler::Agent { .. } variant Remov

📅 Opened Mar 15, 2026💬 2 comments
Quality: 70/100Contribute

Summary Found as an out-of-scope observation while reviewing PR for #375. CapsuleRegistry::register and CapsuleRegistry::register_connector both return CapsuleError::UnsupportedEntryPoint when a duplicate ID is detected, but their doc comments claim they return CapsuleError::AlreadyRegistered and CapsuleError::ConnectorAlreadyRegistered respectively — neither of which exists in the CapsuleError enum. Impact Callers cannot reliably match on duplicate-registration errors without fragile string inspection. Any code written against the (false) documented API will silently fall through to a wildcard arm. Error messages in logs read as "Unsupported entry point: Already registered: foo", which is misleading. PR #375 cleaned up the symmetric unregister / unregister_connector paths (introducing NotFound) but did not address the register pair. Files / Lines crates/astrid-capsule/src/registry.rs line 60 (doc comment for register) crates/astrid-capsule/src/registry.rs line 66-68 (returns Unsu

📅 Opened Mar 15, 2026💬 2 comments
Quality: 70/100Contribute

Bug Found as an out-of-scope finding during review of PR fixing issue #445. File: crates/astrid-events/src/ipc.rs Line: 731 Description The test is_known_tag_covers_all_variants sets EXPECTED_VARIANT_COUNT = 17 and has 17 representatives. However IpcPayload has 19 variants: RawJson, UserInput, AgentResponse, ApprovalRequired, ApprovalResponse, OnboardingRequired, LlmRequest, LlmStreamEvent, LlmResponse, ToolExecuteRequest, ToolExecuteResult, ToolCancelRequest, SelectionRequired, ElicitRequest, ElicitResponse, Connect, Disconnect, Custom, Unknown The test omits ToolCancelRequest from the representatives list entirely, so the test never verifies that is_known_tag correctly recognizes "tool_cancel_request" and that the variant serializes to a known tag. Unknown is a #[serde(other)] catch-all that is intentionally excluded (it has no type tag of its own). But ToolCancelRequest is a real publishable variant and should be represented. Impact If is_known_tag ever loses coverage of "tool_canc

📅 Opened Mar 14, 2026💬 2 comments
Quality: 70/100Contribute

Describe the bug In crates/astrid-cli/src/tui/render.rs, the markdown parser for numbered lists uses strip_prefix(|c: char| c.is_ascii_digit()). Since strip_prefix with a closure only matches a single character, it only consumes one digit. If a list item starts with 10. , it consumes 1, leaving 0. , and then .and_then(|s| s.strip_prefix(". ")) fails. To Reproduce Have the assistant output a markdown numbered list with 10 or more items. Observe that items 1-9 are styled correctly (indented with colored numbers). Observe that item 10 and beyond are rendered as plain unstyled text without indentation. Suggested Fix Change the parsing logic to consume all leading digits before checking for . . Note: Found as an out-of-scope finding during review of PR feat/multi-line-paste.

📅 Opened Mar 14, 2026💬 2 comments
Quality: 70/100Contribute

In crates/astrid-capsule/src/engine/mcp.rs, invoke_interceptor does not check tool_result.is_error. When astrid_hook_intercept returns isError: true, the Rust side returns Ok with the error text as payload content. Hook errors are silently treated as success. Fix: check is_error and return Ok with empty vec if true, with a warn log. Found as OOS finding during review of feat/openclaw-pipeline-integration.

📅 Opened Mar 9, 2026💬 2 comments
Quality: 70/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 astrid-runtime/astrid

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

Frequently Asked Questions - Contributing to astrid-runtime/astrid

01

Is astrid-runtime/astrid welcoming to first-time open-source contributors?

astrid-runtime/astrid has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming 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 ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 63.1 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 63.1 places astrid-runtime/astrid in the Welcoming tier.

04

What is the external contributor pull request merge rate for astrid-runtime/astrid?

The external pull request merge rate is 62.5%. 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 astrid-runtime/astrid?

Yes, astrid-runtime/astrid currently has 5 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 astrid-runtime/astrid 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.