https://github.com/openwrt/firewall4.git
active 2025-03-16 → 2026-06-19 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 461 days from 2025-03-16 to 2026-06-19. Pushes: 0 total, peak 0 in a day. Pull requests: 8 total, peak 2 in a day. Issues: 12 total, peak 2 in a day. Comments: 75 total, peak 5 in a day. Stars: 9 total, peak 1 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| brada4 | 51 | 0 | 3 | 41 |
| lowjoel | 6 | 0 | 0 | 3 |
| ckorber | 6 | 0 | 1 | 5 |
| brianjmurrell | 5 | 0 | 0 | 3 |
| pprindeville | 5 | 0 | 0 | 4 |
| whiskerp | 3 | 0 | 0 | 2 |
| XCas13 | 3 | 0 | 1 | 1 |
| lantis1008 | 2 | 0 | 0 | 1 |
| Nicole-Norris | 2 | 0 | 1 | 1 |
| systemcrash | 2 | 0 | 0 | 2 |
| abajk | 2 | 0 | 0 | 1 |
| l-jonas | 2 | 0 | 0 | 2 |
| fonoirs | 2 | 0 | 0 | 1 |
| Neustradamus | 1 | 0 | 0 | 1 |
| dave14305 | 1 | 0 | 0 | 0 |
| vendolis | 1 | 0 | 0 | 1 |
| Djfe | 1 | 0 | 0 | 1 |
| saldry | 1 | 0 | 1 | 0 |
| stintel | 1 | 0 | 0 | 1 |
| feckert | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#92stintel2026-05-07 22:35ruleset: avoid port translating local sockets
- Issue#94brada42026-05-03 03:28Maintenance?
- Issue comment#93pprindeville2026-04-28 16:50firewall4: should enforce "strong host" model
- Issue comment#93l-jonas2026-04-28 04:43firewall4: should enforce "strong host" model
- Issue comment#93l-jonas2026-04-27 05:14firewall4: should enforce "strong host" model
- Issue comment#93pprindeville2026-04-16 05:07firewall4: should enforce "strong host" model
- Issue comment#93pprindeville2026-04-15 22:19firewall4: should enforce "strong host" model
- Issue comment#93pprindeville2026-04-11 23:20firewall4: should enforce "strong host" model
- Issue#93pprindeville2026-04-10 17:48firewall4: should enforce "strong host" model
- Issue comment#90brada42026-03-20 08:13add Anti-spoof rules
- Issue comment#74brada42026-02-25 10:13fw4: enable mac ranges for rule
- Issue comment#74systemcrash2026-02-24 15:32fw4: enable mac ranges for rule
- Issue comment#57brianjmurrell2026-02-05 14:50Allow use of `option src '!wan'`
- Issue comment#88brianjmurrell2026-01-22 18:54Apostrophe in single quotes causes silent failure
- Issue comment#41brada42026-01-18 21:42ruleset: do not emit extra l4proto filter for helpers
- Issue#86dave143052026-01-13 00:53Unwanted mangle-rule.uc template
- Pull request#85saldry2026-01-07 07:59
- Issue comment#84brada42026-01-06 20:17Could firewall4 use iif/oif instead of iifname/oifname?
- Issue comment#41brada42025-11-28 00:15ruleset: do not emit extra l4proto filter for helpers
- Issue comment#84brada42025-11-27 17:03Could firewall4 use iif/oif instead of iifname/oifname?
- Issue comment#74systemcrash2025-11-26 21:29fw4: enable mac ranges for rule
- Issue comment#74ckorber2025-11-26 10:20fw4: enable mac ranges for rule
- Issue comment#82brada42025-11-12 09:32/usr/share/nftables.d/chain-post will not get included if corresponding chain is not used in /etc/config/firewall
- Issue comment#82brada42025-11-12 08:43/usr/share/nftables.d/chain-post will not get included if corresponding chain is not used in /etc/config/firewall
- Issue comment#82brada42025-11-12 08:42/usr/share/nftables.d/chain-post will not get included if corresponding chain is not used in /etc/config/firewall
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 9 stars here means stars gained during the window, not the repo's star count.