OpenAI-compatible proxy for Microsoft 365 Copilot — use the Copilot licence you already have as a backend for pi, openclaw and other coding agents. Prompt-emulated tool calling, no extra licence, no MCP.
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 50%
Response Time: 6d
First Timer Success: -
cramt/m365-copilot-proxy has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in cramt/m365-copilot-proxy respond to incoming external pull requests in approximately 142.5 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 48.7 places cramt/m365-copilot-proxy in the B tier.
The external contributor pull request merge rate for cramt/m365-copilot-proxy is 50.0%, based on public PR activity from non-core contributors.
cramt/m365-copilot-proxy currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
OpenAI-compatible proxy for Microsoft 365 Copilot — use the Copilot licence you already have as a backend for pi, openclaw and other coding agents. Prompt-emulated tool calling, no extra licence, no MCP.
Collaborative maintainer environment in cramt/m365-copilot-proxy. Reviews community pull requests with focus on project quality.
Discussions in cramt/m365-copilot-proxy 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/cramt/m365-copilot-proxy?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~93 hours (62% approval). Large PRs (>500 lines) take ~684 hours (22% approval). Keep your diff compact for rapid review.
Splitting this out of #4, where it was buried under a "how do I get my TOTP secret" title. What shipped M365_ENABLE_INTERACTIVE_APPROVAL=1 (merged 2026-08-06, code adapted from @EatonWu's fork) opens a real browser window, you complete SSO/MFA by hand once, and tokens refresh silently from the MSAL cache afterwards. No secrets.json, no TOTP seed. It's the fallback for tenants where the stored-credential path simply cannot work: the authenticator-app / software-OATH method is disabled by policy MFA is push / number-matching only, FIDO2, or Windows Hello sign-in is federated to Okta / Ping / Duo What's verified check result token via the interactive path 9.4s audience https://substrate.office.com/sydney token drives a real chat turn pong, contentOrigin: DeepLeo What is NOT verified, plainly My verification signed in through cached AAD SSO cookies — no human actually typed anything, and I have no federated tenant to test against. The redirect capture, PKCE exchange and t
I was wondering if u had a way around this: I got it installed on pi (windows) and tried a bunch of stuff. It does sometimes adopt powershell commands and correctly open/edit files. But only when i specifically say "use bash to" but still this doesn't always suffice. So I tried to add specific memories in m365 directly so it always uses powershell commands and to always prefer to work on windows session and not its own sandbox. But even this doesn't work. And once I give it a long task or an agent-subagent workflow, it starts giving ls and linux commands even tho it's been told multiple times it's on windows and it should only use powershell commands. It keeps reverting back to its linux sandbox in spite of memories and special prompting. I only tried gpt 5.6 so far but i assume all give the same results. If you know a way around this please help. Otherwise thanks for this upload it helps me a lot.
uhhh im too lazy to code so i gave ut ti k3 and it cook it very well should i pull request
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 cramt/m365-copilot-proxy, 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 cramt/m365-copilot-proxy acknowledge new external contributions in approximately 5 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
cramt/m365-copilot-proxy has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~5 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 48.7 places cramt/m365-copilot-proxy in the Solid tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, cramt/m365-copilot-proxy currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for cramt/m365-copilot-proxy 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.