The PnP Core SDK is a modern .NET SDK designed to work for Microsoft 365. It provides a unified object model for working with SharePoint Online and Teams which is agnostic to the underlying API's being called
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 44%
Response Time: -
First Timer Success: 29%
pnp/pnpcore has a recorded first-timer success rate of 28.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in pnp/pnpcore 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 58.9 places pnp/pnpcore in the A tier.
The external contributor pull request merge rate for pnp/pnpcore is 43.6%, based on public PR activity from non-core contributors.
pnp/pnpcore currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in pnp/pnpcore. Maintains strict focus on technical quality and test standards.
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/pnpcore?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (54% approval). Large PRs (>500 lines) take ~115 hours (20% approval). Keep your diff compact for rapid review.
⭐ Priority (Medium)😢 I'm annoyed but I'll live 📝 Describe the bug When building a batch and calling web.Lists.GetByIdBatchAsync(...) more than once using the same List ID, the operation fails with an exception. The issue occurs regardless of whether different expressions are specified for each call. It can also be reproduced without passing any expressions. This behavior prevents valid batch scenarios where the same list is requested multiple times with different loading requirements. 👣 Steps To Reproduce var batch = context.NewBatch(); var list1 = await web.Lists.GetByIdBatchAsync(batch, listId); var list2 = await web.Lists.GetByIdBatchAsync(batch, listId); await context.ExecuteAsync(batch); The same issue occurs when using different expressions: var batch = context.NewBatch(); var list1 = await web.Lists.GetByIdBatchAsync(batch, listId, p => p.Title); var list2 = await web.Lists.GetByIdBatchAsync(batch, listId, p => p.Id); await context.ExecuteAsync(batch); 📜 Expect
in flow https://github.com/pnp/pnpcore/blob/dev/.github/workflows/docfx.yml we should update EndBug/add-and-commit to use direct commit hash instead of tag. this is the same security improvement we already did in other actions and other workflows
⭐ Priority (Urgent)⚠️😱 I can't use the extension 📝 Describe the bug When a control (web part) is added to a flexible section, the data-sp-control data has an attribute for the section height (formatted for readability): <div data-sp-canvascontrol="" data-sp-canvasdataversion="1.0" data-sp-controldata=" { "position":{ "layoutIndex":1, "zoneIndex":1, "zoneId":"171c45d4-6db3-4d28-96f6-682c5f553547", "sectionIndex":1, "sectionFactor":100, "controlIndex":2 }, "zoneHeight":602, <------------------------------------------- "id":"8c7a9328-faf0-43e6-af20-446d5138103a", "controlType":3, "isFromSectionTemplate":true, "addedFromPersistedData":true, "flexibleLayoutPosition":{ "lg":{ "x":62, "y":25, "w":6, "h":6, "dataVersion":"1.0" } }, "webPartId":"d1d91016-032f-456d-98a4-721247c305e8", "reser
Category Bug Describe the bug Unable to add or set a Web Part inside of a Full Width Section even when the Web Part has supportsFullBleed or when passing in isFullWidth to PropertiesJson. I receive the following error: "You cannot host text controls inside a one column full width section, only an image web part or hero web part are allowed" This is an issue that has come and gone in the past and it looks like it might be back. #387 pnp/powershell#4719 (open) pnp/pnpframework#1045 The issue only appears to happen within the first top section of a Site Page (where a Page Header Web Part typically would be). You are able to set the same Web Part in a Full Width zone that is not the first section in the page. Steps to reproduce Create a full width page Add a custom web part at the top of the page (replacing the Page Title/Header Web Part) Save the page. Try to update the properties of the Web Part using Set_PnPPageWebpart or through the SDK $instanceId = "7f1fb168-1990-4bbc-b283-8386
Category Ensure Samples have minimum required assets e.g. readme and sample.json file Register the repo for ingestion with the solution sample gallery repo Update all the samples to reflect the changes and ensure each have metadata populated.
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/pnpcore, 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/pnpcore acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 43.6% were successfully merged into the primary branch.
pnp/pnpcore has a recorded first-timer success rate of 28.6%. 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 58.9 places pnp/pnpcore in the Welcoming tier.
The external pull request merge rate is 43.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pnp/pnpcore 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 pnp/pnpcore 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.