Community-driven baseline to accelerate Intune adoption and learning.
C-Rank Grade: D (Risky) - 11/100
External PR Merge Rate: -
Response Time: <1h
First Timer Success: -
SkipToTheEndpoint/OpenIntuneBaseline has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in SkipToTheEndpoint/OpenIntuneBaseline 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 10.8 places SkipToTheEndpoint/OpenIntuneBaseline in the D tier.
The external contributor pull request merge rate for SkipToTheEndpoint/OpenIntuneBaseline is 0.0%, based on public PR activity from non-core contributors.
SkipToTheEndpoint/OpenIntuneBaseline currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Community-driven baseline to accelerate Intune adoption and learning.
Collaborative maintainer environment in SkipToTheEndpoint/OpenIntuneBaseline. Reviews community pull requests with focus on project quality.
Discussions in SkipToTheEndpoint/OpenIntuneBaseline 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/SkipToTheEndpoint/OpenIntuneBaseline?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (81% approval). Large PRs (>500 lines) take ~0 hours (29% approval). Keep your diff compact for rapid review.
Baseline Info (please complete the following information): OS: [e.g. Windows] Version: [e.g. 3.6] - version 3.6 policies tested Describe the bug These existing .json files in this repo do not reflect recent changes in graph. For example, STIG audit baseline features. To be more specific, the stored .json policies in this repo do not have auditRuleInformation. When assigned, this line is appended for each setting. This causes M365 policy management tools to report drift/mismatch (e.g. Nerdio Manager and Inforcer). solution: The policies need to be updated to reflect the latest intune/graph changes. To Reproduce Steps to reproduce the behaviour: Sync this repo. Assign one of the itnune policies. compare the differences between the GH source .json policy and the .json that lands in the tenant. you will see auditRuleInformation added to the destination tenant polciy and these are absent in these policies here. Expected behaviour Policies should match aside from a few little expected meta
Is your feature request related to a problem? Please describe. Recently there were negative news about this feature with LG monitors installing things without user consent resulting in ads on the system. This would also prevent popups for things "Install Logi Options" when adding a Logitech device to a computer. This one can be quite irritating (to at least our users), as they do not have the rights to install this, but still get the popup. I guess there will be more cases like this. Describe the solution you'd like Adding that setting, set to "enabled" into the "Win - OIB - SC - Windows User Experience - D - Feature Configuration". Seemed to be the most fitting one for this. Describe alternatives you've considered I have set it by hand for now, but I think and inclusion in the baseline is warranted.
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 SkipToTheEndpoint/OpenIntuneBaseline, 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 SkipToTheEndpoint/OpenIntuneBaseline acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
SkipToTheEndpoint/OpenIntuneBaseline has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 10.8 places SkipToTheEndpoint/OpenIntuneBaseline in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, SkipToTheEndpoint/OpenIntuneBaseline 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 SkipToTheEndpoint/OpenIntuneBaseline 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.