10. Embedded Software Dependencies¶
Like most software, L7|ESP relies on a number of open-source component to function. At L7 Informatics, we track the version, license and security issues of each of these. For visibility into the underlying technology stack, each dependency is listed below.
10.1. Backend¶
L7|ESP runs as several independent processes that communicate with each other via TCP/IP-based protocols. The process tree spawned by L7|ESP is detailed in figure 1:

Figure 1. L7|ESP Process Tree¶
The L7|ESP backend is written primarily in Python, as such we rely on the following packages which are made available through PyPI:
Warning
Could not query the Snyk API because SNYK_API_TOKEN
environment variable was not set.
The PDF service uses the popular Node library Puppeteer to control Chrome:
Warning
Could not query the Snyk API because SNYK_API_TOKEN
environment variable was not set.
10.2. Frontend¶
The L7|ESP web interface is written in VueJS and runs in your browser. The following JavaScript libraries are embedded in each build of the frontend:
Warning
Could not query the Snyk API because SNYK_API_TOKEN
environment variable was not set.
10.3. System Libraries¶
L7|ESP ships as a container image built on top of the stable and dependable Debian Linux distribution. The latest major release is currently Debian 11 (Bullseye).
This container image includes major components for running the platform, such as database software (PostgreSQL, Redis) and programming language interpreters (Python, NodeJS).
Warning
Could not query the Snyk API because SNYK_API_TOKEN
environment variable was not set.