Avoid using docker_image pre-commit hook (portability)

Related: pre-commit/pre-commit#2920

.github/SECURITY.md

@@ -6,5 +6,6 @@ The only supported version is the latest release.
 
 ## Reporting a Vulnerability
 
-Send an email to [email protected] if you found any security
-vulnerability that is better to not have a public bug raise right away.
+Use [github reporting](https://github.com/pycontribs/mk/security) if you
+found any security vulnerability that is better to not have a public bug raised
+right away.

.gitignore

@@ -12,6 +12,6 @@ report.html
 site
 src/mk.egg-info
 src/mk/_version.py
-.coverage
+.coverage*
 coverage.xml
 CMakeFiles

.pre-commit-config.yaml

@@ -26,11 +26,10 @@ repos:
         # entry: codespell --relative
         args: [--relative, --no-progress, --no-summary]
         name: Spell check with cspell
-
-  - repo: https://github.com/markdownlint/markdownlint.git
-    rev: v0.12.0
+  - repo: https://github.com/igorshubovych/markdownlint-cli
+    rev: v0.41.0
     hooks:
-      - id: markdownlint_docker
+      - id: markdownlint
   - repo: https://github.com/psf/black
     rev: 24.4.2
     hooks:

docs/README.md

@@ -20,9 +20,10 @@ configuration file is needed as the tool will look for common tools used by the
 repository and expose their commands.
 
 `mk` is inspired by tools such [make][make], [waf][waf], [taskfile][taskfile],
-[tox][tox], [npm][npm], [yarn][yarn] and [pre-commit][pre-commit], but **it does
-not aim to replace them**. Instead, it aims to provide a unified interface for
-calling them that is friendly even for those that never used these tools.
+[tox][tox], [nox][nox], [npm][npm], [yarn][yarn] and [pre-commit][pre-commit],
+but **it does not aim to replace them**. Instead, it aims to provide a unified
+interface for calling them that is friendly even for those that never used
+these tools.
 
 ## Installation
 
@@ -101,7 +102,7 @@ status or that the testing did not leave untracked files.
   unknown. (#20)
 - Configuration file where additional actions can be added. (#21)
 - Dependencies between commands. While some tools support dependencies, many do
-  not. You should be able to declare that a specific command would run only
+  not. You should be able to declare that a specific command will run only
   after another one already passed. (#22)
 - Ability to generate CI/CD pipelines so the user would spend less time writing
   non-portable configurations. (#23)