Community maintained packages for OpenWrt. Documentation for submitting pull requests is in CONTRIBUTING.md
AI Analysis
OpenWrt packages is the official community-maintained feed of build scripts, patches, and configurations for applications and libraries used in OpenWrt router firmware. It serves embedded Linux developers, network administrators, and router enthusiasts who need to compile custom firmware or manage OpenWrt package installations. This project is not for general-purpose application development—it is specialized infrastructure for OpenWrt ecosystem participants.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Official OpenWrt community package feed: build scripts for thousands of applications in embedded Linux systems
openwrt/packages is the official community-maintained feed for OpenWrt, a Linux distribution for embedded devices and routers. It provides build recipes, patches, and configuration for thousands of applications, libraries, and kernel modules. Used by OpenWrt developers, device manufacturers, and hobbyists building custom firmware. It is essential infrastructure for the OpenWrt ecosystem rather than a user-facing application.
Created in 2014 as part of OpenWrt's modularization of the build system. The packages feed separates application and library packaging from core system components, allowing community contributions to be vetted and integrated into the main buildroot. It has grown with OpenWrt's adoption in ISP deployments, home networking, and IoT devices.
Steady growth correlating with OpenWrt's maturation and wider adoption in commercial and hobbyist networking. The fork landscape (kenzok8, Lienol, fw876 variants) indicates demand for extended package sets, though these appear to be regional or specialty distributions rather than replacements. Recent activity (last push 2026-06-30) shows ongoing maintenance with 13 stars gained in last 7 days, typical for infrastructure projects serving existing users rather than acquiring new ones.
Adoption not formally documented in README, but can be inferred from: (1) OpenWrt's known deployment in hundreds of thousands of networking devices globally via ISPs and manufacturers; (2) presence of competing forks (kenzok8, Lienol) indicating parallel ecosystem usage; (3) core integration into OpenWrt buildroot means packages feed is used in every OpenWrt build pipeline by definition. Actual end-user adoption is indirect but substantial.
Makefile-based build system layered on OpenWrt buildroot. Appears to use a feed structure where individual packages are defined as modular recipes. README indicates integration via `./scripts/feeds` utilities. Likely organized as a collection of package Makefiles and patches rather than a monolithic application.
not documented in README
Last push on 2026-06-30 (within hours of analysis date) indicates active maintenance. 4,538 stars and 3,902 forks suggest established, widely-referenced project. However, growth rate (13 stars/7 days) is consistent with stable infrastructure maintenance rather than rapid expansion. No evidence of stagnation; appears to operate on a steady-state maintenance model.
ADOPT IF: you are building custom OpenWrt firmware and need access to the official package repository. The feed is already integrated into the standard buildroot and is the canonical source for community-maintained packages. AVOID IF: you are looking for a general-purpose package manager for non-embedded systems, or if you need packages outside the OpenWrt ecosystem. MONITOR IF: you are evaluating OpenWrt for a project and want to understand the maturity and breadth of available packages—fork activity suggests some users supplement the official feed, which may indicate gaps in coverage for certain regions or use cases.
Independent dimensions
Mainstream potential
3/10
Technical importance
7/10
Adoption evidence
8/10
- Quality variance: as a community-maintained feed, package quality and security review rigor likely varies across thousands of entries. README does not document vetting process.
- Maintenance burden: large number of packages (thousands inferred) may create long-tail maintenance risk where rarely-used packages fall out of sync with upstream or security patches.
- Regional fragmentation: presence of multiple active forks suggests some users don't fully trust or prefer official feed, which could indicate governance or transparency concerns not visible in README.
- Dependency on OpenWrt stability: packages feed is tightly coupled to OpenWrt buildroot; breaking changes in core system could cascade.
- Documentation gaps: README is minimal; actual package-submission workflow and quality standards appear documented elsewhere (CONTRIBUTING.md), reducing discoverability.
Likely to remain stable and essential infrastructure for OpenWrt ecosystem. Slow, steady growth as embedded Linux and IoT deployments continue. May see increased formalization of quality/security review processes if OpenWrt adoption grows in high-security contexts (industrial, carrier). Competing forks unlikely to diminish official feed's importance but may persist as regional variants.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- Makefile
- License
- GPL-2.0
- Last updated
- 7h ago
- Created
- 147mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Similar repos
kenzok8/openwrt-packages
OpenWrt-packages is a curated collection of LuCI applications, themes, and...
unifreq/openwrt_packit
This project packages OpenWrt firmware for ARM64 single-board computers and TV...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
|
4.6k | +12 | Makefile | 7/10 | 7h ago |
|
|
27.5k | — | C | 8/10 | 1d ago |
|
|
7.2k | — | Shell | 7/10 | 4h ago |
|
|
3.7k | — | C | 7/10 | 2w ago |
|
|
1.7k | — | Shell | 6/10 | 1mo ago |
|
|
4.2k | — | C | 6/10 | 6d ago |
Parent project containing core system. packages feed is explicitly layered on top; complementary, not competitive. Main repo has 6x more stars, reflects higher visibility but serves different purpose.
Community fork with 7,138 stars, appears to be Chinese/Asian focused extended package set. Suggests some users prefer additional or pre-selected packages; indicates packages feed alone may not meet all regional or specialized demands.
Another fork with 3,654 stars, likely regional variant. Existence suggests packages feed serves as baseline but doesn't fully capture all user needs in certain markets or use cases.
Specialized package repository (4,162 stars), appears focused on specific application category rather than general packages. Complements rather than competes with official feed.
1,667 stars, shell-based utility. Appears to be build/packaging tool rather than package collection. Orthogonal purpose.