diff --git a/.github/workflows/contributors_report.yaml b/.github/workflows/contributors_report.yaml
index 3547c66..f863cfb 100644
--- a/.github/workflows/contributors_report.yaml
+++ b/.github/workflows/contributors_report.yaml
@@ -30,7 +30,7 @@ jobs:
           echo "END_DATE=$end_date" >> "$GITHUB_ENV"
 
       - name: Run contributor action
-        uses: github/contributors@6949781e2a2575cba21a80325c9dd6014f5c898b
+        uses: github/contributors@4d90d92531d4c5775be5a70c119ca7c0be165964
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           START_DATE: ${{ env.START_DATE }}
diff --git a/.github/workflows/scorecard.yml b/.github/workflows/scorecard.yml
index 1ef43d7..3d1199c 100644
--- a/.github/workflows/scorecard.yml
+++ b/.github/workflows/scorecard.yml
@@ -42,6 +42,6 @@ jobs:
           path: results.sarif
           retention-days: 5
       - name: "Upload to code-scanning"
-        uses: github/codeql-action/upload-sarif@ce28f5bb42b7a9f2c824e633a3f6ee835bab6858 # v3.29.0
+        uses: github/codeql-action/upload-sarif@4e828ff8d448a8a6e532957b1811f387a63867e8 # v3.29.4
         with:
           sarif_file: results.sarif
diff --git a/.github/workflows/super-linter.yaml b/.github/workflows/super-linter.yaml
index cf68556..7105f0a 100644
--- a/.github/workflows/super-linter.yaml
+++ b/.github/workflows/super-linter.yaml
@@ -26,7 +26,7 @@ jobs:
           python -m pip install --upgrade pip
           pip install -r requirements.txt -r requirements-test.txt
       - name: Lint Code Base
-        uses: super-linter/super-linter@12150456a73e248bdc94d0794898f94e23127c88
+        uses: super-linter/super-linter@5119dcd8011e92182ce8219d9e9efc82f16fddb6
         env:
           DEFAULT_BRANCH: main
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
diff --git a/Dockerfile b/Dockerfile
index 36b5a4a..a079ff9 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,6 +1,6 @@
 #checkov:skip=CKV_DOCKER_2
 #checkov:skip=CKV_DOCKER_3
-FROM python:3.13-slim@sha256:f2fdaec50160418e0c2867ba3e254755edd067171725886d5d303fd7057bbf81
+FROM python:3.13-slim@sha256:4c2cf9917bd1cbacc5e9b07320025bdb7cdf2df7b0ceaccb55e9dd7e30987419
 LABEL com.github.actions.name="contributors" \
     com.github.actions.description="GitHub Action that given an organization or repository, produces information about the contributors over the specified time period." \
     com.github.actions.icon="users" \
diff --git a/README.md b/README.md
index 52e66dd..c60d65b 100644
--- a/README.md
+++ b/README.md
@@ -39,7 +39,6 @@ Find out more in the [GitHub API documentation](https://docs.github.com/en/rest/
 1. Select a best fit workflow file from the [examples below](#example-workflows).
 1. Copy that example into your repository (from step 1) and into the proper directory for GitHub Actions: `.github/workflows/` directory with the file extension `.yml` (ie. `.github/workflows/contributors.yml`)
 1. Edit the values below from the sample workflow with your information:
-
    - `ORGANIZATION`
    - `REPOSITORY`
    - `START_DATE`
@@ -56,7 +55,7 @@ Find out more in the [GitHub API documentation](https://docs.github.com/en/rest/
    - Then take the value of the API token you just created, and [create a repository secret](https://docs.github.com/en/actions/security-guides/encrypted-secrets) where the name of the secret is `GH_TOKEN` and the value of the secret the API token.
    - Then finally update the workflow file to use that repository secret by changing `GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}` to `GH_TOKEN: ${{ secrets.GH_TOKEN }}`. The name of the secret can really be anything. It just needs to match between when you create the secret name and when you refer to it in the workflow file.
 1. If you want the resulting issue with the output to appear in a different repository other than the one the workflow file runs in, update the line `token: ${{ secrets.GITHUB_TOKEN }}` with your own GitHub API token stored as a repository secret.
-   - This process is the same as described in the step above. More info on creating secrets can be found [here](https://docs.github.com/en/actions/security-guides/encrypted-secrets).
+   - This process is the same as described in the step above. More info on [creating secrets](https://docs.github.com/en/actions/security-guides/encrypted-secrets) can be found.
 1. Commit the workflow file to the default branch (often `master` or `main`)
 1. Wait for the action to trigger based on the `schedule` entry or manually trigger the workflow as shown in the [documentation](https://docs.github.com/en/actions/using-workflows/manually-running-a-workflow).
 
diff --git a/requirements-test.txt b/requirements-test.txt
index f2231f6..bea8fbc 100644
--- a/requirements-test.txt
+++ b/requirements-test.txt
@@ -1,8 +1,8 @@
 black==25.1.0
-flake8==7.2.0
-mypy==1.16.0
+flake8==7.3.0
+mypy==1.17.0
 mypy-extensions==1.1.0
 pylint==3.3.7
-pytest==8.4.0
+pytest==8.4.1
 pytest-cov==6.2.1
 types-requests==2.32.4.20250611
diff --git a/requirements.txt b/requirements.txt
index f4818a2..737a316 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,3 +1,3 @@
 github3.py==4.0.1
-python-dotenv==1.1.0
+python-dotenv==1.1.1
 requests==2.32.4