`ant-releases`: extracting a release archive can write files outside the destination directory (path traversal / zip-slip)

Summary

`ant-releases` downloads and unpacks release archives from the `safe_network` / `autonomi` repositories. When it extracts an archive, it builds each output path by joining the archive entry's **own name** onto the destination directory, with no check for `..` or absolute components — a classic "zip-slip" path traversal (CWE-22 / CWE-23). A crafted archive can therefore create or overwrite files outside the intended extraction directory.

In `extract_release_archive` (`src/lib.rs`), the ZIP branch does:

```rust let out_path = dest_dir_path.join(file.name()); // raw zip entry name, no containment check if file.name().ends_with('/') { std::fs::create_dir_all(&out_path)?; // dir created outside dest_dir } else { let mut outfile = std::fs::File::create(&out_path)?; // file written outside dest_dir std::io::copy(&mut file, &mut outfile)?; } ```

## Proof of concept

A one-entry ZIP whose entry name is `../foo_pwned.txt`, passed to `AntReleaseRepoActions::extract_release_archive` (obtained via the crate's public `<dyn AntReleaseRepoActions>::default_config()`), writes `foo_pwned.txt` as a sibling of the destination directory, outside it. Confirmed against the published `0.4.3` crate.