Status: UNDER REVIEW (2026-11-15). The earlier version assumed published open-source software. The runtime source is private, so the published-source exemption (reasoning 1) is not relied on. Counsel to redo this assessment. What stays true as facts: the product contains no encryption functionality (table above) and no encryption crates are in the lockfile.
What Aster is, for classification purposes
A CPU rendering, layout and UI library plus an application framework (documents, collaboration protocol, plugin host). It processes pixels, text, fonts, images, vector paths and document operations. Distributed as compiled binaries under the Aster Runtime EULA.
Cryptography check
The question that drives classification is whether the software has "information security" functionality (encryption, decryption, authentication, digital signatures, key management) as a function it provides.
| Check | Result | Evidence |
|---|---|---|
| Crypto crates in the default dependency graph (sha, aes, ring, rustls, openssl, hmac, chacha, TLS) | None. The no-I/O guard rejects these names in the default graph of the core crates and aster-appkit | tools/trust/no-io-check.sh (DENY list); rust/Cargo.lock |
Crypto crates anywhere in rust/Cargo.lock | None. The lockfile contains font, text, small utility, Windows/JNI binding and proc-macro crates only | rust/Cargo.lock |
| Crypto code written in-tree | None found (the string SHA256 appears only as sample display text in UI examples and tests, and in comments naming file hashes). The only integrity code is a CRC-32 used to detect torn writes in aster-appkit persistence, an error-detection checksum, not an information security function | rust/crates/aster-appkit/src/codec.rs, src/app/persist.rs |
| Network transport encryption | None. The optional net-sync transport is a plain length-framed TCP stream; applications supply their own TLS or VPN | rust/crates/aster-appkit/src/sync/tcp.rs |
| Calls to operating-system crypto APIs | None found in the guarded crates | tools/trust/no-io-check.sh |
| Release signing | Release artifacts are signed by us at build time with a standard signature tool (Releases: signing, provenance and verification). Signing is not a function the software provides to users | tools/trust/sign.sh |
To re-run the check at any version: run tools/trust/no-io-check.sh, then grep -iE "sha|aes|ring|rustls|openssl|crypt" rust/Cargo.lock and review cargo tree. The SBOM (Supply chain: SBOM, licences, advisories, vetting, reproducibility) lists every component.
Reasoning
- No encryption functionality. Category 5 Part 2 (ECCNs 5D002 and 5D992) covers information security items. Aster has none (see the table above), so those entries do not apply (15 CFR Part 774 Supplement No. 1; 742.15).
- Fallback (to be confirmed). If a particular compiled build were considered subject to the EAR, our reading is that it is EAR99 (not specifically listed on the Commerce Control List), needing no license for most destinations, end users and uses.
Things this does not remove:
- US sanctions (OFAC) and the restricted party lists apply regardless of the EAR status of the code. Ask counsel how this applies to hosting and downloads.
- End-use restrictions that apply to anyone with knowledge of a prohibited use.
- Other jurisdictions: the EU dual-use regulation (Regulation (EU) 2021/821) and others have their own rules.
Triggers to re-assess
- adding any encryption, hashing for security, signing, key handling or TLS, in the project or via a dependency (encryption source then needs the 740.13(e) notification, and classification under 5D002);
- adding a network protocol that carries authenticated or confidential data;
- moving the publisher or development to another jurisdiction.
Sources
- Bureau of Industry and Security, Export Administration Regulations: https://www.bis.gov/regulations/ear and eCFR Title 15 Parts 730-774 (https://www.ecfr.gov/current/title-15/subtitle-B/chapter-VII/subchapter-C).
- BIS encryption guidance: https://www.bis.gov/learn-support/encryption-and-export-administration-regulations-ear
- 15 CFR 734.3 (items subject to the EAR), 734.7 (published), 740.13(e) (publicly available encryption source code), 742.15 (encryption items), Part 774 Supplement No. 1 (Commerce Control List).
- OFAC sanctions programs: https://ofac.treasury.gov/