Project Summary
BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides replacements for most of the utilities you usually find in GNU fileutils, shellutils, etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however, the options that are included provide the expected functionality and behave very much like their GNU counterparts. BusyBox provides a fairly complete environment for any small or embedded system.
BusyBox has been written with size-optimization and limited resources in mind. It is also extremely modular so you can easily include or exclude commands (or features) at compile time. This makes it easy to customize your embedd
In a Nutshell, BusyBox...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a large development team
with decreasing Y-O-Y commits -
...
took an estimated 55 years of effort (COCOMO model)
starting with its first commit in October, 1999
ending with its most recent commit about 1 month ago
Quick Reference
GNU General Public License v2.0 or later
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Forbidden
Sub-License
Hold Liable
Required
Distribute Original
Disclose Source
Include Copyright
State Changes
Include License
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
Project Vulnerability Report
Security Confidence Index
Vulnerability Exposure Index
Did You Know...
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
search using multiple tags to find exactly what you need
-
...
65% of companies leverage OSS to speed application development in 2016
-
...
by exploring contributors within projects, you can view details on every commit they have made to that project
30 Day SummaryApr 30 2025 — May 30 2025
|
12 Month SummaryMay 30 2024 — May 30 2025
|
