OWASP Foundation web repository
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 62%
Response Time: -
First Timer Success: 50%
OWASP/www-project-agent-memory-guard 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 OWASP/www-project-agent-memory-guard 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.
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.2 places OWASP/www-project-agent-memory-guard in the A tier.
The external contributor pull request merge rate for OWASP/www-project-agent-memory-guard is 61.5%, based on public PR activity from non-core contributors.
OWASP/www-project-agent-memory-guard currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in OWASP/www-project-agent-memory-guard. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in OWASP/www-project-agent-memory-guard 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/OWASP/www-project-agent-memory-guard?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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (77% approval). Large PRs (>500 lines) take ~115 hours (28% approval). Keep your diff compact for rapid review.
Docs GFI refresh (replacement for closed #115) Goal: One small, pin-able good first issue for newcomers. Prior GFI #115 is closed completed (PR #118 merged 9 Sep) — README already links LangChain middleware + clinic. This issue is the next docs-only bite. Scope (docs only — no detector/code changes) Add a short "Framework integrations" subsection (or FAQ bullet) that points maintainers/users at: Discussion #116 — LangChain middleware how-to README LangChain middleware snippet (MemoryGuardMiddleware) Public clinic Gist: https://gist.github.com/vgudur-dev/ead8817d2f4df08c04b808cc5b53eb06 Optional: how to open an Adopter: <name> — <framework> issue after trying the clinic Acceptance Links above present and accurate Vendor-neutral wording (no product pitch) Explicit non-claims: not OWASP-certified; not MITRE-approved; ATLAS AML.M0031 is YAML listing only pepy downloads and GitHub clones cited as two separate series if any metrics are mentioned (never blend) Why pin Keeps a
Description Create integration adapters for Microsoft AutoGen and the OpenAI Agents SDK to protect their memory and state management from poisoning attacks. Motivation AutoGen and OpenAI Agents SDK are rapidly growing multi-agent frameworks. Both maintain conversation state and shared memory that is vulnerable to poisoning. Providing security middleware for these frameworks positions Agent Memory Guard as the universal security layer for agentic AI. Proposed Implementation AutoGen Adapter Create src/agent_memory_guard/integrations/autogen.py: Wrap AutoGen's ConversableAgent message handling Intercept send/receive to screen for poisoning Support group chat memory protection OpenAI Agents SDK Adapter Create src/agent_memory_guard/integrations/openai_agents.py: Wrap the Agents SDK's context/state management Screen tool outputs before they enter agent memory Protect handoff context between agents Acceptance Criteria AutoGen adapter with message screening OpenAI Agents SDK adapter wi
Description Implement a Redis-backed MemoryStore that persists agent memory across restarts and enables distributed agent deployments. Motivation The current InMemoryStore is great for development and testing, but production deployments need persistent storage. Redis is the most common choice for fast key-value storage in production AI systems. Proposed Implementation Create src/agent_memory_guard/storage/redis_store.py with: RedisMemoryStore implementing the MemoryStore protocol Support for Redis connection pools and Sentinel Key namespacing for multi-tenant deployments TTL support for automatic memory expiration Atomic operations for concurrent agent access Example API from agent_memory_guard import MemoryGuard, Policy from agent_memory_guard.storage.redis_store import RedisMemoryStore store = RedisMemoryStore(url="redis://localhost:6379", namespace="agent-1") guard = MemoryGuard(store=store, policy=Policy.strict()) Acceptance Criteria Implements full MemoryStore protocol Conne
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 OWASP/www-project-agent-memory-guard, 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 OWASP/www-project-agent-memory-guard acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 61.5% were successfully merged into the primary branch.
OWASP/www-project-agent-memory-guard 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 ~-. 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 63.2 places OWASP/www-project-agent-memory-guard in the Welcoming tier.
The external pull request merge rate is 61.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, OWASP/www-project-agent-memory-guard currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for OWASP/www-project-agent-memory-guard 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.