About (administration)
The About tab says which Tesria this is, and lists everything it is built from, with each license. Its main job is for the day a security problem is announced in something widely used: it tells you, in one click, whether your Tesria includes it.
To open it, choose Admin, About (Admin is in the top bar; in a narrower window it is under More, and on a phone in the ☰ menu). Anyone who can see the Dashboard can open it; checking for vulnerabilities needs the right to see security alerts.
Which Tesria this is
The version at the top is the one to quote when you ask for help, and the one to compare with the Release notes. After an upgrade it also says what you upgraded from, and when. Links go to tesria.com, the source code, and the licenses of everything Tesria includes.
Checking for known vulnerabilities
When a vulnerability is announced in a package many programs use, the first question is: am I affected?
Step 1: Choose Check for known vulnerabilities
Tesria asks OSV.dev, the open database of vulnerabilities behind GitHub’s and npm’s security advisories, about every package it includes. The answer takes a few seconds.
Step 2: Read the result
No known vulnerabilities, with the date and who checked: nothing Tesria includes has a published vulnerability as of that moment.
A list of packages: each with the vulnerabilities found (their ids, the CVE number when there is one, how severe, and a sentence on what it is), linked to the full advisory. The advisory says which version of the package fixes it; the fix reaches you when a Tesria release updates the package, so upgrade when one does. Until then, the advisory usually says what the problem needs to be exploited, which tells you how worried to be.
What the check sends. The names and versions of the packages, and, like any request, your server’s address. Nothing about your wiki, its pages or its people. It happens only when someone chooses the button, never on its own. A server that cannot reach the internet says so, and still shows the list.
The last result stays on the page, with when it was made, until someone checks again.
The check covers the packages. The container images have their own section, next.
Container images
The operating systems and runtimes Tesria runs on: one image for the app, one for the database and backups, and so on, each with a line saying what it is for. Images marked as building the app, as optional, or as for testing only are not running on an ordinary Tesria. OSV.dev does not cover images, so each has a command to check it with Docker’s own tools on the server; choose Copy beside it and run it in a terminal there. docker scout cves comes with Docker Desktop, and trivy image works the same way.
Images get security updates of their own between Tesria releases. To pick them up, on the server run docker compose pull and docker compose build --pull, then docker compose up -d.
Packages
Every other package this version ships, for each part of Tesria: the server, the web app, the collaboration service and the PDF service. Filter by name or license, or choose one part. Third-party licenses, at the top, has the full license text of each.
Supporting Tesria
Tesria is free. If it is useful to you and you would like to say thanks, Ways to support Tesria opens tesria.com/support, which lists how: GitHub Sponsors or Ko-fi. It is never required, and nothing in Tesria depends on it.
Applies to | Tesria 0.6 and later |
|---|---|
Updated | September 24, 2026 |
Changes | New in 0.6. |