Ecosyste.ms: Issues

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

GitHub / inverse-inc / packetfence issue stats

Last synced: about 2 months ago

Total issues: 168
Total pull requests: 202
Average time to close issues: 5 months
Average time to close pull requests: 4 months
Total issue authors: 47
Total pull request authors: 16
Average comments per issue: 1.26
Average comments per pull request: 1.4
Merged pull requests: 123
Bot issues: 0
Bot pull requests: 17

Past year issues: 71
Past year pull requests: 96
Past year average time to close issues: 21 days
Past year average time to close pull requests: 25 days
Past year issue authors: 27
Past year pull request authors: 8
Past year average comments per issue: 0.87
Past year average comments per pull request: 0.95
Past year merged pull requests: 71
Past year bot issues: 0
Past year bot pull requests: 7

More repo stats: https://repos.ecosyste.ms/hosts/GitHub/repositories/inverse-inc/packetfence
JSON API: https://issues.ecosyste.ms/api/v1/hosts/GitHub/repositories/inverse-inc%2Fpacketfence

Issue Author Associations

  • Contributor (74, 44.05%)
  • None (68, 40.48%)
  • Member (25, 14.88%)
  • Collaborator (1, 0.60%)

Pull Request Author Associations

  • Contributor (131, 64.85%)
  • Member (68, 33.66%)
  • None (2, 0.99%)
  • Collaborator (1, 0.50%)

Top Issue Authors

Top Pull Request Authors


All Maintainers

Active Maintainers


Top Issue Labels

  • Type: Bug (120)
  • Priority: High (41)
  • tests (21)
  • Priority: Medium (18)
  • Type: Feature / Enhancement (18)
  • Priority: Low (8)
  • Priority: Critical (8)
  • Configurator (2)
  • zammitbug (2)
  • Customer (2)
  • go (1)
  • Tech debt (1)

Top Pull Request Labels

  • Status: For review (39)
  • Priority: High (30)
  • dependencies (17)
  • go (12)
  • Type: Feature / Enhancement (11)
  • Status: In progress (9)
  • Priority: Medium (7)
  • Type: Bug (6)
  • Status: Tested and works (6)
  • Priority: Low (5)
  • javascript (5)
  • Status: Fix confirmed (4)
  • Priority: Critical (4)
  • Documentation (2)
  • Status: Not ready (2)
  • segmentation (2)