Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / libretro / mupen64plus-libretro-nx issue stats
Last synced: 8 months ago
Total issues: 106
Total pull requests: 44
Average time to close issues: 3 months
Average time to close pull requests: 4 months
Total issue authors: 91
Total pull request authors: 22
Average comments per issue: 4.76
Average comments per pull request: 2.8
Merged pull requests: 21
Bot issues: 0
Bot pull requests: 1
Past year issues: 27
Past year pull requests: 18
Past year average time to close issues: 2 days
Past year average time to close pull requests: about 2 months
Past year issue authors: 26
Past year pull request authors: 9
Past year average comments per issue: 1.22
Past year average comments per pull request: 2.0
Past year merged pull requests: 7
Past year bot issues: 0
Past year bot pull requests: 0
JSON API: https://issues.ecosyste.ms/api/v1/hosts/GitHub/repositories/libretro%2Fmupen64plus-libretro-nx
Issue Author Associations
- None (98, 92.45%)
- Contributor (8, 7.55%)
Pull Request Author Associations
- Contributor (28, 63.64%)
- None (15, 34.09%)
- Member (1, 2.27%)
Top Issue Authors
- Papermanzero (4)
- AngelofMe (4)
- Tasosgemah (3)
- nijoakim (3)
- Gagert (3)
- ghost (2)
- Agusum (2)
- bslenul (2)
- isidoro-80 (1)
- soundsnow (1)
- asciibeats (1)
- Yqnn (1)
- Newtype14 (1)
- legluondunet (1)
- BParks21 (1)
Top Pull Request Authors
- warmenhoven (15)
- bslenul (4)
- Themaister (4)
- mudlord (3)
- mountnside (1)
- doctor-amaton (1)
- jdorigao (1)
- cruduxcru0 (1)
- thelamer (1)
- dmrlawson (1)
- Thundertheidiot (1)
- CEnnis91 (1)
- Sanaki (1)
- lgtm-com[bot] 🤖 (1)
- zoltanvb (1)
All Maintainers
- kivutar (1)
Active Maintainers
Top Issue Labels
- information (4)
- upstream issue (4)
- revisit later (3)
- investigating (2)
- mitigate (2)
- more infos needed (2)
- architectural bug (1)
- question (1)
- help wanted (1)
- High Prio (1)
- bug (1)
- unverified bug (1)
- Feature Requested (1)
- enhancement (1)
- majoras issue (1)
- internally fixed (1)
- upstream fixed (1)
- wontfix (1)
- its on a branch (1)
- good first issue (1)
- invalid (1)