Local-first desktop monitoring for AI agents. Inspect processes, files, network activity and evidence; review selected actions through opt-in policy and MCP tools. Windows-first; macOS/Linux experimental.
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 48%
Response Time: 3d
First Timer Success: 50%
antropos17/Aegis has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in antropos17/Aegis respond to incoming external pull requests in approximately 83.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 61.1 places antropos17/Aegis in the A tier.
The external contributor pull request merge rate for antropos17/Aegis is 48.1%, based on public PR activity from non-core contributors.
antropos17/Aegis currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Local-first desktop monitoring for AI agents. Inspect processes, files, network activity and evidence; review selected actions through opt-in policy and MCP tools. Windows-first; macOS/Linux experimental.
Growing JavaScript project in antropos17/Aegis 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/antropos17/Aegis?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~54 hours (60% approval). Large PRs (>500 lines) take ~398 hours (22% approval). Keep your diff compact for rapid review.
SummaryCards.svelte renders the five cards at the top of the Shield tab. None of the five labels goes through the i18n layer, so they stay English when the language changes. Same class of defect as #271, which was fixed for AgentStatsPanel.svelte in #273. Hardcoded strings src/renderer/lib/components/SummaryCards.svelte 167: <span class="card-label">Total Agents</span> 179: <span class="card-label">Avg Risk Score</span> 191: <span class="card-label">Events / min</span> The remaining two labels are indirected through constants, but the literals are still English and still outside i18n: src/renderer/lib/utils/summary-metrics.ts 21:export const SENSITIVE_SUMMARY_LABEL = 'Sensitive Alerts'; 29:export const MONITORING_DURATION_LABEL = 'Monitoring Duration'; consumed at SummaryCards.svelte:203 and :215. The component imports no i18n at all: grep -c i18n src/renderer/lib/components/SummaryCards.svelte # 0 The pattern to follow AgentStatsPanel.svelte after #273: import { t } from
Two parts of CONTRIBUTING.md give instructions a contributor cannot follow, because they name things the repository does not have. 1. Branch prefix CONTRIBUTING.md:19 2. **Branch** from `master`: `git checkout -b feature/your-feature` feature/ is not a prefix this project uses. Eight lines later, the same file says the right thing: CONTRIBUTING.md:27 — "Create a feature branch: git checkout -b feat/my-feature" BRANCHING.md:6-10 — feat/ fix/ perf/ chore/ docs/ AGENTS.md:79 — "Feature branches, always: feat/* | fix/* | chore/* | docs/*" 2. Issue labels CONTRIBUTING.md:181-189 lists labels to use when filing an issue. Two of the seven do not exist on this repository: CONTRIBUTING.md:184 — feature. The repository's label for this is enhancement. CONTRIBUTING.md:189 — kernel. No such label. The list also omits most of the labels that do exist and are in active use: good first issue, help wanted, testing, typescript, ui, monitoring, detection, network, ci/cd, packaging, questi
Two documents tell a contributor that a hook file guards commits on master, and name a path that is not in the repository. AGENTS.md:81 … .claude/hooks/branch-guard.js refuses edits on master before you reach that point. BRANCHING.md:23 The .claude/hooks/branch-guard.js hook refuses edits on master before you get that far. Nothing under .claude/ is tracked. The only branch-guard file in the repository is .codex/hooks/branch-guard.js, wired by .codex/hooks.json. The rest of both sentences is accurate — branch protection on master does reject a direct push. It is only the hook path that a contributor cannot find. Reproduction git grep -n -F '.claude/hooks/branch-guard.js' -- AGENTS.md BRANCHING.md # AGENTS.md:81 # BRANCHING.md:23 git ls-files | grep branch-guard # .codex/hooks/branch-guard.js git ls-files | grep '^\.claude/' # (no output) Verified at master 0b21a90. Note: BRANCHING.md was edited by PR #274, which touched lines 27-38 only; line 23 is untouched by it. Definition
Three contributor-facing documents state three different Node.js requirements, and the lowest one is unusable. Site Says CONTRIBUTING.md:14 "Requires Node.js 18+" README.md:105 "Requires Node.js 22.x (engines in package.json)" llms-full.txt:22 "requires Node.js 20.19+ or 22.12+ … so Node 18 and 19 are excluded" The authority disagrees with the first one: node -p "require('./package.json').engines.node" # 22.x cat .nvmrc # 22 grep -n "node-version" .github/workflows/*.yml # '22' on every job .github/workflows/ci.yml pins node-version: '22' for all five jobs, and release-build.yml does the same. llms-full.txt:22 states the reason 18 cannot work: Vite 7 declares ^20.19.0 || >=22.12.0, so a contributor who follows CONTRIBUTING.md and installs Node 18 hits an engine failure at npm ci or a broken build, before writing any code. Reproduction git grep -n -F 'Node.js 18+' # CONTRIBUTING.md:14 git grep -n -F 'Node.js 22.x' # RE
npm run counts:check derives 19 counters from the tree and checks them against 96 declaration sites, and it is green. The numbers below sit outside that gate — no check computes them, so they went stale without anything turning red. This is exactly the pattern memory-bank/ai-mistakes.md #24 records. All figures below were measured at master 0b21a90. 1. Test counts — three sites Site Says Measured CONTRIBUTING.md:21 "run npm test (1075 tests across 68 files)" 122 files, 2137 passed / 4 skipped (2141) llms.txt:26 "Tests: 1075 passing, 4 skipped across 68 files (Vitest)" same llms-full.txt:60 "Tests: 1075 passing, 4 skipped across 68 files (Vitest)" same README.md:84 already states the project's position on this: "Test counts. Hand-copied suite counts go stale silently; the suite prints its own counts, and CI runs it on every commit." These three sites contradict that policy. 2. Version — two sites llms.txt:28 and llms-full.txt:62 both read **Version**: 0.10.0-alpha. p
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 antropos17/Aegis, 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 antropos17/Aegis acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 48.1% were successfully merged into the primary branch.
antropos17/Aegis has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. 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 61.1 places antropos17/Aegis in the Welcoming tier.
The external pull request merge rate is 48.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, antropos17/Aegis currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for antropos17/Aegis 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.