Add MseeP.ai badge

[mseep-ai]

Hi there,

This pull request shares a security update on codex-usage-tracker.

We also have an entry for codex-usage-tracker in our directory, MseeP.ai, where we provide regular security and trust updates on your app.

We invite you to add our badge for your MCP server to your README to help your users learn from a third party that provides ongoing validation of codex-usage-tracker.

You can easily take control over your listing for free: visit it at https://mseep.ai/app/douglasmonsky-codex-usage-tracker.

Thanks,

The MseeP Team
MCP servers you can trust

---

Here are our latest evaluation results of codex-usage-tracker

Security Scan Results

Security Score: 51/100

Risk Level: high

Scan Date: 2026-07-21

Score starts at 100, deducts points for security issues, and adds points for security best practices

Detected Vulnerabilities

Medium Severity

• brace-expansion

  • [{'source': 1123897, 'name': 'brace-expansion', 'dependency': 'brace-expansion', 'title': 'brace-expansion: DoS via exponential-time expansion of consecutive non-expanding {} groups', 'url': 'https://github.com/advisories/GHSA-3jxr-9vmj-r5cp', 'severity': 'high', 'cwe': ['CWE-400', 'CWE-407'], 'cvss': {'score': 5.3, 'vectorString': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}, 'range': '<1.1.16'}]
  • Fixed in version: unknown

• js-yaml

  • [{'source': 1123913, 'name': 'js-yaml', 'dependency': 'js-yaml', 'title': 'js-yaml: Quadratic-complexity (O(n^2)) DoS via !!omap tag in YAML11_SCHEMA', 'url': 'https://github.com/advisories/GHSA-724g-mxrg-4qvm', 'severity': 'moderate', 'cwe': ['CWE-407', 'CWE-770'], 'cvss': {'score': 5.3, 'vectorString': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}, 'range': '>=5.0.0 <=5.2.0'}]
  • Fixed in version: unknown

• markdownlint-cli2

  • ['js-yaml']
  • Fixed in version: unknown

Security Findings

Medium Severity Issues

• semgrep: Avoiding SQL string concatenation: untrusted input concatenated with raw SQL query can result in SQL Injection. In order to execute raw query safely, prepared statement should be used. SQLAlchemy provides TextualSQL to easily used prepared statement with named parameters. For complex SQL composition, use SQL Expression Language or Schema Definition Language. In most cases, SQLAlchemy ORM will be a better option.

  • Location: scripts/benchmark_refresh_ingestion.py
  • Line: 341

• semgrep: Avoiding SQL string concatenation: untrusted input concatenated with raw SQL query can result in SQL Injection. In order to execute raw query safely, prepared statement should be used. SQLAlchemy provides TextualSQL to easily used prepared statement with named parameters. For complex SQL composition, use SQL Expression Language or Schema Definition Language. In most cases, SQLAlchemy ORM will be a better option.

  • Location: scripts/benchmark_refresh_ingestion.py
  • Line: 349

• ... and 94 more medium severity issues

Low Severity Issues

• semgrep: Use of base64 decoding detected. This might indicate obfuscated code.

This security assessment was conducted by MseeP.ai, an independent security validation service for MCP servers. Visit our website to learn more about our security reviews.