Manage Microsoft 365 and SharePoint Framework projects on any platform
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 43%
Response Time: 3h
First Timer Success: 43%
pnp/cli-microsoft365 has a recorded first-timer success rate of 42.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pnp/cli-microsoft365 respond to incoming external pull requests in approximately 2.9 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 64.8 places pnp/cli-microsoft365 in the A tier.
The external contributor pull request merge rate for pnp/cli-microsoft365 is 43.2%, based on public PR activity from non-core contributors.
pnp/cli-microsoft365 currently has 41 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Manage Microsoft 365 and SharePoint Framework projects on any platform
Active maintainer team in pnp/cli-microsoft365 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/pnp/cli-microsoft365?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 21:00 to 01:00 UTC (21:00 - 01:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (54% approval). Large PRs (>500 lines) take ~14 hours (19% approval). Keep your diff compact for rapid review.
Usage m365 spo report siteversionstorageusage status get [options] Description Retrieve the status of a version storage usage report Options Option Description --siteUrl <siteUrl> URL of the site collection to target. --fileUrl <fileUrl> Server-relative URL of the file where the report will be stored. Examples Get the progress of a specific file version usage report m365 spo report siteversionstorageusage --siteUrl "https://contoso.sharepoint.com/sites/Marketing" --fileUrl "/sites/Marketing/Reports/FileUsage.csv" Default properties No response Additional Info API request Get report status POST https://contoso.sharepoint.com/sites/Marketing/_api/Site/GetProgressForFileVersionExpirationReport(reportFileUrl='/sites/Marketing/Reports/StorageReport.csv') Docs ImportantWhile the job is being processed, you can see the report file being gradually populated. Do not update the file during this time. It will cause the job to fail. Check the progress of the report generation to confi
Usage m365 spo page unpublish [options] Description Unpublishes a modern page Options Option Description -u, --webUrl <webUrl> URL of the site. -n, --name <name> Name of the page to target. Examples Publish a modern page m365 spo page unpublish --webUrl https://contoso.sharepoint.com/sites/Marketing --name "Style guide.aspx" Publish a modern page in a subfolder m365 spo page unpublish --webUrl https://contoso.sharepoint.com/sites/Marketing --name "/Styles/Guide.aspx" Default properties No response Additional Info API URL: POST https://contoso.sharepoint.com/sites/Playground/_api/web/GetFileByServerRelativePath(DecodedUrl='/sites/Playground/SitePages/Home.aspx')/UnPublish
We're adding a new Permissions section to all commands. This section will document the minimal delegated and application permissions required to execute the command. The goal is to: Make it easier to run the CLI with custom app registrations and application permissions. Ensure we only document the minimal set of permissions needed. Keep documentation consistent by placing the Permissions section right before the Examples section. If there are multiple resources, order them alphabetically If there are commands that only support one type of auth (like delegated or app-only), we have an example for that as well. E.g. m365 planner tenant settings list - Permissions Resources Writing the docs page How to document minimal permissions Planner example 1 Planner example 2 Commands in scope This issue covers the following commands: m365 viva engage community-user add m365 viva engage community-user list m365 viva engage community-user remove m365 viva engage message-like set m365 viva engag
We're adding a new Permissions section to all commands. This section will document the minimal delegated and application permissions required to execute the command. The goal is to: Make it easier to run the CLI with custom app registrations and application permissions. Ensure we only document the minimal set of permissions needed. Keep documentation consistent by placing the Permissions section right before the Examples section. If there are multiple resources, order them alphabetically If there are commands that only support one type of auth (like delegated or app-only), we have an example for that as well. E.g. m365 planner tenant settings list - Permissions Resources Writing the docs page How to document minimal permissions Planner example 1 Planner example 2 Commands in scope This issue covers the following commands: m365 viva engage message add m365 viva engage message get m365 viva engage message list m365 viva engage message remove
We're adding a new Permissions section to all commands. This section will document the minimal delegated and application permissions required to execute the command. The goal is to: Make it easier to run the CLI with custom app registrations and application permissions. Ensure we only document the minimal set of permissions needed. Keep documentation consistent by placing the Permissions section right before the Examples section. If there are multiple resources, order them alphabetically If there are commands that only support one type of auth (like delegated or app-only), we have an example for that as well. E.g. m365 planner tenant settings list - Permissions Resources Writing the docs page How to document minimal permissions Planner example 1 Planner example 2 Commands in scope This issue covers the following commands: m365 viva engage community add m365 viva engage community get m365 viva engage community list m365 viva engage community remove m365 viva engage community set
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 pnp/cli-microsoft365, 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 pnp/cli-microsoft365 acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 43.2% were successfully merged into the primary branch.
pnp/cli-microsoft365 has a recorded first-timer success rate of 42.9%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 hours. 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 64.8 places pnp/cli-microsoft365 in the Welcoming tier.
The external pull request merge rate is 43.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pnp/cli-microsoft365 currently has 41 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for pnp/cli-microsoft365 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.