communitytoolkit/windowscommunitytoolkit vs nickemanarin/screentogif
Both showing Mixed signals — pick on fit, not health
As of September 2026, windowscommunitytoolkit and screentogif both show mixed maintenance signals. windowscommunitytoolkit last saw a commit 1 year ago with 12+ active contributors, while screentogif last saw a commit 1 month ago with 13+ active contributors. windowscommunitytoolkit is MIT-licensed while screentogif is MS-PL-licensed. Neither has known critical or high-severity CVEs in its dependency tree.
Informational only. RepoPilot summarises public signals at the time of analysis. Not professional, security, or legal advice.
communitytoolkit/windowscommunitytoolkit
Stale — last commit 2y ago
last commit was 2y ago; no tests detected in the complete Git tree…
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
last commit was 2y ago; Scorecard "Branch-Protection" is 0/10…
- ⚠Stale — last commit 2y ago
- ⚠No tests detected in the complete Git tree
- ⚠Scorecard: marked unmaintained (0/10)
- ⚠Scorecard: default branch unprotected (0/10)
- ✓12 active contributors
- ✓Distributed ownership (top contributor 43% of recent commits)
- ✓MIT licensed
- ✓CI configured
What would improve this?
- •Use as dependency Mixed to Healthy if: 1 commit in the last 365 days
- •Deploy as-is Mixed to Healthy if: 1 commit in the last 180 days
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
nickemanarin/screentogif
Mixed signals — read the receipts
non-standard license (MS-PL); no tests detected in the complete Git tree…
No blocking repository signals were found — inspect the evidence before forking.
Documented and popular — useful reference codebase to read through.
Scorecard "Branch-Protection" is 0/10; dependency CVE scan unavailable
- ⚠Concentrated ownership — top contributor handles 66% of recent commits
- ⚠Non-standard license (MS-PL) — review terms
- ⚠No tests detected in the complete Git tree
- ⚠Scorecard: default branch unprotected (0/10)
- ✓Last commit 5w ago
- ✓13 active contributors
- ✓MS-PL licensed
- ✓CI configured
What would improve this?
- •Use as dependency Concerns to Mixed if: clarify license terms
Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard
Signal-by-signal breakdown
| windowscommunitytoolkit | screentogif | |
|---|---|---|
| Stars | 6,070 | 27,590 |
| Last commit | 1y ago | 1mo ago |
| License | MIT | MS-PL |
| Open issues | 314 | 331 |
| Has tests | No | No |
| Has CI | ✓ | ✓ |
| Test coverage | 0% | 0% |
| Dependency CVEs | No CVEs | No CVEs |
| Architecture grade | C | C |
| Cycles | 0 | 0 |
| Bottom-line | Mixed signals | Mixed signals |
Want the full analysis? communitytoolkit/windowscommunitytoolkit · nickemanarin/screentogif
Ask AI about communitytoolkit/windowscommunitytoolkit vs nickemanarin/screentogif
Open the chat with a comparison question pre-filled.