Forge / Legal
Open Source Licenses for Forge
Effective date: July 17, 2026
Forge is built on a foundation of open-source software. We are grateful to the open-source community for these contributions. This document lists the major open-source dependencies used in Forge and their respective licenses.
Major Dependencies
Core Framework
- Expo SDK 56 - MIT License
- React Native - MIT License
- TypeScript - Apache License 2.0
- Expo Router - MIT License
State Management and Storage
- Zustand - MIT License
- Expo SecureStore - MIT License
- Expo FileSystem - MIT License
- AsyncStorage - MIT License
- TanStack Query (React Query) - MIT License
Forms and Validation
- React Hook Form - MIT License
- Zod - MIT License
Testing
- Vitest - MIT License
Native Android Module
- SSHJ (sshj) - MIT License
- Kotlin - Apache License 2.0
Editor and Terminal
- Monaco Editor - MIT License
- xterm.js - MIT License
UI Components
- React Native Vector Icons - MIT License
- Expo Vector Icons - MIT License
- Expo Splash Screen - MIT License
- Expo Font - MIT License
Build and Development
- Expo Continuous Native Generation - MIT License
- Expo CLI - MIT License
License Texts
MIT License
MIT License
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.Apache License 2.0
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.Third-Party Notices
SSHJ (sshj)
- Copyright (c) 2012-2024 SSHJ Contributors
- License: MIT
- Website: https://github.com/hierynomus/sshj
Monaco Editor
- Copyright (c) Microsoft Corporation
- License: MIT
- Website: https://github.com/microsoft/monaco-editor
xterm.js
- Copyright (c) 2014-2024 xterm.js contributors
- License: MIT
- Website: https://github.com/xtermjs/xterm.js
React Native
- Copyright (c) Facebook, Inc. and its affiliates.
- License: MIT
- Website: https://reactnative.dev/
Expo
- Copyright (c) 2024 Expo
- License: MIT
- Website: https://expo.dev/
Attribution Requirements
All MIT-licensed components require preservation of copyright notices in documentation or about dialogs. Apache License 2.0 components require preservation of copyright notices, patent notices, trademark notices, and attribution notices in documentation.
Modifications
Forge may include modified versions of some open-source components:
- ForgeSsh Android module: Custom native module built on SSHJ
- WebView assets: Bundled Monaco and xterm configurations
- Custom plugins: Forge-specific Expo config plugins
Modified components retain their original licenses. Modifications are clearly marked in source code where applicable.
License Compliance
Forge's build process includes:
- Dependency license auditing
- Lockfile maintenance for reproducible builds
- Attribution file generation for distribution
Full License Texts
Complete license texts for all dependencies are available in the following locations:
node_modules/*/LICENSE- Individual package licensespackage.json- Dependency list with versionspackage-lock.json- Exact dependency tree
Notices and Attribution
This document serves as attribution for all open-source components used in Forge. If you distribute Forge or derivative works, you must include appropriate copyright notices and license texts for all included open-source components.
Changes to Dependencies
Dependencies may be updated between releases. Each release will include an updated dependency inventory. Material changes to dependency licensing will be documented in release notes.
Note: This document lists major dependencies as of the Forge v1.0.0-rc.1 release. For a complete and authoritative list, inspect the package.json and package-lock.json files in the Forge repository, or generate a Software Bill of Materials (SBOM) from the signed production artifact.
