Is tar-no-std safe to use?

tar-no-std has no known vulnerabilities on the latest version (0.4.2). DepScope rates its health at 58/100 (high risk).

What is the latest version of tar-no-std?

The latest version of tar-no-std is 0.4.2, released 2025-08-25.

Does tar-no-std have known vulnerabilities?

No known vulnerabilities on the latest version of tar-no-std.

Is tar-no-std deprecated?

No, tar-no-std is actively maintained. Latest release: 0.4.2 (2025-08-25).

What are alternatives to tar-no-std?

Popular alternatives to tar-no-std in Cargo include: hashbrown, getrandom, windows-sys, syn.

What license does tar-no-std use?

tar-no-std is licensed under MIT.

tar-no-std

cargov0.4.2

Library to read Tar archives (by GNU Tar) in `no_std` contexts with zero allocations. The crate is simple and only supports reading of "basic" archives, therefore no extensions, such as GNU Longname. The maximum supported file name length is 256 characters excluding the NULL-byte (using the tar name/prefix longname implementation).The maximum supported file size is 8GiB. Directories are supported, but only regular fields are yielded in iteration.

License MITpermissive19 versions0 deps131,973 weekly dl

phip1611/tar-no-std

/ 100

Health

safe to use

[email protected] is safe to use (health: 58/100)

Health breakdown0 – 100

10/25

maintenance

14/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/cargo/tar-no-std