Browse / Other
lmmx/mibz2
No description on GitHub.
Works.Tested on 2026-10-27. From the README alone, on Linux with Haiku.
What we checked
Does it run from the README?Yes. Running in 4:38 on a clean Linux box.The run
Tested Oct 27, 2026, rev 24169e6.
Does it do what the README says?2 of 2 claims held up.Evidence
“Output is byte-for-byte libbzip2's and every block and stream CRC is checked”
Expected decoded blocks identical in libbzip2 and lbzip2 with CRC checked. Got every block CRC checked: identical in libbzip2, lbzip2.
“Documented windows example command decodes a .bz2 window file”
Expected 1 blocks, 5200 bytes, 0 windows failed. Got 1 blocks, 5200 bytes, 0 windows failed.
Which setups did we try?Works with Haiku. Unverified with Luna.Setups
Linux / Haiku: works, Oct 27, rev 24169e6. Linux / Luna: unverified, Oct 27, rev 24169e6.
Needs keys, a login or a browser?No.Details
None seen
Is it safe to run?Made outbound HTTPS connections: yes (hosts not recorded) by <guest-path>What we saw
Review signals across current setups: connection review. 12 listed items (named-host connections, static matches, dependency advisories) are below and do not change this verdict.
Repository processes attempted these non-loopback connections; proxies can hide the final hostname. 8 distinct locations. 2 attributed processes.
OSV reports a known vulnerability in this dependency version. zip 3 findings.
Reviewed as expected for a test run: attempted writes that failed, so nothing was written; package managers (cargo) downloaded dependencies over HTTPS; package managers (rustup-init) downloaded dependencies over HTTPS; resolver address lookups that send no data; wrote only to its own open file handles.
Reviewed as expected for a test run: attempted writes that failed, so nothing was written; wrote only to its own open file handles.
Full event, path and process lists for each observed setup:
A quiet run is not a safety guarantee.
Is it maintained?Maintained · 42 commits in 90 days · 19 merged PRs in 90 days · 4 open issues · 1 open PRsActivity
actively maintained: last commit 0 days ago; 42 commits and 19 merged PRs in 90 days; 4 open issues, 1 open PRs; latest release 2026-10-27
Can I show this on my README?Copy the badge.Badge
The run
Oct 27 · rev 24169e6Independent test, not endorsed by the project.