diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index e6e82887..b27c3586 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -27,9 +27,6 @@ jobs:
     - name: Run bandit test
       run: tox -e bandit
 
-    - name: Run safety dependency scan
-      run: tox -e safety
-
     - name: Run auto-tests
       run: tox -e cov-ci
 
diff --git a/.safety-policy.yml b/.safety-policy.yml
deleted file mode 100644
index 71098c32..00000000
--- a/.safety-policy.yml
+++ /dev/null
@@ -1,15 +0,0 @@
-security:
-  ignore-cvss-severity-below: 4
-  ignore-vulnerabilities:
-    70612:
-      # CVE-2019-8341, jinja2:
-      #
-      # In summary, the CVE says that it is unsafe to use untrusted
-      # user input as Jinja template sources as arbitrary code execution
-      # is possible. This should be obvious, so unsurprisingly Jinja
-      # maintainers and various third-parties reject/dispute the CVE,
-      # including Red Hat in https://bugzilla.redhat.com/show_bug.cgi?id=1677653
-      #
-      reason: >-
-        Not exploitable: user input is not used in any Jinja template sources
-  continue-on-vulnerability-error: False
diff --git a/test-requirements.in b/test-requirements.in
index c9b82d93..b1e0edf1 100644
--- a/test-requirements.in
+++ b/test-requirements.in
@@ -7,7 +7,4 @@ pytest-cov
 mypy
 importlib-metadata
 bandit
-safety
 freezegun
-# marshmallow (dependency of safety) version 4.0 introduces breaking changes
-marshmallow<4
diff --git a/tox.ini b/tox.ini
index 18bfbcc6..31813796 100644
--- a/tox.ini
+++ b/tox.ini
@@ -29,11 +29,6 @@ usedevelop=true
 commands=
 	bandit -r -ll -c bandit.yaml .
 
-[testenv:safety]
-usedevelop=true
-commands=
-	safety check --output json {posargs}
-
 [testenv:docs]
 use_develop=true
 deps=