Blosc

Latest version: v1.11.2

Safety actively analyzes 714815 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 7

1.16.3

=============================

- Fix for building for clang with -march=haswell. See PR 262.

- Fix all the known warnings for GCC/Clang. Still some work to do for MSVC
in this front.

- Due to some problems with several CI systems, the check for library symbols
are deactivated now by default. If you want to enforce this check, use:
`cmake .. -DDEACTIVATE_SYMBOLS_CHECK=ON` to re-activate it.

1.16.2

- Correct the check for the compressed size when the buffer is memcpyed. This
was a regression introduced in 1.16.0. Fixes 261.

1.16.1

- Fixed a regression in 1.16.0 that prevented to compress empty buffers
(see 260).

- Zstd updated to 1.3.8 (from 1.3.7).

1.16.0

- Now the functions that execute Blosc decompressions are safe by default
for untrusted/possibly corrupted inputs. The additional checks seem to
not affect performance significantly (see some benchmarks in 258), so
this is why they are the default now.

The previous functions (with less safety) checks are still available with a
'_unsafe' suffix. The complete list is:

- blosc_decompress_unsafe()
- blosc_decompress_ctx_unsafe()
- blosc_getitem_unsafe()

Also, a new API function named blosc_cbuffer_validate(), for validating Blosc
compressed data, has been added.

For details, see PR 258. Thanks to Jeremy Maitin-Shepard.

- Fixed a bug in `blosc_compress()` that could lead to thread deadlock under
some situations. See 251. Thanks to wenjuno for the report and the fix.

- Fix data race in shuffle.c host_implementation initialization. Fixes 253.
Thanks to Jeremy Maitin-Shepard.

1.15.1

This is a maintenance release that adds a workaround for Visual Studio
2008's lack of a stdint.h file to blosclz.c.

For more info, please see the release notes in:

https://github.com/Blosc/c-blosc/blob/master/RELEASE_NOTES.rst

1.15.0

In this release, the `blosc_compress()` and `blosc_decompress()` interfaces
are now fork-safe, preventing child-process deadlocks in fork-based
multiprocessing applications. These interfaces with BLOSC_NOLOCK were, and
continue to be, fork-safe. `_ctx` interface context reuse continues to be
unsafe in the child process post-fork. Thanks to Alex Ford.

Also, a few bugs have been fixed, more compatibility with oldish compilers
and LZ4 and Zstd codecs have been updated to their latest versions.

For more info, please see the release notes in:

https://github.com/Blosc/c-blosc/blob/master/RELEASE_NOTES.rst

Page 3 of 7

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.