-
Notifications
You must be signed in to change notification settings - Fork 45
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: PSeitz/lz4_flex
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0.12.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: PSeitz/lz4_flex
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 0.13.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 8 commits
- 16 files changed
- 6 contributors
Commits on Jan 28, 2026
-
To draw attention to the enabled "private vulnerability reporting" feature. Because unlike the SECURITY.md file which is prominently shown in a few places in the GitHub UI, the "private vulnerability reporting" feature can be difficult to find in case users are not aware that it exists.
Configuration menu - View commit details
-
Copy full SHA for 7b5fb80 - Browse repository at this point
Copy the full SHA 7b5fb80View commit details
Commits on Feb 19, 2026
-
fix get_maximum_output_size overflow on 32-bit targets
Cast input_len to u64 before multiplying by 110, avoiding overflow on 32-bit targets (e.g. wasm32) where `input_len * 110` overflows usize when input_len > 2^32 / 110 ≈ 39MB. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Configuration menu - View commit details
-
Copy full SHA for 2991a09 - Browse repository at this point
Copy the full SHA 2991a09View commit details
Commits on Mar 5, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 22e77f9 - Browse repository at this point
Copy the full SHA 22e77f9View commit details
Commits on Mar 6, 2026
-
Configuration menu - View commit details
-
Copy full SHA for c90fc91 - Browse repository at this point
Copy the full SHA c90fc91View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1bdafca - Browse repository at this point
Copy the full SHA 1bdafcaView commit details -
Configuration menu - View commit details
-
Copy full SHA for 7191df8 - Browse repository at this point
Copy the full SHA 7191df8View commit details
Commits on Mar 14, 2026
-
fix handling of invalid match offsets during decompression
* fix handling of invalid match offsets during decompression * extend decompress tests * remove ineffective zeroing of memory Is redundant now due to new `offset == 0` check. And it looks like previously this zeroing did not work as desired anyway: It only affected the first byte but did not help for any subsequently copied bytes. The LZ4 C implementation it is referring to does this differently. * fuzz decompression with MemorySanitizer * remove inline(always) to avoid performance regression inline(always) is a footgun. In combination with the changes in read_match_offset the performance degrades by 50% in some cases.
Configuration menu - View commit details
-
Copy full SHA for 055502e - Browse repository at this point
Copy the full SHA 055502eView commit details
Commits on Mar 15, 2026
-
Configuration menu - View commit details
-
Copy full SHA for bfaae84 - Browse repository at this point
Copy the full SHA bfaae84View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 0.12.0...0.13.0