From e0fc20908f58a712b6ddda604fcc358ac7e1bd66 Mon Sep 17 00:00:00 2001 From: Alexsander Hamir Date: Mon, 5 Jan 2026 16:39:04 -0800 Subject: [PATCH] Fix bad practices: replace real-looking API keys in docstrings with example patterns - Replace sk-02Wr4IAlN3NvPXvL5JVvDA with sk-example-... in key_management_endpoints.py - Replace sk-Fn8Ej39NkBQmUagFEoUWPQ with sk-example-... in spend_management_endpoints.py - Add SHA256 hashes to ignore mock data in cache_dashboard.tsx comments --- .gitguardian.yaml | 16 ++++++++++++++++ .../key_management_endpoints.py | 2 +- .../spend_tracking/spend_management_endpoints.py | 2 +- 3 files changed, 18 insertions(+), 2 deletions(-) diff --git a/.gitguardian.yaml b/.gitguardian.yaml index f6976da6297..2b4e41ef393 100644 --- a/.gitguardian.yaml +++ b/.gitguardian.yaml @@ -109,4 +109,20 @@ secret: - name: Test JWT token pattern match: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9 + + # Mock data in cache_dashboard.tsx comments + - name: Mock API key in cache_dashboard comments 147dba2181f + match: 8c892b51c97ff98b14f17864b89a13c0f4e7ea0c8de739b6acfa1cf9cab4e01d + + - name: Mock API key in cache_dashboard comments 8c23f021d05 + match: 05681b08b5b2a6d5b3efdcfd8243b92e69715a267f24d105e946656de829de23 + + - name: Mock API key in cache_dashboard comments 0ad4b3c03dc + match: 42386bbdf8a420ebc43057dcf62c3ab6a78ea9e7a816d465a44d582ad9c245c4 + + - name: Mock API key in cache_dashboard comments 034224b36e9 + match: d700e35089af83d66a6d8a31b09d68e67c883d87b49d2186a9fcbac492ccd8fe + + - name: Mock API key in cache_dashboard comments 4f9c71cce0a + match: 119117ac366f569fe34c94ad805b88a5bf02b0d45ef0f2142518fcc7e75364e8 diff --git a/litellm/proxy/management_endpoints/key_management_endpoints.py b/litellm/proxy/management_endpoints/key_management_endpoints.py index da44bda791d..4da4d54546c 100644 --- a/litellm/proxy/management_endpoints/key_management_endpoints.py +++ b/litellm/proxy/management_endpoints/key_management_endpoints.py @@ -1917,7 +1917,7 @@ async def info_key_fn( Example Curl - if no key is passed, it will use the Key Passed in Authorization Header ``` curl -X GET "http://0.0.0.0:4000/key/info" \ --H "Authorization: Bearer sk-02Wr4IAlN3NvPXvL5JVvDA" +-H "Authorization: Bearer sk-example-1234567890abcdef" ``` """ from litellm.proxy.proxy_server import prisma_client diff --git a/litellm/proxy/spend_tracking/spend_management_endpoints.py b/litellm/proxy/spend_tracking/spend_management_endpoints.py index 5be9d9bab3c..4eca480375e 100644 --- a/litellm/proxy/spend_tracking/spend_management_endpoints.py +++ b/litellm/proxy/spend_tracking/spend_management_endpoints.py @@ -1938,7 +1938,7 @@ async def view_spend_logs( # noqa: PLR0915 Example Request for specific api_key ``` - curl -X GET "http://0.0.0.0:8000/spend/logs?api_key=sk-Fn8Ej39NkBQmUagFEoUWPQ" \ + curl -X GET "http://0.0.0.0:8000/spend/logs?api_key=sk-example-1234567890abcdef" \ -H "Authorization: Bearer sk-1234" ```