Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / elizaOS / eliza issue stats

Last synced: 5 days ago

Total issues: 249
Total pull requests: 391
Average time to close issues: 12 days
Average time to close pull requests: 2 days
Total issue authors: 113
Total pull request authors: 179
Average comments per issue: 3.2
Average comments per pull request: 1.59
Merged pull requests: 152
Bot issues: 1
Bot pull requests: 20

Past year issues: 249
Past year pull requests: 391
Past year average time to close issues: 12 days
Past year average time to close pull requests: 2 days
Past year issue authors: 113
Past year pull request authors: 179
Past year average comments per issue: 3.2
Past year average comments per pull request: 1.59
Past year merged pull requests: 152
Past year bot issues: 1
Past year bot pull requests: 20

More repo stats: https://repos.ecosyste.ms/hosts/GitHub/repositories/elizaOS/eliza
JSON API: https://issues.ecosyste.ms/api/v1/hosts/GitHub/repositories/elizaOS%2Feliza

Issue Author Associations

  • None (147, 59.04%)
  • Contributor (48, 19.28%)
  • Member (32, 12.85%)
  • Collaborator (22, 8.84%)

Pull Request Author Associations

  • None (184, 47.06%)
  • Contributor (134, 34.27%)
  • Collaborator (58, 14.83%)
  • Member (15, 3.84%)

Top Issue Authors

Top Pull Request Authors


All Maintainers

Active Maintainers


Top Issue Labels

  • bug (110)
  • enhancement (74)
  • Need Feedback (69)
  • Needs Testing (29)
  • no-issue-activity (17)
  • automation (6)
  • documentation (6)
  • Priority: High (6)
  • Client: Twitter (5)
  • V2 (2)
  • Needs Refactor (2)
  • Client: Telegram (2)
  • trust-system (2)
  • core-system (2)
  • characters (2)
  • good first issue (1)
  • algorithm (1)
  • ui (1)
  • ux (1)
  • Design (1)
  • voice (1)
  • testing (1)
  • Trading (1)
  • Client: Direct (1)

Top Pull Request Labels

  • Plugin_new (30)
  • Needs Testing (26)
  • needs_documentation (6)
  • testing (3)
  • ModelProvider_new (2)
  • Needs Refactor (2)
  • needs more work (2)
  • documentation (1)
  • automation (1)
  • enhancement (1)
  • infrastructure (1)
  • no push access (1)