These charts show monthly counts of newly filed issues and pull
requests on github.com/[org], so you can watch how
open-file activity has changed over time. Each open is counted once, in
the month it was created (body text is not used). The scan covers
[repo_count] repositories that finished scraping
(org repository list last refreshed [repos_listed_at] UTC).
Source volume: [event_count] opens in total ([issue_count] issues and [pr_count] pull requests), spanning [date_range] ([month_count] calendar months with at least one open in the dataset). Report generated [generated_at] UTC.
Author groups (used as the three lines on each chart):
committer — the GitHub account that filed the open is
linked to an ASF committer in LDAP (Boxer-style GitHub binding:
numeric id and/or login). This is not “everyone with an Apache account,”
only those who have linked GitHub.
unknown — human-looking filers not matched to that LDAP
map (includes outsiders and ASF committers who never linked GitHub, or
who filed from a different account).
bot — known automation (dependabot, renovate, GitHub
Actions bots, etc.). Bots use the right-hand axis so small bot counts
stay visible without dominating the human open scales.
Overall mix of opens (entire period): committer [group_committer] ([pct_committer]), unknown [group_unknown] ([pct_unknown]), bot [group_bot] ([pct_bot]).
Committer map (LDAP import): [map_total] ASF committer accounts in the map; [map_linked] ([pct_map_linked]) have a GitHub id and/or login ([map_with_id] with numeric id, [map_with_login] with login string); [map_neither] have neither and can never match a GitHub open as “committer.” Unlinked committers who file issues/PRs appear under unknown, so the committer line is a lower bound on true committer participation on GitHub.