Trust / Open-source acknowledgements

Third-party licenses and notices

SiliconForge’s license covers its original product layer. Bundled libraries, bundled engineering tools and separately installed tools retain their own rights and obligations.

Source for your download

Choose the entry matching your application version, operating system and downloaded filename. If filenames are similar, compare the installer’s checksum. A source archive for another package is not a substitute.

For machine-readable release records, use the corresponding-source catalog (JSON). Archive links belong to the exact package records in that catalog; no unlisted version is implied to be covered. If your package is missing, contact Support with its version, platform and filename.

These archives are for examining or building the included third-party components. Their inventory identifies the source, build instructions, patches and license materials provided. You do not need to download a source archive to install SiliconForge, and it does not contain SiliconForge’s proprietary application code.

Keep the notices and source records for the exact package you use, including an older 0.1.0 package after a 0.1.1 update. Publication of a source archive does not itself certify a reproducible build or remove rights granted by the component’s license.

Public license and inventory files

These files are source-level reference inventories, not an attestation that a particular binary contains exactly this set of bytes or that legal review is complete. Use the notices, license files, SBOM and source materials accompanying your exact package for that release. Application artifacts and the website can have different revisions; do not substitute the current website inventory for an older installer’s records.

Major application components

Qt / PySide6 and shiboken6
Native application UI/runtime. The recorded license alternatives are LGPL-3.0-only, GPL-2.0-only or GPL-3.0-only. Read the full LGPL 3.0, GPL 2.0 and GPL 3.0 texts and the distribution-specific notices. The product license does not remove applicable third-party rights.
CPython and Python dependencies
The application includes its Python runtime and packages such as NumPy, PyQtGraph and the OpenAI client library. Their license expressions and versions are listed in the SBOM. Full upstream notices are retained with the installed runtime and package metadata; the OpenAI client library is not a bundled AI model or provider account.
Node.js and ELK.js
Pinned runtime and layout support. Read the Node.js license and bundled notices and Eclipse Public License 2.0 for ELK.
Graphviz DOT
Layout support with the Graphviz Eclipse Public License 2.0 text. This does not imply Graphviz validates the electrical or logical correctness of a design.
libavoid
The separate architecture routing library is recorded as LGPL-2.1-or-later. Read the LGPL 2.1 text; the package’s replaceable-library and corresponding-source materials are separate from the proprietary product layer.
Lucide icons
Selected offline SVG assets from Lucide 1.40.0. The complete notice preserves ISC terms and MIT terms for Feather-derived icons.
netlistsvg digital symbols
MIT-licensed digital SVG symbols rendered by the native UI, not an embedded netlistsvg JavaScript application. Read the copyright and license notice.

This overview is not exhaustive: consult the SBOM and package notices for the complete recorded dependency set.

Separate tools and catalog IP

HDL/CAD tools such as Verilator, Yosys and solvers run as separate subprocesses and keep their own licenses, whether bundled with the application or installed separately. Published application packages include engineering tools; the exact platform package inventory identifies them. The Engineering Tool Pack is not offered as a separate download. That does not mean its components are absent from an application package. Use the release-specific source records above for bundled components, not a historical standalone-pack inventory. Catalog IP acquired separately and an externally installed Codex CLI retain their own terms.

Product license · Engineering-tool setup · Release verification