Plugins and Third-Party Tools#
Understand what each DDS integration installs or opens, its license, and its update and security limits.
Choose an Integration#
DDS handles each integration separately. Check the source repository and supported host below, then check the status in your installed DDS release.
Integration |
Supported use |
Adapter source and tool terms |
|---|---|---|
Verilator |
Source-preview catalog entry. The adapter plans lint arguments; DDS installation and execution are unavailable. |
|
Visual Studio Code |
Registers a DDS integration and opens a separately installed official VS Code application. Windows WSL use also requires the separately installed Microsoft WSL extension. Browser Cloud cannot launch it. |
|
KLayout |
On Windows x64 and Ubuntu 24.04 x64 (including WSL), the native integration downloads pinned official packages, verifies their hashes and opens a selected saved layout in a separate process. Required libraries and a GUI display must be available. Browser Cloud cannot launch it. |
Installing or removing the VS Code integration does not install or uninstall the VS Code application. KLayout has a separate managed tool package. DDS built-in analysis and layout views retain their own capabilities.
Licenses Apply to the Actual Material#
A public SDK or adapter license applies to the files it identifies. It does not replace the license of an external tool, copied library, bundled runtime, extension or trademark. A separate GitHub repository is useful for review and contributions, but is not by itself a legal requirement or proof of redistribution compliance.
Verilator offers LGPL-3.0 or Artistic-2.0 licensing for its internals. Record the applicable option and review runtime/header inclusion and any modified or distributed tool package. Its source-preview adapter has a separate Apache-2.0 license. See the official copyright explanation.
The pinned KLayout 0.30.12 source states GPL-3.0-or-later. If providing its binaries, evaluate the exact corresponding source, license notices, patches, build inputs and bundled dependency terms. Merely linking the adapter source is insufficient. See the versioned copyright.
VS Code source uses MIT, while Microsoft product binaries and Microsoft extensions have their own terms. The Visual Studio Marketplace terms separately restrict use of its offerings outside the designated Microsoft products. Opening official VS Code is different from importing its extensions into DDS.
Using a separate process helps define an integration boundary, but does not automatically settle licensing. Review the actual code, exchanged data and distribution method. Third-party names identify compatible tools and do not imply endorsement.
Downloads, Files and Permissions#
The native KLayout integration downloads pinned packages from the official upstream origin and verifies their hashes. Its source repository contains the adapter; the tool package has its own version and license notices.
An external editor or viewer can read the workspace or file you open with it. Review that application and its extensions, privacy settings and own update mechanism before sharing sensitive designs. A catalog listing does not create a sandbox around a native application or guarantee the absence of malware.
Hashes check expected bytes and signatures can identify a publisher. Neither is a guarantee of safety. Public source review, dependency analysis, scanning and restricted execution address different risks. Read the software terms and privacy notice for the current service boundaries.
Version Changes and Reporting#
VS Code updates through its own supported distribution. DDS compatibility depends on the installed version and required extensions. KLayout uses the pinned version supported by the DDS integration.
Check the adapter repository for source changes and known issues. General community plugin installation and an automatic plugin updater are not available in the current DDS release.
For adapter source issues, use the relevant GitHub repository above. For installation or native integration problems, contact Altifigence Support with your DDS version, operating system, integration version and a minimal reproduction. Remove credentials and private design files from public reports.
To develop and test your own diagnostics plugin, follow DDS Plugin SDK.