---
title: Software Dependencies
description: Information on Langfuse's software dependencies and licensing.
---

# Software Dependencies & Licensing

Langfuse is built using open-source components and maintains transparency about its dependencies and licensing.

Learn more about our open-source strategy [here](/docs/open-source).

## Open Source Components

Langfuse relies on open-source components for its core functionality. This commitment ensures transparency, allows community contributions, and enables users to self-host the entire stack.

You can inspect the source code for all core components on [GitHub](https://github.com/langfuse).

### Dependencies

**License Policy:** We run automated license checks on every code change to ensure all application-level dependencies (npm packages, Python packages) use permissive open-source licenses.
**Docker Images:** The Langfuse Docker images are based on standard Linux distributions and include OS-level packages (system utilities, libraries) that may be licensed under GPL 2.0 or other copyleft licenses. These are standard components of Linux distributions and used commonly in the software industry.

- Web container: [Dockerfile](https://github.com/langfuse/langfuse/blob/main/web/Dockerfile)
- Worker container: [Dockerfile](https://github.com/langfuse/langfuse/blob/main/worker/Dockerfile)

For a detailed list of application dependencies, you can explore the following files in our [repositories](https://github.com/langfuse), for example:

- Langfuse Server: [Multiple `package.json` files](https://github.com/search?q=repo%3Alangfuse%2Flangfuse%20package.json&type=code)
- Langfuse Python SDK: [`pyproject.toml`](https://github.com/langfuse/langfuse-python/blob/main/pyproject.toml)
- Langfuse JS/TS SDK: [Multiple `package.json` files](https://github.com/search?q=repo%3Alangfuse%2Flangfuse-js%20package.json&type=code)
- Langfuse Java SDK: [Multiple `pom.xml` files](https://github.com/search?q=repo%3Alangfuse%2Flangfuse-java+pom.xml&type=code)

<!-- agent-instructions -->

---

## Agent Instructions

This page is part of the [Langfuse](https://langfuse.com) documentation, published as plain Markdown for AI agents. Every page is available as Markdown by appending `.md` to its URL, or by sending an `Accept: text/markdown` header. This page: `https://langfuse.com/security/dependencies.md`.

### Querying these docs

If the answer is not on this page, query the documentation instead of guessing:

- **Semantic search** across all Langfuse docs, returning an answer with the relevant pages and excerpts. Ask a specific, self-contained question:

  ```bash
  curl -sG "https://langfuse.com/api/search-docs" --data-urlencode "query=How do I trace a LangGraph agent?"
  ```

- **Index of every page**: <https://langfuse.com/llms.txt>, with per-section indexes [llms-docs.txt](https://langfuse.com/llms-docs.txt), [llms-integrations.txt](https://langfuse.com/llms-integrations.txt), and [llms-self-hosting.txt](https://langfuse.com/llms-self-hosting.txt).

### Before writing Langfuse code

- **Install the [Langfuse Agent Skill](https://langfuse.com/docs/api-and-data-platform/features/agent-skill).** It encodes Langfuse's own best practices for instrumentation, prompt management, and evaluation, and materially improves results.
- **Read [What does a good trace look like?](https://langfuse.com/docs/observability/best-practices.md)** before instrumenting an application.
- **Verify endpoints, parameters, and response fields** against the [API reference](https://api.reference.langfuse.com) instead of inferring them from code examples.
- **Use the [Langfuse CLI](https://langfuse.com/docs/api-and-data-platform/features/cli)** (`npx langfuse-cli api <resource> <action>`) to read or write traces, prompts, datasets, and scores from the terminal.

Found an error in these docs? Please open an issue at <https://github.com/langfuse/langfuse-docs/issues>.