License
exav is licensed under the MIT License (see
LICENSE): every crate,
and the @exav/unpack-wasm and @exav/viewer npm packages. What the viewer
bundles, and the engines installed beside it, keep their own licenses (see
File viewer).
Third-party notices
Section titled “Third-party notices”The exav binary statically links third-party crates under permissive licenses,
whose required notices are reproduced in
NOTICE. A build with the
http feature, such as the published image, also links the ring TLS
primitives and the webpki-roots certificate store. Among the rest:
- exav’s native YARA engine reuses and adapts the YARA-X parser,
source and test vectors under BSD-3-Clause, with attribution retained
(
crates/exav-core/LICENSE-YARA-X). It compiles rules to a native tree-walking evaluator, with no WASM runtime or JIT behind it. - exav also contains code ported or derived from permissively licensed projects
(RAR, AZO, CAB, DMG, PPMd and bzip2 decoders among them, the HWP3 layout, and
iced-x86’s generated decoder tables), each attributed inNOTICE. - exav-render’s office converters (spreadsheets, presentations, text
documents) are written from published specifications, among them
Microsoft’s Open Specifications and the OASIS OpenDocument standard, and
from what other converters do with sample files, used as a black box. No code
of another office application is in them. The specifications, the tables and
message layouts taken from MIT-licensed projects (numbers-parser and
keynote-parser), and the test fixtures are listed in
crates/exav-render/NOTICE. - The WASM sandbox runs exav under a WASI runtime you provide, under its own license; exav does not bundle it. See the WASM sandbox guide.
The GPL signature database
Section titled “The GPL signature database”exav does not bundle or redistribute the GPL-licensed ClamAV signature database.
It can read the CVD format (reading a format is interoperability, not
redistribution), but the signatures are fetched by you, with freshclam or
cvdupdate, or with exav’s --auto-update from a URL you supply.
See Signatures.
exav ships no signature database of its own, only a built-in EICAR test signature; real detection comes from databases you supply.
Clean-room provenance
Section titled “Clean-room provenance”All exav code was written independently from public specifications and permissively licensed sources, and derives nothing from ClamAV’s GPLv2 source. See Contributing for the clean-room rule.