diff --git a/README.md b/README.md
index 43557ba1cad..5d303c242bf 100644
--- a/README.md
+++ b/README.md
@@ -2,8 +2,6 @@
System and Service Manager
-
-
[](https://the-real-systemd.semaphoreci.com/projects/systemd)
[](https://scan.coverity.com/projects/350)
[](https://oss-fuzz-build-logs.storage.googleapis.com/index.html#systemd)
diff --git a/docs/ARCHITECTURE.md b/docs/ARCHITECTURE.md
index aaa3d862676..0a78f0502f0 100644
--- a/docs/ARCHITECTURE.md
+++ b/docs/ARCHITECTURE.md
@@ -198,6 +198,6 @@ can be found under various directories such as `factory/`, `modprobe.d/`, `netwo
## Utilities for Developers
-`tools/`, `coccinelle/`, `.github/`, `.semaphore/`, `.lgtm/`, `.mkosi/` host various
+`tools/`, `coccinelle/`, `.github/`, `.semaphore/`, `.mkosi/` host various
utilities and scripts that are used by maintainers and developers. They are not
shipped or installed.
diff --git a/docs/CODE_QUALITY.md b/docs/CODE_QUALITY.md
index 7d54a0f2e28..86577a48b57 100644
--- a/docs/CODE_QUALITY.md
+++ b/docs/CODE_QUALITY.md
@@ -69,9 +69,9 @@ available functionality:
13. When building systemd from a git checkout the build scripts will
automatically enable a git commit hook that ensures whitespace cleanliness.
-14. [LGTM](https://lgtm.com/) analyzes every commit pushed to `main`. The list
- of active alerts can be found
- [here](https://lgtm.com/projects/g/systemd/systemd/alerts/?mode=list).
+14. [CodeQL](https://codeql.github.com/) analyzes each PR and every commit
+ pushed to `main`. The list of active alerts can be found
+ [here](https://github.com/systemd/systemd/security/code-scanning).
15. Each PR is automatically tested with [Address Sanitizer](https://clang.llvm.org/docs/AddressSanitizer.html)
and [Undefined Behavior Sanitizer](https://clang.llvm.org/docs/UndefinedBehaviorSanitizer.html).
diff --git a/test/README.testsuite b/test/README.testsuite
index 7e3d6c06237..ac7cd361e75 100644
--- a/test/README.testsuite
+++ b/test/README.testsuite
@@ -211,10 +211,10 @@ where --test-name= is the name of the test you want to run/debug. The
--shell-fail option will pause the execution in case the test fails and shows
you the information how to connect to the testbed for further debugging.
-Manually running LGTM/CodeQL analysis
+Manually running CodeQL analysis
=====================================
-This is mostly useful for debugging various CodeQL/LGTM quirks.
+This is mostly useful for debugging various CodeQL quirks.
Download the CodeQL Bundle from https://github.com/github/codeql-action/releases
and unpack it somewhere. From now the 'tutorial' assumes you have the `codeql`
@@ -238,9 +238,9 @@ This can occur if the specified build commands failed to compile or process any
- For other languages, the --command must specify a "clean" build which compiles
all the source code files without reusing existing build artefacts.
-If you want to run all queries systemd uses in LGTM/CodeQL, run:
+If you want to run all queries systemd uses in CodeQL, run:
-$ codeql database analyze codeqldb/ --format csv --output results.csv .github/codeql-custom.qls .lgtm/cpp-queries/*.ql -vvv
+$ codeql database analyze codeqldb/ --format csv --output results.csv .github/codeql-custom.qls .github/codeql-queries/*.ql -vvv
Note: this will take a while.