# Subprojects and embedded code

Weblate would not be possible without other projects it depends on. This
document describes how other code is used in Weblate.

## Vendored frontend code

Weblate vendors several JavaScript libraries. The process is described in
[Weblate sučelje](https://docs.weblate.org/hr/latest/contributing/frontend.md) and licensing of each vendored library is documented via REUSE
as described in [Weblate license](https://docs.weblate.org/hr/latest/contributing/license.md). The up-to-date list of dependencies can be
reviewed in [Software Bill of Material](https://docs.weblate.org/hr/latest/security/release-artifacts.md#sbom).

## SPDX license data

The SPDX license data is included as a Git submodule in the source code and
`weblate/utils/licensedata.py` is generated using
`scripts/generate-license-data.py`. The submodule tracks tagged SPDX
releases. Renovate updates the release recorded in `.gitmodules`, and
the license update workflow updates the submodule and generated license data.

## Test data

The test repositories in `weblate/trans/tests/data/test-base-repo.*.tar`
are generated from [https://github.com/WeblateOrg/test](https://github.com/WeblateOrg/test), see [Testing repository](https://docs.weblate.org/hr/latest/contributing/tests.md#test-data).

## Python dependencies

Weblate would not be possible without many third-party dependencies. The
current dependencies are in `pyproject.toml` and can be reviewed in
[Software Bill of Material](https://docs.weblate.org/hr/latest/security/release-artifacts.md#sbom). The most important dependencies are also described in
[Python dependencies](https://docs.weblate.org/hr/latest/admin/install.md#python-deps).