| Vulnerabilities | |||||
|---|---|---|---|---|---|
| Version | Suggest | Low | Medium | High | Critical |
| 1.11.0 | 0 | 0 | 0 | 0 | 0 |
| 1.10.0 | 0 | 0 | 0 | 0 | 0 |
| 1.9.0 | 0 | 0 | 0 | 0 | 0 |
| 1.8.1 | 0 | 0 | 0 | 0 | 0 |
| 1.8.0 | 0 | 0 | 0 | 0 | 0 |
| 1.7.0 | 0 | 0 | 0 | 0 | 0 |
| 1.6.1 | 0 | 0 | 0 | 0 | 0 |
| 1.6.0 | 0 | 0 | 0 | 0 | 0 |
| 1.5.1 | 0 | 0 | 0 | 0 | 0 |
| 1.5.0 | 0 | 0 | 0 | 0 | 0 |
| 1.4.0 | 0 | 0 | 0 | 0 | 0 |
| 1.3.1 | 0 | 0 | 0 | 0 | 0 |
| 1.3.0 | 0 | 0 | 0 | 0 | 0 |
| 1.2.0 | 0 | 0 | 0 | 0 | 0 |
| 1.1.1 | 0 | 0 | 0 | 0 | 0 |
| 1.1.0 | 0 | 0 | 0 | 0 | 0 |
| 1.0.1 | 0 | 0 | 0 | 0 | 0 |
| 1.0.0 | 0 | 0 | 0 | 0 | 0 |
| 0.4.1 | 0 | 0 | 0 | 0 | 0 |
| 0.4.0 | 0 | 0 | 0 | 0 | 0 |
| 0.3.4 | 0 | 0 | 0 | 0 | 0 |
| 0.3.3 | 0 | 0 | 0 | 0 | 0 |
| 0.3.2 | 0 | 0 | 0 | 0 | 0 |
| 0.3.1 | 0 | 0 | 0 | 0 | 0 |
| 0.3.0 | 0 | 0 | 0 | 0 | 0 |
| 0.2.0 | 0 | 0 | 0 | 0 | 0 |
| 0.1.2 | 0 | 0 | 0 | 0 | 0 |
| 0.1.1 | 0 | 0 | 0 | 0 | 0 |
| 0.1.0 | 0 | 0 | 0 | 0 | 0 |
| 0.0.0 | 0 | 0 | 0 | 0 | 0 |
1.11.0 - This version is safe to use because it has no known security vulnerabilities at this time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform
Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.
MIT - MIT LicenseA 100% safe crate of vec-like types.
Not just safe at the public API boundary, fully safe for all internal code too: #![forbid(unsafe_code)]
The provided types are as follows:
ArrayVec is an array-backed vec-like data structure. It panics on overflow.SliceVec is similar, but using a &mut [T] as the data backing.TinyVec (alloc feature) is an enum that's either an Inline(ArrayVec) or a Heap(Vec).
If a TinyVec is Inline and would overflow its array it automatically transitions to Heap and continues whatever it was doing.To attain this "100% safe code" status there is one compromise: the element type of the vecs must implement Default.
For more API details, please see the docs.rs documentation
Maybe you don't want to use tinyvec, there's other crates you might use instead!
The main difference is that both of those crates use unsafe code.
This mostly allows them to get rid of the Default limitation for elements that tinyvec imposes.
The smallvec and arrayvec crates are generally correct, but there's been occasional bugs leading to UB.
With tinyvec, any uncaught bugs can't lead to UB, because the crate is safe code all the way through.
If you want that absolute level of assurance against UB, use tinyvec.