Third-party software
Licenses and third parties
Legible notices of key components present in current inventory.
The full inventory of the Android project contains hundreds of direct and transitive dependencies. This page highlights components relevant to the runtime; Development tools are not presented as if they were embedded resources.
Relevant engines and libraries
| Component | Use | License observed |
|---|---|---|
| Expo / React Native / React | Application interface and runtime | MIT |
| Mozilla PDF.js / pdfjs-dist | Local view of PDF | Apache-2.0 |
| pdf-lib | Local operations with PDF | MIT |
| SheetJS Community Edition | Spreadsheets in the offline bundle | Apache-2.0 |
| JSZip and fflate | ZIP/DEFLATE files | MIT |
| junrar / UnRAR | Reading and extraction RAR | UnRAR License |
| Zip4j | Local ZIP processing on Vault | Apache-2.0 |
| AndroidX PDF | Native PDF view | Apache-2.0 |
| @signpdf and node-forge | Local signature P12/PFX | MIT / BSD-3-Clause |
| Google Play Services / ML Kit Document Scanner | Scan experience | Google Terms |
Google Drive
Google Drive may appear as an optional provider in the Android selector. This does not imply partnership, endorsement, OAuth within EllenDoc or shared backend.
Gap before release
The license, provenance, and SBOM of the vendorized Secure Document Vault still need to be confirmed before distributing a AAB that contains this component. Full notices must accompany the published artifact.
Brands
Microsoft Office, Android, Google Play, Google Drive and other brands belong to their respective owners. Format compatibility does not mean affiliation.