Leaderboard github.com
CoplayDev/unity-mcp
Unity MCP acts as a bridge between AI assistants and your Unity Editor. Give your LLM tools to manage assets, control scenes, edit scripts, and automate tasks within Unity.
AI provenance
22%
explicit
- Confidence
- 95%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
70/100
adequate
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
52/100
weak
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
22% explicit
Explicit AI attribution on 22% of first-party code added; an estimated 22% including velocity signals.
How the score is built
- Explicitly attributed share22%
- Unattributed share in AI-pace bursts12%
- Estimated AI-generated share22%
- AI tool configuration files16
- Work sessions at AI pace18
- Releases at AI pace4
- Coding-style index (1.0+ means possible)0.30
Attributed AI tools
| Tool | Commits | Lines added | First seen | Last seen |
|---|---|---|---|---|
| Claude Code | 203 | 61,568 | 2025-07-29 | 2026-09-13 |
| GitHub Copilot coding agent | 5 | 8,725 | 2026-01-21 | 2026-03-03 |
| OpenAI Codex | 39 | 7,673 | 2026-01-04 | 2026-10-07 |
| Cursor agent | 1 | 16 | 2026-08-21 | 2026-08-21 |
Lines added per month all AI-attributed share
- 2025-0313,593 · 0% AI
- 2025-047,733 · 0% AI
- 2025-05678 · 0% AI
- 2025-072,410 · 13% AI
- 2025-0815,168 · 1% AI
- 2025-0937,594 · 13% AI
- 2025-1046,102 · 7% AI
- 2025-1121,621 · 14% AI
- 2025-129,524 · 2% AI
- 2026-0184,418 · 28% AI
- 2026-0220,959 · 70% AI
- 2026-0339,831 · 18% AI
- 2026-043,431 · 45% AI
- 2026-055,463 · 8% AI
- 2026-0612,747 · 67% AI
- 2026-075,976 · 52% AI
- 2026-086,687 · 1% AI
- 2026-097,696 · 24% AI
- 2026-106,923 · 52% AI
- 2026-1132 · 0% AI
Findings in AI-attributed lines vs the rest
From git blame: 33,199 lines trace to AI-attributed commits, 119,518 to others. Reported, not scored.
| Findings per 1,000 lines | AI-attributed | Other | Ratio |
|---|---|---|---|
| Code quality | 0.66 | 1.49 | 0.45× |
| Security | 0.18 | 0.20 | 0.90× |
Evidence by analyzer
Explicit AI attributionok29 items
- Claude Code: 203 attributed commits, 61,568 lines added
- OpenAI Codex: 39 attributed commits, 7,673 lines added
- GitHub Copilot coding agent: 5 attributed commits, 8,725 lines added
- Cursor agent: 1 attributed commits, 16 lines added
- OpenAI Codex: on merged branch (88f1e4db73)
- OpenAI Codex: on merged branch (ff7f6d3db6)
- OpenAI Codex: on merged branch (ff7f6d3db6)
- OpenAI Codex: on merged branch (ff7f6d3db6)
- OpenAI Codex: on merged branch (ff7f6d3db6)
- OpenAI Codex: on merged branch (ff7f6d3db6)
- OpenAI Codex: on merged branch (ff7f6d3db6)
- OpenAI Codex: on merged branch (ff7f6d3db6)
- OpenAI Codex: on merged branch (6abce3e0f5)
- OpenAI Codex: on merged branch (6abce3e0f5)
- OpenAI Codex: on merged branch (6abce3e0f5)
- OpenAI Codex: on merged branch (6abce3e0f5)
- OpenAI Codex: on merged branch (6abce3e0f5)
- OpenAI Codex: on merged branch (6abce3e0f5)
- OpenAI Codex: on merged branch (6abce3e0f5)
- OpenAI Codex: on merged branch (6abce3e0f5)
- OpenAI Codex: on merged branch (6abce3e0f5)
- OpenAI Codex: on merged branch (6abce3e0f5)
- OpenAI Codex: on merged branch (6abce3e0f5)
- OpenAI Codex: on merged branch (6abce3e0f5)
- Claude Code: author email [email protected]
- Cursor agent: trailer 'Co-authored-by: Cursor'
- OpenAI Codex: on merged branch (5595c7be99)
- OpenAI Codex: on merged branch (5595c7be99)
- Claude Code: trailer 'Co-Authored-By: Claude'
- attributed_commit_share
- 16.4%
- attributed_commits
- 246
- attributed_loc
- 75,994
- attributed_loc_share
- 21.8%
- commits
- 1,503
- effective_loc
- 348,586
- tools_detected
- 4
AI tool configurationok16 items
- .claude/mcp.json (claude-code configuration)
- .claude/prompts/nl-gameobject-suite.md (claude-code configuration)
- .claude/prompts/nl-unity-suite-nl.md (claude-code configuration)
- .claude/prompts/nl-unity-suite-t.md (claude-code configuration)
- .claude/settings.json (claude-code configuration)
- .claude/skills/blender-to-unity/SKILL.md (claude-code configuration)
- .claude/skills/blender-to-unity/manual-verify.md (claude-code configuration)
- .claude/skills/blender-to-unity/references/bridge-fidelity.md (claude-code configuration)
- .claude/skills/mcp-source/SKILL.md (claude-code configuration)
- .claude/skills/unity-mcp-skill/SKILL.md (claude-code configuration)
- .claude/skills/unity-mcp-skill/references/probuilder-guide.md (claude-code configuration)
- .claude/skills/unity-mcp-skill/references/resources-reference.md (claude-code configuration)
- .claude/skills/unity-mcp-skill/references/tools-reference.md (claude-code configuration)
- .claude/skills/unity-mcp-skill/references/workflows.md (claude-code configuration)
- CLAUDE.md (claude-code configuration)
- .github/workflows/claude-nl-suite.yml runs anthropics/claude-code-action
- artifacts
- 15
- earliest_adoption
- 2025-09-07
- tools_configured
- 1
- workflow_agents
- 1
Commit velocityok15 items
- 2,834 lines of first-party code in ~0.5h (5,668 lines/hour, 1 commit session)
- 1,045 lines of first-party code in ~0.7h (1,488 lines/hour, PR #490)
- 2,107 lines of first-party code in ~1.7h (1,206 lines/hour, 6 commit session)
- 4,724 lines of first-party code in ~4.0h (1,173 lines/hour, PR #354)
- 6,387 lines of first-party code in ~6.1h (1,050 lines/hour, 9 commit session)
- 4,252 lines of first-party code in ~4.1h (1,049 lines/hour, 2 commit session)
- 6,285 lines of first-party code in ~6.0h (1,043 lines/hour, PR #606)
- 5,375 lines of first-party code in ~5.3h (1,009 lines/hour, PR #870)
- 1,720 lines of first-party code in ~1.8h (944 lines/hour, 6 commit session)
- 3,353 lines of first-party code in ~4.0h (837 lines/hour, 3 commit session)
- 3,069 lines of first-party code in ~4.0h (767 lines/hour, 1 commit session)
- 2,995 lines of first-party code in ~4.0h (740 lines/hour, PR #369)
- 2,881 lines of first-party code in ~4.1h (709 lines/hour, PR #882)
- 1,879 lines of first-party code in ~2.7h (685 lines/hour, PR #519)
- 2,726 lines of first-party code in ~4.7h (586 lines/hour, PR #507)
- excluded_import_loc
- 110,279
- flagged_loc
- 55,374
- flagged_loc_share
- 23.2%
- flagged_units
- 18
- max_loc_per_hour
- 5,668
- measured_loc
- 238,307
- median_loc_per_hour
- 90.41
- pr_timed_units
- 208
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 0
- work_units
- 557
Release velocityok4 items
- v8.7.1 → v9.0.0: 12,232 lines in 3.1 days (3,946.3 lines/day)
- v9.0.8 → v9.1.0: 7,705 lines in 2.45 days (3,140.0 lines/day)
- v9.3.0 → v9.3.1: 12,706 lines in 0.45 days (28,406.5 lines/day)
- v9.5.2 → v9.5.3: 7,817 lines in 2.45 days (3,193.7 lines/day)
- flagged_releases
- 4
- max_loc_per_day
- 69,936
- releases
- 87
Coding styleok8 items
- step-by-step narration comment: // First, honor overrides and cross-platform resolution via the base implementation
- step-by-step narration comment: // First, try to resolve the absolute path for better UI/logging display
- step-by-step narration comment: // First, honor overrides and cross-platform resolution via the base implementation
- step-by-step narration comment: // First, try to resolve the absolute path for better UI/logging display
- step-by-step narration comment: // First, honor overrides and cross-platform resolution via the base implementation
- step-by-step narration comment: // First, try to resolve the absolute path for better UI/logging display.
- step-by-step narration comment: // Step 1: Check if process name matches known server executables
- step-by-step narration comment: // Step 2: Try to get command line with wmic for better validation
- count:assistant_voice
- 0
- count:emoji_in_code
- 15
- count:narrated_steps
- 38
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 8
- files:narrated_steps
- 11
- files:placeholder
- 0
- index
- 0.30
- lines_scanned
- 152,717
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0.10
- per_kloc:narrated_steps
- 0.25
- per_kloc:placeholder
- 0
Findings in AI-written linesok
- ai_lines
- 33,199
- blame_failures
- 0
- files_blamed
- 791
- other_lines
- 119,518
- quality:ai_findings
- 22
- quality:ai_per_kloc
- 0.66
- quality:other_findings
- 178
- quality:other_per_kloc
- 1.49
- quality:ratio
- 0.45
- security:ai_findings
- 6
- security:ai_per_kloc
- 0.18
- security:other_findings
- 24
- security:other_per_kloc
- 0.20
- security:ratio
- 0.90
Code quality
70 adequate
Code quality is adequate: test-to-source ratio 0.40, CI runs tests; 27% of function code in complex or long functions; 5% duplicated lines. Weakest area: type safety.
How the score is built
- Complexity44
- Duplication74
- Lint and smells77
- Tests and CI95
- Documentation80
- Type safety0
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok10 items
- ManageProBuilder::CreateShapeViaGenerator in MCPForUnity/Editor/Tools/ProBuilder/ManageProBuilder.cs: complexity 203, 186 lines
- script_apply_edits in Server/src/services/tools/script_apply_edits.py: complexity 173, 438 lines
- _iter_csharp_tokens in Server/src/services/tools/script_apply_edits.py: complexity 135, 304 lines
- FalModelSchema::Parse in MCPForUnity/Editor/Services/AssetGen/FalModelSchema.cs: complexity 126, 109 lines
- ManageScript::EditScript in MCPForUnity/Editor/Tools/ManageScript.cs: complexity 121, 412 lines
- ManageScript::TryComputeMethodSpan in MCPForUnity/Editor/Tools/ManageScript.cs: complexity 99, 168 lines
- GameObjectSerializer::GetComponentData in MCPForUnity/Editor/Helpers/GameObjectSerializer.cs: complexity 97, 273 lines
- GameObjectCreate::Handle in MCPForUnity/Editor/Tools/GameObjects/GameObjectCreate.cs: complexity 73, 292 lines
- GameObjectModify::Handle in MCPForUnity/Editor/Tools/GameObjects/GameObjectModify.cs: complexity 71, 210 lines
- ServerManagementService::StopLocalHttpServerInternal in MCPForUnity/Editor/Services/ServerManagementService.cs: complexity 66, 249 lines
- complex_functions
- 303
- function_nloc
- 100,562
- functions
- 5,663
- long_functions
- 102
- many_param_functions
- 56
- mean_ccn
- 4.72
- p90_ccn
- 11
- risky_nloc_share
- 27.4%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: CustomTools/RoslynRuntimeCompilation/RoslynRuntimeCompiler.cs:759 and CustomTools/RoslynRuntimeCompilation/RoslynRuntimeCompiler.cs:807
- 6+ duplicated lines: MCPForUnity/Editor/Clients/McpClientConfiguratorBase.cs:156 and MCPForUnity/Editor/Clients/McpClientConfiguratorBase.cs:439
- 6+ duplicated lines: MCPForUnity/Editor/Clients/McpClientConfiguratorBase.cs:993 and MCPForUnity/Editor/Windows/Components/ClientConfig/McpClientConfigSection.cs:395
- 6+ duplicated lines: MCPForUnity/Editor/Dependencies/PlatformDetectors/LinuxPlatformDetector.cs:51 and MCPForUnity/Editor/Dependencies/PlatformDetectors/WindowsPlatformDetector.cs:56
- 6+ duplicated lines: MCPForUnity/Editor/Dependencies/PlatformDetectors/LinuxPlatformDetector.cs:95 and MCPForUnity/Editor/Dependencies/PlatformDetectors/MacOSPlatformDetector.cs:93
- 6+ duplicated lines: MCPForUnity/Editor/External/Tommy.cs:383 and MCPForUnity/Editor/External/Tommy.cs:405
- 6+ duplicated lines: MCPForUnity/Editor/Helpers/AssetPathUtility.cs:337 and MCPForUnity/Editor/Helpers/AssetPathUtility.cs:388
- 6+ duplicated lines: MCPForUnity/Editor/Helpers/CodexConfigHelper.cs:31 and MCPForUnity/Editor/Helpers/CodexConfigHelper.cs:186
- 6+ duplicated lines: MCPForUnity/Editor/Helpers/ExecPath.cs:36 and MCPForUnity/Editor/Helpers/ExecPath.cs:85
- 6+ duplicated lines: MCPForUnity/Editor/Helpers/ParamCoercion.cs:132 and MCPForUnity/Editor/Helpers/ParamCoercion.cs:169
- compared_lines
- 96,587
- duplicated_lines
- 4,859
- duplicated_share
- 5.0%
- files
- 791
Lintok
- category:best-practice
- 420
- category:correctness
- 4
- category:maintainability
- 8
- findings
- 432
- scanned_lines
- 152,478
- weighted_findings
- 157
Tests and CIok12 items
- CI config: .github/workflows/beta-release.yml
.github/workflows/beta-release.yml - CI config: .github/workflows/claude-nl-suite.yml
.github/workflows/claude-nl-suite.yml - CI config: .github/workflows/compile-check.yml
.github/workflows/compile-check.yml - CI config: .github/workflows/docs-deploy.yml
.github/workflows/docs-deploy.yml - CI config: .github/workflows/docs-generate.yml
.github/workflows/docs-generate.yml - CI config: .github/workflows/e2e-bridge.yml
.github/workflows/e2e-bridge.yml - CI config: .github/workflows/github-repo-stats.yml
.github/workflows/github-repo-stats.yml - CI config: .github/workflows/python-tests.yml
.github/workflows/python-tests.yml - CI config: .github/workflows/release.yml
.github/workflows/release.yml - CI config: .github/workflows/stats.yml
.github/workflows/stats.yml - CI runs tests (pytest)
- CI runs linters (pre-commit)
- check:ci_present
- yes
- check:ci_runs_lint
- yes
- check:ci_runs_tests
- yes
- check:has_tests
- yes
- check:test_ratio
- no
- check:tests_cochange
- yes
- ci_files
- 12
- cochange_commits
- 189
- cochange_share
- 73.0%
- source_lines
- 152,717
- test_lines
- 61,242
- test_ratio
- 0.40
Documentationok3 items
- README.md
README.md - LICENSE
LICENSE - CONTRIBUTING.md
CONTRIBUTING.md
- check:changelog
- no
- check:contributing
- yes
- check:license
- yes
- check:readme
- yes
- readme_lines
- 77
Type safetyok
- check:low_escape_density
- no
- check:strict_config
- no
- escapes
- 587
- escapes_per_kloc
- 16.89
Security
52 weak
Security posture is weak: 193 known vulnerabilities in 52 dependencies; 14 high-severity SAST findings; 59 high-severity workflow issues. Weakest area: ci actions.
How the score is built
- Secrets94
- Static analysis (SAST)95
- Vulnerable dependencies0
- CI workflows0
- Security posture40
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesok
- checked
- 33
- declared
- 33
- lookup_errors
- 0
- missing
- 0
- recent
- 0
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 0
- secrets_nonprod
- 2
Static analysis (opengrep)ok
- findings
- 32
- findings_high
- 14
- findings_low
- 0
- findings_medium
- 18
- parse_errors
- 4
- scanned_lines
- 152,478
- weighted_findings
- 22.70
Dependencies (osv-scanner)ok
- penalty
- 402
- vulnerabilities
- 193
- vulnerable_packages
- 52
- vulns_critical
- 15
- vulns_high
- 83
- vulns_low
- 18
- vulns_medium
- 77
- vulns_unknown
- 0
CI workflows (zizmor)ok
- findings
- 94
- findings_high
- 59
- findings_low
- 20
- findings_medium
- 15
- penalty
- 724.30
- workflows
- 12
Security postureok3 items
- Security policy: SECURITY.md
SECURITY.md - MCPForUnity/package.json has no lockfile alongside it (unpinned dependencies)
MCPForUnity/package.json - TestProjects/AssetStoreUploads/Packages/com.unity.asset-store-tools/package.json has no lockfile alongside it (unpinned dependencies)
TestProjects/AssetStoreUploads/Packages/com.unity.asset-store-tools/package.json
- check:dependency_updates
- no
- check:lockfiles
- no
- check:security_policy
- yes
- check:signed_commits
- no
- signed_commit_share
- 18.5%
- unpinned_manifests
- 2
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
15 critical170 high124 medium204 low8 info
521 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| critical | osv/GHSA-6q48-6c7w-9gw2 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4320, GHSA-6q48-6c7w-9gw2 | Dependencies (osv-scanner) |
| critical | osv/GHSA-6v38-4h7w-rj9h |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-6v38-4h7w-rj9h | Dependencies (osv-scanner) |
| critical | osv/GHSA-7vr2-2fgp-9w7p |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4355, GHSA-7vr2-2fgp-9w7p | Dependencies (osv-scanner) |
| critical | osv/GHSA-7wc2-qxgw-g8gg |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-2118, GHSA-7wc2-qxgw-g8gg | Dependencies (osv-scanner) |
| critical | osv/GHSA-82r6-8w77-94w6 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4025, GHSA-82r6-8w77-94w6 | Dependencies (osv-scanner) |
| critical | osv/GHSA-8m4g-j4wp-wgcg |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4356, GHSA-8m4g-j4wp-wgcg | Dependencies (osv-scanner) |
| critical | osv/GHSA-ffc3-869f-jxw9 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4145, GHSA-ffc3-869f-jxw9 | Dependencies (osv-scanner) |
| critical | osv/GHSA-p423-j2cm-9vmq |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-36, GHSA-p423-j2cm-9vmq | Dependencies (osv-scanner) |
| critical | osv/GHSA-vv7q-7jx5-f767 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-338, GHSA-vv7q-7jx5-f767 | Dependencies (osv-scanner) |
| critical | osv/GHSA-wvwj-cvrp-7pv5 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-287, GHSA-wvwj-cvrp-7pv5 | Dependencies (osv-scanner) |
| critical | osv/GHSA-5gmw-xhrv-c9v3 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-5gmw-xhrv-c9v3 | Dependencies (osv-scanner) |
| critical | osv/GHSA-85c8-ppgw-ccpr |
website/package-lock.json | [email protected] (npm) is affected by GHSA-85c8-ppgw-ccpr | Dependencies (osv-scanner) |
| critical | osv/GHSA-jqcg-44mw-7w3h |
website/package-lock.json | [email protected] (npm) is affected by GHSA-jqcg-44mw-7w3h | Dependencies (osv-scanner) |
| critical | osv/GHSA-pqg4-j6r4-53mv |
website/package-lock.json | [email protected] (npm) is affected by GHSA-pqg4-j6r4-53mv | Dependencies (osv-scanner) |
| critical | osv/GHSA-xv26-6w52-cph6 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-xv26-6w52-cph6 | Dependencies (osv-scanner) |
| high | opengrep/python.lang.maintainability.useless-inner-function |
Server/src/main.py:387 | function `health_http` is defined inside a function but never used | Lint |
| high | opengrep/python.lang.maintainability.useless-inner-function |
Server/src/main.py:396 | function `auth_login_url` is defined inside a function but never used | Lint |
| high | opengrep/python.lang.maintainability.useless-inner-function |
Server/src/main.py:414 | function `cli_command_route` is defined inside a function but never used | Lint |
| high | opengrep/python.lang.maintainability.useless-inner-function |
Server/src/main.py:534 | function `cli_instances_route` is defined inside a function but never used | Lint |
| high | opengrep/python.lang.maintainability.useless-inner-function |
Server/src/main.py:552 | function `cli_custom_tools_route` is defined inside a function but never used | Lint |
| high | opengrep/python.lang.maintainability.useless-inner-function |
Server/src/services/custom_tool_service.py:89 | function `register_tools` is defined inside a function but never used | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
tools/local_harness.py:1044 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
tools/local_harness.py:1231 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
tools/local_harness.py:1234 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
tools/local_harness.py:1239 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
tools/local_harness.py:1244 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
tools/local_harness.py:1352 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
tools/local_harness.py:1357 | time.sleep() call; did you mean to leave this in? | Lint |
| high | opengrep/python.lang.best-practice.arbitrary-sleep |
tools/local_harness.py:860 | time.sleep() call; did you mean to leave this in? | Lint |
| high | zizmor/unpinned-uses |
.github/actions/publish-docker/action.yml:102 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/actions/publish-docker/action.yml:37 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/actions/publish-docker/action.yml:44 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/actions/publish-docker/action.yml:56 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/template-injection |
.github/actions/publish-docker/action.yml:71 | code injection via template expansion [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/actions/publish-docker/action.yml:77 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/actions/publish-docker/action.yml:89 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/actions/publish-docker/action.yml:99 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/actions/publish-pypi/action.yml:20 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/actions/publish-pypi/action.yml:7 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | opengrep/python.lang.security.use-defused-xml |
.github/scripts/mark_skipped.py:15 | The Python documentation recommends using `defusedxml` instead of `xml` because the native Python `xml` library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.use-defused-xml-parse |
.github/scripts/mark_skipped.py:65 | The native Python `xml` library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause denial of service. Do not use this library to parse untrusted input. Instead the... | Static analysis (opengrep) |
| high | zizmor/unpinned-uses |
.github/workflows/beta-release.yml:168 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/cache-poisoning |
.github/workflows/beta-release.yml:174 | runtime artifacts potentially vulnerable to a cache poisoning attack [confidence low] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/beta-release.yml:174 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/beta-release.yml:239 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/beta-release.yml:41 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/claude-nl-suite.yml:1634 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/claude-nl-suite.yml:1649 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/claude-nl-suite.yml:1669 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/claude-nl-suite.yml:44 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/claude-nl-suite.yml:49 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/compile-check.yml:51 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/excessive-permissions |
.github/workflows/docs-deploy.yml:33 | overly broad permissions [confidence high] | CI workflows (zizmor) |
| high | zizmor/excessive-permissions |
.github/workflows/docs-deploy.yml:34 | overly broad permissions [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/docs-deploy.yml:46 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/docs-deploy.yml:57 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/docs-deploy.yml:69 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/docs-deploy.yml:82 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/docs-deploy.yml:97 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/docs-generate.yml:40 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/docs-generate.yml:45 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/e2e-bridge.yml:162 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/e2e-bridge.yml:81 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/e2e-bridge.yml:85 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/github-repo-stats.yml:18 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/python-tests.yml:51 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/python-tests.yml:56 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/python-tests.yml:83 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/python-tests.yml:96 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/release.yml:311 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/release.yml:327 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/release.yml:483 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/release.yml:512 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/cache-poisoning |
.github/workflows/release.yml:520 | runtime artifacts potentially vulnerable to a cache poisoning attack [confidence low] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/release.yml:520 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/release.yml:532 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/release.yml:545 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/cache-poisoning |
.github/workflows/release.yml:551 | runtime artifacts potentially vulnerable to a cache poisoning attack [confidence low] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/release.yml:551 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/release.yml:556 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/release.yml:57 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/release.yml:571 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/stats.yml:14 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/stats.yml:15 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/sync-releases.yml:56 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/sync-releases.yml:66 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/unity-tests.yml:156 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/unity-tests.yml:162 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/unity-tests.yml:233 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/unity-tests.yml:63 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | opengrep/dockerfile.security.missing-user-entrypoint |
Server/Dockerfile:35 | By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile... | Static analysis (opengrep) |
| high | opengrep/dockerfile.security.missing-user |
Server/Dockerfile:36 | By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile... | Static analysis (opengrep) |
| high | osv/GHSA-45c3-73f7-pv4m |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-45c3-73f7-pv4m | Dependencies (osv-scanner) |
| high | osv/GHSA-537c-gmf6-5ccf |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-537c-gmf6-5ccf | Dependencies (osv-scanner) |
| high | osv/GHSA-58pv-8j8x-9vj2 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-1469, GHSA-58pv-8j8x-9vj2 | Dependencies (osv-scanner) |
| high | osv/GHSA-5rvq-cxj2-64vf |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-3036, GHSA-5rvq-cxj2-64vf | Dependencies (osv-scanner) |
| high | osv/GHSA-7432-952r-cw78 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-2116, GHSA-7432-952r-cw78 | Dependencies (osv-scanner) |
| high | osv/GHSA-752w-5fwx-jx9f |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-120, GHSA-752w-5fwx-jx9f | Dependencies (osv-scanner) |
| high | osv/GHSA-82w8-qh3p-5jfq |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-249, GHSA-82w8-qh3p-5jfq | Dependencies (osv-scanner) |
| high | osv/GHSA-84m7-p3x7-pcfv |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-84m7-p3x7-pcfv | Dependencies (osv-scanner) |
| high | osv/GHSA-8988-9cw3-xx77 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4175, GHSA-8988-9cw3-xx77 | Dependencies (osv-scanner) |
| high | osv/GHSA-9v7f-9g4p-ffgj |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4144, GHSA-9v7f-9g4p-ffgj | Dependencies (osv-scanner) |
| high | osv/GHSA-c73q-w75p-j82v |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-c73q-w75p-j82v | Dependencies (osv-scanner) |
| high | osv/GHSA-g6cj-pr64-35w5 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-3552, GHSA-g6cj-pr64-35w5 | Dependencies (osv-scanner) |
| high | osv/GHSA-hvrp-rf83-w775 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-3481, GHSA-hvrp-rf83-w775 | Dependencies (osv-scanner) |
| high | osv/GHSA-jpw9-pfvf-9f58 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-3482, GHSA-jpw9-pfvf-9f58 | Dependencies (osv-scanner) |
| high | osv/GHSA-jwv3-5hgf-82ww |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-3553, GHSA-jwv3-5hgf-82ww | Dependencies (osv-scanner) |
| high | osv/GHSA-m344-f55w-2m6j |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-2117, GHSA-m344-f55w-2m6j | Dependencies (osv-scanner) |
| high | osv/GHSA-mf9v-mfxr-j63j |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-142, GHSA-mf9v-mfxr-j63j | Dependencies (osv-scanner) |
| high | osv/GHSA-p4g4-x82p-q773 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4149, GHSA-p4g4-x82p-q773 | Dependencies (osv-scanner) |
| high | osv/GHSA-pp6c-gr5w-3c5g |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-3039, GHSA-pp6c-gr5w-3c5g | Dependencies (osv-scanner) |
| high | osv/GHSA-pxh4-856f-4h89 |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-pxh4-856f-4h89 | Dependencies (osv-scanner) |
| high | osv/GHSA-qccp-gfcp-xxvc |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-141, GHSA-qccp-gfcp-xxvc | Dependencies (osv-scanner) |
| high | osv/GHSA-r6ph-v2qm-q3c2 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-2141, GHSA-r6ph-v2qm-q3c2 | Dependencies (osv-scanner) |
| high | osv/GHSA-rww4-4w9c-7733 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-2476, GHSA-rww4-4w9c-7733 | Dependencies (osv-scanner) |
| high | osv/GHSA-vj7q-gjh5-988w |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-3483, GHSA-vj7q-gjh5-988w | Dependencies (osv-scanner) |
| high | osv/GHSA-vvf4-9x63-8xvv |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-vvf4-9x63-8xvv | Dependencies (osv-scanner) |
| high | osv/GHSA-vxq7-64xx-v4gw |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4177, GHSA-vxq7-64xx-v4gw | Dependencies (osv-scanner) |
| high | osv/GHSA-wp53-j4wj-2cfg |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-1852, GHSA-wp53-j4wj-2cfg | Dependencies (osv-scanner) |
| high | osv/GHSA-wqp7-x3pw-xc5r |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-2281, GHSA-wqp7-x3pw-xc5r | Dependencies (osv-scanner) |
| high | osv/GHSA-x33g-cr3x-6449 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4183, GHSA-x33g-cr3x-6449 | Dependencies (osv-scanner) |
| high | osv/GHSA-xgmm-8j9v-c9wx |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-179, GHSA-xgmm-8j9v-c9wx | Dependencies (osv-scanner) |
| high | osv/PYSEC-2025-183 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2025-183 | Dependencies (osv-scanner) |
| high | opengrep/python.lang.security.use-defused-xml-parse |
tools/check_unity_test_results.py:22 | The native Python `xml` library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause denial of service. Do not use this library to parse untrusted input. Instead the... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.use-defused-xml |
tools/check_unity_test_results.py:6 | The Python documentation recommends using `defusedxml` instead of `xml` because the native Python `xml` library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
tools/ci_unity_license.py:123 | Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.use-defused-xml |
tools/ci_unity_license.py:17 | The Python documentation recommends using `defusedxml` instead of `xml` because the native Python `xml` library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
tools/local_harness.py:1145 | Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.use-defused-xml |
tools/local_harness.py:71 | The Python documentation recommends using `defusedxml` instead of `xml` because the native Python `xml` library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
tools/local_harness.py:796 | Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
tools/local_harness.py:813 | Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit |
tools/local_harness.py:929 | Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external... | Static analysis (opengrep) |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-tainted-env-args |
tools/local_harness.py:929 | Detected subprocess function 'run' with user controlled data. A malicious actor could leverage this to perform command injection. You may consider using 'shlex.quote()'. [confidence medium] | Static analysis (opengrep) |
| high | osv/GHSA-27r3-jxmh-p828 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-27r3-jxmh-p828 | Dependencies (osv-scanner) |
| high | osv/GHSA-2883-xcg3-v3hh |
website/package-lock.json | [email protected] (npm) is affected by GHSA-2883-xcg3-v3hh | Dependencies (osv-scanner) |
| high | osv/GHSA-2883-xcg3-v3hh |
website/package-lock.json | [email protected] (npm) is affected by GHSA-2883-xcg3-v3hh | Dependencies (osv-scanner) |
| high | osv/GHSA-28wg-ghj8-5hjv |
website/package-lock.json | [email protected] (npm) is affected by GHSA-28wg-ghj8-5hjv | Dependencies (osv-scanner) |
| high | osv/GHSA-2m5v-pch6-74hx |
website/package-lock.json | [email protected] (npm) is affected by GHSA-2m5v-pch6-74hx | Dependencies (osv-scanner) |
| high | osv/GHSA-2p49-hgcm-8545 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-2p49-hgcm-8545 | Dependencies (osv-scanner) |
| high | osv/GHSA-2v37-7h3g-55p8 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-2v37-7h3g-55p8 | Dependencies (osv-scanner) |
| high | osv/GHSA-395f-4hp3-45gv |
website/package-lock.json | [email protected] (npm) is affected by GHSA-395f-4hp3-45gv | Dependencies (osv-scanner) |
| high | osv/GHSA-3jxr-9vmj-r5cp |
website/package-lock.json | [email protected] (npm) is affected by GHSA-3jxr-9vmj-r5cp | Dependencies (osv-scanner) |
| high | osv/GHSA-4528-x5fx-h6hg |
website/package-lock.json | [email protected] (npm) is affected by GHSA-4528-x5fx-h6hg | Dependencies (osv-scanner) |
| high | osv/GHSA-4c8g-83qw-93j6 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-4c8g-83qw-93j6 | Dependencies (osv-scanner) |
| high | osv/GHSA-4cwx-7wf7-3272 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-4cwx-7wf7-3272 | Dependencies (osv-scanner) |
| high | osv/GHSA-4w7w-5xrc-9h26 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-4w7w-5xrc-9h26 | Dependencies (osv-scanner) |
| high | osv/GHSA-52cp-r559-cp3m |
website/package-lock.json | [email protected] (npm) is affected by GHSA-52cp-r559-cp3m | Dependencies (osv-scanner) |
| high | osv/GHSA-52cp-r559-cp3m |
website/package-lock.json | [email protected] (npm) is affected by GHSA-52cp-r559-cp3m | Dependencies (osv-scanner) |
| high | osv/GHSA-587h-7wmj-h5pm |
website/package-lock.json | [email protected] (npm) is affected by GHSA-587h-7wmj-h5pm | Dependencies (osv-scanner) |
| high | osv/GHSA-5c6j-r48x-rmvq |
website/package-lock.json | [email protected] (npm) is affected by GHSA-5c6j-r48x-rmvq | Dependencies (osv-scanner) |
| high | osv/GHSA-5p2g-fcmc-qvqq |
website/package-lock.json | [email protected] (npm) is affected by GHSA-5p2g-fcmc-qvqq | Dependencies (osv-scanner) |
| high | osv/GHSA-5p4m-2wfm-xmqj |
website/package-lock.json | [email protected] (npm) is affected by GHSA-5p4m-2wfm-xmqj | Dependencies (osv-scanner) |
| high | osv/GHSA-5p4m-2wfm-xmqj |
website/package-lock.json | [email protected] (npm) is affected by GHSA-5p4m-2wfm-xmqj | Dependencies (osv-scanner) |
| high | osv/GHSA-68fv-2mgg-jv7q |
website/package-lock.json | [email protected] (npm) is affected by GHSA-68fv-2mgg-jv7q | Dependencies (osv-scanner) |
| high | osv/GHSA-6h2x-m376-mqjq |
website/package-lock.json | [email protected] (npm) is affected by GHSA-6h2x-m376-mqjq | Dependencies (osv-scanner) |
| high | osv/GHSA-6j4f-fj2g-mc7p |
website/package-lock.json | [email protected] (npm) is affected by GHSA-6j4f-fj2g-mc7p | Dependencies (osv-scanner) |
| high | osv/GHSA-73wf-gq98-2v4g |
website/package-lock.json | [email protected] (npm) is affected by GHSA-73wf-gq98-2v4g | Dependencies (osv-scanner) |
| high | osv/GHSA-7p8r-x3mc-p8w7 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-7p8r-x3mc-p8w7 | Dependencies (osv-scanner) |
| high | osv/GHSA-8r9p-f939-6h3c |
website/package-lock.json | [email protected] (npm) is affected by GHSA-8r9p-f939-6h3c | Dependencies (osv-scanner) |
| high | osv/GHSA-c83g-rgw3-j3cx |
website/package-lock.json | [email protected] (npm) is affected by GHSA-c83g-rgw3-j3cx | Dependencies (osv-scanner) |
| high | osv/GHSA-f65p-4m7j-42xc |
website/package-lock.json | [email protected] (npm) is affected by GHSA-f65p-4m7j-42xc | Dependencies (osv-scanner) |
| high | osv/GHSA-fph4-wmhf-6fwf |
website/package-lock.json | [email protected] (npm) is affected by GHSA-fph4-wmhf-6fwf | Dependencies (osv-scanner) |
| high | osv/GHSA-g84c-rxfj-3j2c |
website/package-lock.json | [email protected] (npm) is affected by GHSA-g84c-rxfj-3j2c | Dependencies (osv-scanner) |
| high | osv/GHSA-hm92-r4w5-c3mj |
website/package-lock.json | [email protected] (npm) is affected by GHSA-hm92-r4w5-c3mj | Dependencies (osv-scanner) |
| high | osv/GHSA-jqff-g426-hqxp |
website/package-lock.json | [email protected] (npm) is affected by GHSA-jqff-g426-hqxp | Dependencies (osv-scanner) |
| high | osv/GHSA-mh99-v99m-4gvg |
website/package-lock.json | [email protected] (npm) is affected by GHSA-mh99-v99m-4gvg | Dependencies (osv-scanner) |
| high | osv/GHSA-mrwp-f3q8-3g9p |
website/package-lock.json | [email protected] (npm) is affected by GHSA-mrwp-f3q8-3g9p | Dependencies (osv-scanner) |
| high | osv/GHSA-q3jh-wrc6-jgq8 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-q3jh-wrc6-jgq8 | Dependencies (osv-scanner) |
| high | osv/GHSA-qhr7-859c-m2p7 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-qhr7-859c-m2p7 | Dependencies (osv-scanner) |
| high | osv/GHSA-qrxm-fqhp-jwvm |
website/package-lock.json | [email protected] (npm) is affected by GHSA-qrxm-fqhp-jwvm | Dependencies (osv-scanner) |
| high | osv/GHSA-qw65-cvwx-89v3 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-qw65-cvwx-89v3 | Dependencies (osv-scanner) |
| high | osv/GHSA-r28c-9q8g-f849 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-r28c-9q8g-f849 | Dependencies (osv-scanner) |
| high | osv/GHSA-rfgv-xxqx-mfg5 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-rfgv-xxqx-mfg5 | Dependencies (osv-scanner) |
| high | osv/GHSA-rgj7-g3m4-5g8c |
website/package-lock.json | [email protected] (npm) is affected by GHSA-rgj7-g3m4-5g8c | Dependencies (osv-scanner) |
| high | osv/GHSA-rgw5-rvv9-x895 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-rgw5-rvv9-x895 | Dependencies (osv-scanner) |
| high | osv/GHSA-v2hh-gcrm-f6hx |
website/package-lock.json | [email protected] (npm) is affected by GHSA-v2hh-gcrm-f6hx | Dependencies (osv-scanner) |
| high | osv/GHSA-vc2v-76pw-4v95 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-vc2v-76pw-4v95 | Dependencies (osv-scanner) |
| high | osv/GHSA-vmh5-mc38-953g |
website/package-lock.json | [email protected] (npm) is affected by GHSA-vmh5-mc38-953g | Dependencies (osv-scanner) |
| high | osv/GHSA-vxpw-j846-p89q |
website/package-lock.json | [email protected] (npm) is affected by GHSA-vxpw-j846-p89q | Dependencies (osv-scanner) |
| high | osv/GHSA-w27v-7q3p-w38r |
website/package-lock.json | [email protected] (npm) is affected by GHSA-w27v-7q3p-w38r | Dependencies (osv-scanner) |
| high | osv/GHSA-w293-vg96-wgc3 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-w293-vg96-wgc3 | Dependencies (osv-scanner) |
| high | osv/GHSA-w3rx-r6r6-pgpr |
website/package-lock.json | [email protected] (npm) is affected by GHSA-w3rx-r6r6-pgpr | Dependencies (osv-scanner) |
| high | osv/GHSA-w5hq-g745-h8pq |
website/package-lock.json | [email protected] (npm) is affected by GHSA-w5hq-g745-h8pq | Dependencies (osv-scanner) |
| high | osv/GHSA-wq5f-xc86-pv6w |
website/package-lock.json | [email protected] (npm) is affected by GHSA-wq5f-xc86-pv6w | Dependencies (osv-scanner) |
| high | osv/GHSA-xjj6-f33q-929c |
website/package-lock.json | [email protected] (npm) is affected by GHSA-xjj6-f33q-929c | Dependencies (osv-scanner) |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
Server/src/cli/commands/batch.py:167 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
Server/src/cli/commands/batch.py:47 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
Server/src/cli/commands/shader.py:171 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
Server/src/cli/commands/shader.py:82 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.maintainability.return-not-in-function |
Server/src/core/config.py:59 | `return` only makes sense inside a function | Lint |
| medium | opengrep/python.lang.maintainability.return-not-in-function |
Server/src/core/config.py:65 | `return` only makes sense inside a function | Lint |
| medium | opengrep/python.lang.best-practice.logging-error-without-handling |
Server/src/main.py:845 | Errors should only be logged when handled. The code logs the error and propogates the exception, consider reducing the level to warning or info. | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
Server/src/services/tools/manage_script.py:354 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
Server/src/transport/legacy/port_discovery.py:157 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.unspecified-open-encoding |
Server/src/transport/legacy/port_discovery.py:195 | Missing 'encoding' parameter. 'open()' uses device locale encodings by default, corrupting files with special characters. Specify the encoding to ensure cross-platform support when opening files in text mode (e.g. encoding="utf-8"). | Lint |
| medium | opengrep/python.lang.best-practice.logging-error-without-handling |
Server/src/transport/legacy/unity_connection.py:210 | Errors should only be logged when handled. The code logs the error and propogates the exception, consider reducing the level to warning or info. | Lint |
| medium | opengrep/python.lang.best-practice.logging-error-without-handling |
Server/src/transport/legacy/unity_connection.py:267 | Errors should only be logged when handled. The code logs the error and propogates the exception, consider reducing the level to warning or info. | Lint |
| medium | opengrep/python.lang.correctness.common-mistakes.string-concat-in-list |
Server/src/utils/focus_nudge.py:156 | Detected strings that are implicitly concatenated inside a list. Python will implicitly concatenate strings when not explicitly delimited. Was this supposed to be individual elements of the list? | Lint |
| medium | opengrep/python.lang.correctness.common-mistakes.string-concat-in-list |
tools/generate_docs_reference.py:374 | Detected strings that are implicitly concatenated inside a list. Python will implicitly concatenate strings when not explicitly delimited. Was this supposed to be individual elements of the list? | Lint |
| medium | zizmor/excessive-permissions |
.github/workflows/beta-release.yml:1 | overly broad permissions [confidence medium] | CI workflows (zizmor) |
| medium | zizmor/excessive-permissions |
.github/workflows/beta-release.yml:16 | overly broad permissions [confidence medium] | CI workflows (zizmor) |
| medium | zizmor/secrets-inherit |
.github/workflows/beta-release.yml:19 | secrets unconditionally inherited by called workflow [confidence high] | CI workflows (zizmor) |
| medium | zizmor/excessive-permissions |
.github/workflows/beta-release.yml:22 | overly broad permissions [confidence medium] | CI workflows (zizmor) |
| medium | zizmor/artipacked |
.github/workflows/claude-nl-suite.yml:44 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| medium | zizmor/excessive-permissions |
.github/workflows/docs-generate.yml:35 | overly broad permissions [confidence medium] | CI workflows (zizmor) |
| medium | zizmor/artipacked |
.github/workflows/e2e-bridge.yml:81 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| medium | zizmor/excessive-permissions |
.github/workflows/github-repo-stats.yml:11 | overly broad permissions [confidence medium] | CI workflows (zizmor) |
| medium | zizmor/excessive-permissions |
.github/workflows/python-tests.yml:40 | overly broad permissions [confidence medium] | CI workflows (zizmor) |
| medium | zizmor/artipacked |
.github/workflows/python-tests.yml:50 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| medium | zizmor/excessive-permissions |
.github/workflows/release.yml:1 | overly broad permissions [confidence medium] | CI workflows (zizmor) |
| medium | zizmor/excessive-permissions |
.github/workflows/release.yml:22 | overly broad permissions [confidence medium] | CI workflows (zizmor) |
| medium | zizmor/secrets-inherit |
.github/workflows/release.yml:24 | secrets unconditionally inherited by called workflow [confidence high] | CI workflows (zizmor) |
| medium | zizmor/excessive-permissions |
.github/workflows/release.yml:29 | overly broad permissions [confidence medium] | CI workflows (zizmor) |
| medium | zizmor/artipacked |
.github/workflows/stats.yml:14 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| medium | opengrep/python.lang.security.audit.non-literal-import |
Server/src/cli/main.py:224 | Untrusted user input in `importlib.import_module()` function allows an attacker to load arbitrary code. Avoid dynamic values in `importlib.import_module()` or use a whitelist to prevent running untrusted code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.non-literal-import |
Server/src/core/telemetry.py:137 | Untrusted user input in `importlib.import_module()` function allows an attacker to load arbitrary code. Avoid dynamic values in `importlib.import_module()` or use a whitelist to prevent running untrusted code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.dynamic-urllib-use-detected |
Server/src/core/telemetry.py:426 | Detected a dynamic value being used with urllib. urllib supports 'file://' schemes, so a dynamic value controlled by a malicious actor may allow them to read arbitrary files. Audit uses of urllib calls to ensure user data cannot control... | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.logging.python-logger-credential-disclosure |
Server/src/main.py:629 | Detected a python logger call with a potential hardcoded secret "Initialized API key authentication service (validation URL: %s, TTL: %.0fs)" being logged. This may lead to secret credentials being exposed. Make sure that the logger is... | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.logging.python-logger-credential-disclosure |
Server/src/services/api_key_service.py:183 | Detected a python logger call with a potential hardcoded secret "API key validation returned status %d for key %s" being logged. This may lead to secret credentials being exposed. Make sure that the logger is not logging sensitive... | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.logging.python-logger-credential-disclosure |
Server/src/services/api_key_service.py:197 | Detected a python logger call with a potential hardcoded secret "API key validation timeout for key %s, retrying..." being logged. This may lead to secret credentials being exposed. Make sure that the logger is not logging sensitive... | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.logging.python-logger-credential-disclosure |
Server/src/services/api_key_service.py:203 | Detected a python logger call with a potential hardcoded secret "API key validation timeout for key %s after %d attempts" being logged. This may lead to secret credentials being exposed. Make sure that the logger is not logging ... | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.logging.python-logger-credential-disclosure |
Server/src/services/api_key_service.py:215 | Detected a python logger call with a potential hardcoded secret "API key validation request error for key %s: %s, retrying..." being logged. This may lead to secret credentials being exposed. Make sure that the logger is not logging ... | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.logging.python-logger-credential-disclosure |
Server/src/services/api_key_service.py:222 | Detected a python logger call with a potential hardcoded secret "API key validation request error for key %s: %s" being logged. This may lead to secret credentials being exposed. Make sure that the logger is not logging sensitive... | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.logging.python-logger-credential-disclosure |
Server/src/services/api_key_service.py:233 | Detected a python logger call with a potential hardcoded secret "Unexpected error validating API key %s: %s" being logged. This may lead to secret credentials being exposed. Make sure that the logger is not logging sensitive... | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.dangerous-globals-use |
Server/src/services/tools/manage_prefabs.py:90 | Found non static data as an index to 'globals()'. This is extremely dangerous because it allows an attacker to execute arbitrary code on the system. Refactor your code not to use 'globals()'. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.dynamic-urllib-use-detected |
Server/src/services/tools/unity_docs.py:94 | Detected a dynamic value being used with urllib. urllib supports 'file://' schemes, so a dynamic value controlled by a malicious actor may allow them to read arbitrary files. Audit uses of urllib calls to ensure user data cannot control... | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.non-literal-import |
Server/src/utils/module_discovery.py:32 | Untrusted user input in `importlib.import_module()` function allows an attacker to load arbitrary code. Avoid dynamic values in `importlib.import_module()` or use a whitelist to prevent running untrusted code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.non-literal-import |
Server/src/utils/module_discovery.py:51 | Untrusted user input in `importlib.import_module()` function allows an attacker to load arbitrary code. Avoid dynamic values in `importlib.import_module()` or use a whitelist to prevent running untrusted code. [confidence low] | Static analysis (opengrep) |
| medium | osv/GHSA-2gx3-rcp4-g85q |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4140, GHSA-2gx3-rcp4-g85q | Dependencies (osv-scanner) |
| medium | osv/GHSA-42vr-xj54-vc7v |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4141, GHSA-42vr-xj54-vc7v | Dependencies (osv-scanner) |
| medium | osv/GHSA-4xgf-cpjx-pc3j |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-4xgf-cpjx-pc3j | Dependencies (osv-scanner) |
| medium | osv/GHSA-5h93-6whr-6q8j |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-5h93-6whr-6q8j | Dependencies (osv-scanner) |
| medium | osv/GHSA-5p39-cfhj-2xmp |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4024, GHSA-5p39-cfhj-2xmp | Dependencies (osv-scanner) |
| medium | osv/GHSA-65pc-fj4g-8rjx |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-215, GHSA-65pc-fj4g-8rjx | Dependencies (osv-scanner) |
| medium | osv/GHSA-6w46-j5rx-g56g |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-1845, GHSA-6w46-j5rx-g56g | Dependencies (osv-scanner) |
| medium | osv/GHSA-7xgj-8392-5q4r |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-7xgj-8392-5q4r | Dependencies (osv-scanner) |
| medium | osv/GHSA-86qp-5c8j-p5mr |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-161, GHSA-86qp-5c8j-p5mr | Dependencies (osv-scanner) |
| medium | osv/GHSA-993g-76c3-p5m4 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-175, GHSA-993g-76c3-p5m4 | Dependencies (osv-scanner) |
| medium | osv/GHSA-c5mf-xmp2-59rc |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4357, GHSA-c5mf-xmp2-59rc | Dependencies (osv-scanner) |
| medium | osv/GHSA-fch4-3c6x-j4gc |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4358, GHSA-fch4-3c6x-j4gc | Dependencies (osv-scanner) |
| medium | osv/GHSA-gc5v-m9x4-r6x2 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-2275, GHSA-gc5v-m9x4-r6x2 | Dependencies (osv-scanner) |
| medium | osv/GHSA-gh4c-6fx4-qh6g |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4176, GHSA-gh4c-6fx4-qh6g | Dependencies (osv-scanner) |
| medium | osv/GHSA-hxm8-2xgr-2p9m |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4147, GHSA-hxm8-2xgr-2p9m | Dependencies (osv-scanner) |
| medium | osv/GHSA-jj8c-mmj3-mmgv |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-25, GHSA-jj8c-mmj3-mmgv | Dependencies (osv-scanner) |
| medium | osv/GHSA-jp82-jpqv-5vv3 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-248, GHSA-jp82-jpqv-5vv3 | Dependencies (osv-scanner) |
| medium | osv/GHSA-jq35-7prp-9v3f |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-176, GHSA-jq35-7prp-9v3f | Dependencies (osv-scanner) |
| medium | osv/GHSA-jwrc-g2q2-pq5p |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4148, GHSA-jwrc-g2q2-pq5p | Dependencies (osv-scanner) |
| medium | osv/GHSA-m2h6-j472-rp4c |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-3554, GHSA-m2h6-j472-rp4c | Dependencies (osv-scanner) |
| medium | osv/GHSA-m8x7-r2rg-vh5g |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-2475, GHSA-m8x7-r2rg-vh5g | Dependencies (osv-scanner) |
| medium | osv/GHSA-m959-cc7f-wv43 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-35, GHSA-m959-cc7f-wv43 | Dependencies (osv-scanner) |
| medium | osv/GHSA-mf5v-w3w3-f6cg |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-mf5v-w3w3-f6cg | Dependencies (osv-scanner) |
| medium | osv/GHSA-mf9w-mj56-hr94 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-2270, GHSA-mf9w-mj56-hr94 | Dependencies (osv-scanner) |
| medium | osv/GHSA-mj87-hwqh-73pj |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-3038, GHSA-mj87-hwqh-73pj | Dependencies (osv-scanner) |
| medium | osv/GHSA-q686-2qmg-hqc7 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4359, GHSA-q686-2qmg-hqc7 | Dependencies (osv-scanner) |
| medium | osv/GHSA-r95x-qfjj-fjj2 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-188, GHSA-r95x-qfjj-fjj2 | Dependencies (osv-scanner) |
| medium | osv/GHSA-rwrf-2pqf-9j8j |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-rwrf-2pqf-9j8j | Dependencies (osv-scanner) |
| medium | osv/GHSA-w4fh-qvv9-3v23 |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-w4fh-qvv9-3v23 | Dependencies (osv-scanner) |
| medium | osv/GHSA-w6j9-cwv2-h6wq |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4152, GHSA-w6j9-cwv2-h6wq | Dependencies (osv-scanner) |
| medium | osv/GHSA-w7vc-732c-9m39 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-178, GHSA-w7vc-732c-9m39 | Dependencies (osv-scanner) |
| medium | osv/GHSA-w8p2-r796-3vmq |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-2119, GHSA-w8p2-r796-3vmq | Dependencies (osv-scanner) |
| medium | osv/GHSA-x4rv-c3wx-4cr8 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4360, GHSA-x4rv-c3wx-4cr8 | Dependencies (osv-scanner) |
| medium | osv/GHSA-x746-7m8f-x49c |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-2280, GHSA-x746-7m8f-x49c | Dependencies (osv-scanner) |
| medium | osv/GHSA-xcq7-p3pf-p88h |
Server/uv.lock | [email protected] (PyPI) is affected by GHSA-xcq7-p3pf-p88h | Dependencies (osv-scanner) |
| medium | opengrep/csharp.lang.security.insecure-deserialization.insecure-newtonsoft-deserialization |
TestProjects/AssetStoreUploads/Packages/com.unity.asset-store-tools/Editor/Validator/Scripts/Services/CachingService/CachingService.cs:29 | TypeNameHandling Auto is unsafe and can lead to arbitrary code execution in the context of the process. Use a custom SerializationBinder whenever using a setting other than TypeNameHandling.None. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/csharp.lang.security.insecure-deserialization.insecure-newtonsoft-deserialization |
TestProjects/AssetStoreUploads/Packages/com.unity.asset-store-tools/Editor/Validator/Scripts/Services/CachingService/CachingService.cs:48 | TypeNameHandling Auto is unsafe and can lead to arbitrary code execution in the context of the process. Use a custom SerializationBinder whenever using a setting other than TypeNameHandling.None. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.dynamic-urllib-use-detected |
tools/ci_unity_license.py:68 | Detected a dynamic value being used with urllib. urllib supports 'file://' schemes, so a dynamic value controlled by a malicious actor may allow them to read arbitrary files. Audit uses of urllib calls to ensure user data cannot control... | Static analysis (opengrep) |
| medium | opengrep/python.lang.security.audit.dynamic-urllib-use-detected |
tools/sync_release_notes.py:123 | Detected a dynamic value being used with urllib. urllib supports 'file://' schemes, so a dynamic value controlled by a malicious actor may allow them to read arbitrary files. Audit uses of urllib calls to ensure user data cannot control... | Static analysis (opengrep) |
| medium | osv/GHSA-2jfj-6hjv-fm6j |
website/package-lock.json | [email protected] (npm) is affected by GHSA-2jfj-6hjv-fm6j | Dependencies (osv-scanner) |
| medium | osv/GHSA-2wm5-q62r-hmrv |
website/package-lock.json | [email protected] (npm) is affected by GHSA-2wm5-q62r-hmrv | Dependencies (osv-scanner) |
| medium | osv/GHSA-3xpg-4rpp-hhhm |
website/package-lock.json | [email protected] (npm) is affected by GHSA-3xpg-4rpp-hhhm | Dependencies (osv-scanner) |
| medium | osv/GHSA-4mjr-xmp4-gh2g |
website/package-lock.json | [email protected] (npm) is affected by GHSA-4mjr-xmp4-gh2g | Dependencies (osv-scanner) |
| medium | osv/GHSA-4qv8-2p9j-2685 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-4qv8-2p9j-2685 | Dependencies (osv-scanner) |
| medium | osv/GHSA-4vpr-x523-8j87 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-4vpr-x523-8j87 | Dependencies (osv-scanner) |
| medium | osv/GHSA-55wc-3pg8-jfw6 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-55wc-3pg8-jfw6 | Dependencies (osv-scanner) |
| medium | osv/GHSA-64mm-vxmg-q3vj |
website/package-lock.json | [email protected] (npm) is affected by GHSA-64mm-vxmg-q3vj | Dependencies (osv-scanner) |
| medium | osv/GHSA-698v-4r3x-3vcv |
website/package-lock.json | [email protected] (npm) is affected by GHSA-698v-4r3x-3vcv | Dependencies (osv-scanner) |
| medium | osv/GHSA-6pq8-jhm2-2vcw |
website/package-lock.json | [email protected] (npm) is affected by GHSA-6pq8-jhm2-2vcw | Dependencies (osv-scanner) |
| medium | osv/GHSA-8xcm-r25x-g524 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-8xcm-r25x-g524 | Dependencies (osv-scanner) |
| medium | osv/GHSA-9fm3-97px-rjf6 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-9fm3-97px-rjf6 | Dependencies (osv-scanner) |
| medium | osv/GHSA-f5vj-f2hx-8m93 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-f5vj-f2hx-8m93 | Dependencies (osv-scanner) |
| medium | osv/GHSA-f72v-6w45-q472 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-f72v-6w45-q472 | Dependencies (osv-scanner) |
| medium | osv/GHSA-fxqj-rqcc-2cmp |
website/package-lock.json | [email protected] (npm) is affected by GHSA-fxqj-rqcc-2cmp | Dependencies (osv-scanner) |
| medium | osv/GHSA-gcqx-w48m-w2h4 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-gcqx-w48m-w2h4 | Dependencies (osv-scanner) |
| medium | osv/GHSA-h67p-54hq-rp68 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-h67p-54hq-rp68 | Dependencies (osv-scanner) |
| medium | osv/GHSA-h67p-54hq-rp68 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-h67p-54hq-rp68 | Dependencies (osv-scanner) |
| medium | osv/GHSA-hrr3-gc8f-f4qj |
website/package-lock.json | [email protected] (npm) is affected by GHSA-hrr3-gc8f-f4qj | Dependencies (osv-scanner) |
| medium | osv/GHSA-jr45-8vmc-qm54 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-jr45-8vmc-qm54 | Dependencies (osv-scanner) |
| medium | osv/GHSA-m28w-2pqf-7qgj |
website/package-lock.json | [email protected] (npm) is affected by GHSA-m28w-2pqf-7qgj | Dependencies (osv-scanner) |
| medium | osv/GHSA-m8rv-5g2x-5cg5 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-m8rv-5g2x-5cg5 | Dependencies (osv-scanner) |
| medium | osv/GHSA-mp7j-qc5w-4988 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-mp7j-qc5w-4988 | Dependencies (osv-scanner) |
| medium | osv/GHSA-mx8g-39q3-5c79 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-mx8g-39q3-5c79 | Dependencies (osv-scanner) |
| medium | osv/GHSA-p88m-4jfj-68fv |
website/package-lock.json | [email protected] (npm) is affected by GHSA-p88m-4jfj-68fv | Dependencies (osv-scanner) |
| medium | osv/GHSA-pmjh-fq2x-6v4x |
website/package-lock.json | [email protected] (npm) is affected by GHSA-pmjh-fq2x-6v4x | Dependencies (osv-scanner) |
| medium | osv/GHSA-pr7r-676h-xcf6 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-pr7r-676h-xcf6 | Dependencies (osv-scanner) |
| medium | osv/GHSA-q2hr-2g5m-vwhr |
website/package-lock.json | [email protected] (npm) is affected by GHSA-q2hr-2g5m-vwhr | Dependencies (osv-scanner) |
| medium | osv/GHSA-q7cg-457f-vx79 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-q7cg-457f-vx79 | Dependencies (osv-scanner) |
| medium | osv/GHSA-qj8w-gfj5-8c6v |
website/package-lock.json | [email protected] (npm) is affected by GHSA-qj8w-gfj5-8c6v | Dependencies (osv-scanner) |
| medium | osv/GHSA-r825-w8mm-5pxw |
website/package-lock.json | [email protected] (npm) is affected by GHSA-r825-w8mm-5pxw | Dependencies (osv-scanner) |
| medium | osv/GHSA-rj75-hqrm-r3gf |
website/package-lock.json | [email protected] (npm) is affected by GHSA-rj75-hqrm-r3gf | Dependencies (osv-scanner) |
| medium | osv/GHSA-rj75-hqrm-r3gf |
website/package-lock.json | [email protected] (npm) is affected by GHSA-rj75-hqrm-r3gf | Dependencies (osv-scanner) |
| medium | osv/GHSA-rx4f-c7p8-82vq |
website/package-lock.json | [email protected] (npm) is affected by GHSA-rx4f-c7p8-82vq | Dependencies (osv-scanner) |
| medium | osv/GHSA-v3r7-h72x-cjcm |
website/package-lock.json | [email protected] (npm) is affected by GHSA-v3r7-h72x-cjcm | Dependencies (osv-scanner) |
| medium | osv/GHSA-v6wh-96g9-6wx3 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-v6wh-96g9-6wx3 | Dependencies (osv-scanner) |
| medium | osv/GHSA-w5vr-8v7q-w6rv |
website/package-lock.json | [email protected] (npm) is affected by GHSA-w5vr-8v7q-w6rv | Dependencies (osv-scanner) |
| medium | osv/GHSA-w74x-v6f9-j3xg |
website/package-lock.json | [email protected] (npm) is affected by GHSA-w74x-v6f9-j3xg | Dependencies (osv-scanner) |
| medium | osv/GHSA-w9m9-85wc-3x92 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-w9m9-85wc-3x92 | Dependencies (osv-scanner) |
| medium | osv/GHSA-w9m9-85wc-3x92 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-w9m9-85wc-3x92 | Dependencies (osv-scanner) |
| medium | osv/GHSA-wr44-6hxh-3jwq |
website/package-lock.json | [email protected] (npm) is affected by GHSA-wr44-6hxh-3jwq | Dependencies (osv-scanner) |
| medium | osv/GHSA-x5fp-wj9c-mxmx |
website/package-lock.json | [email protected] (npm) is affected by GHSA-x5fp-wj9c-mxmx | Dependencies (osv-scanner) |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Clients/McpClientConfiguratorBase.cs:1025 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Clients/McpClientConfiguratorBase.cs:1196 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Clients/McpClientConfiguratorBase.cs:1207 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Clients/McpClientConfiguratorBase.cs:798 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Clients/McpClientConfiguratorBase.cs:808 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Clients/McpClientConfiguratorBase.cs:834 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Clients/McpClientConfiguratorBase.cs:923 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Clients/McpClientRegistry.cs:51 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Dependencies/DependencyManager.cs:74 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/AssetPathUtility.cs:137 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/AssetPathUtility.cs:142 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/AssetPathUtility.cs:191 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/AssetPathUtility.cs:200 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/AssetPathUtility.cs:224 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/AssetPathUtility.cs:45 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/AssetPathUtility.cs:597 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/AssetPathUtility.cs:602 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/AssetPathUtility.cs:629 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/ComponentOps.cs:1025 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/EditorWindowScreenshotUtility.cs:125 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/EditorWindowScreenshotUtility.cs:139 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/EditorWindowScreenshotUtility.cs:273 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/EditorWindowScreenshotUtility.cs:293 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/GameObjectLookup.cs:263 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/GameObjectSerializer.cs:386 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/GameObjectSerializer.cs:644 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/GameObjectSerializer.cs:738 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/GameObjectSerializer.cs:743 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/MaterialOps.cs:107 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/MaterialOps.cs:238 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/MaterialOps.cs:244 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/MaterialOps.cs:255 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/MaterialOps.cs:266 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/MaterialOps.cs:279 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/MaterialOps.cs:290 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/MaterialOps.cs:315 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/MaterialOps.cs:332 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/MaterialOps.cs:336 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/MaterialOps.cs:392 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/MaterialOps.cs:66 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/MaterialOps.cs:84 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/McpConfigurationHelper.cs:140 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/McpConfigurationHelper.cs:52 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/McpLogRecord.cs:88 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/ObjectResolver.cs:102 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/ObjectResolver.cs:194 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/ObjectResolver.cs:89 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/ObjectResolver.cs:96 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PortManager.cs:115 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PortManager.cs:119 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PortManager.cs:126 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PortManager.cs:242 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PortManager.cs:246 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PortManager.cs:278 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PortManager.cs:309 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PortManager.cs:63 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PrefabUtilityHelper.cs:101 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PrefabUtilityHelper.cs:149 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PrefabUtilityHelper.cs:31 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PrefabUtilityHelper.cs:69 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/ProjectIdentityUtility.cs:149 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PropertyConversion.cs:28 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PropertyConversion.cs:41 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/PropertyConversion.cs:86 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/RenderPipelineUtility.cs:188 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/RenderPipelineUtility.cs:192 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/RenderPipelineUtility.cs:198 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/RenderPipelineUtility.cs:202 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/RenderPipelineUtility.cs:208 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/RenderPipelineUtility.cs:349 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/RenderPipelineUtility.cs:434 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/RenderPipelineUtility.cs:87 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/RendererHelpers.cs:50 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/TelemetryHelper.cs:120 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/TelemetryHelper.cs:202 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/TelemetryHelper.cs:210 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/TextureOps.cs:115 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/TextureOps.cs:157 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/TextureOps.cs:19 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/TextureOps.cs:31 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/VectorParsing.cs:209 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/VectorParsing.cs:265 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/VectorParsing.cs:368 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/VectorParsing.cs:459 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/VectorParsing.cs:48 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/VectorParsing.cs:698 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/VectorParsing.cs:724 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Helpers/VectorParsing.cs:94 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/MenuItems/BlenderBridgeMenu.cs:59 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/MenuItems/BlenderBridgeMenu.cs:60 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Migrations/LegacyServerSrcMigration.cs:47 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Migrations/LegacyServerSrcMigration.cs:52 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Migrations/LegacyServerSrcMigration.cs:59 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Migrations/LegacyServerSrcMigration.cs:76 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Migrations/StdIoVersionMigration.cs:112 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Migrations/StdIoVersionMigration.cs:89 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Resources/Editor/Windows.cs:48 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Resources/MenuItems/GetMenuItems.cs:66 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Resources/Scene/CamerasResource.cs:22 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Resources/Scene/GameObjectResource.cs:203 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Resources/Scene/GameObjectResource.cs:280 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Resources/Scene/GameObjectResource.cs:62 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Resources/Scene/RendererFeaturesResource.cs:19 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Resources/Scene/RenderingStatsResource.cs:19 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Resources/Scene/VolumesResource.cs:19 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/AssetGen/FalModelCatalog.cs:342 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/AssetGen/OpenRouterModelCatalog.cs:166 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/BridgeControlService.cs:106 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/BridgeControlService.cs:112 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/BridgeControlService.cs:126 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/BridgeControlService.cs:94 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ClientConfigurationService.cs:112 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/EditorStateCache.cs:316 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpAutoStartHandler.cs:169 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpAutoStartHandler.cs:190 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpAutoStartHandler.cs:218 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpAutoStartHandler.cs:244 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpAutoStartHandler.cs:272 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpAutoStartHandler.cs:304 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpAutoStartHandler.cs:344 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpBridgeReloadHandler.cs:123 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpBridgeReloadHandler.cs:154 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpBridgeReloadHandler.cs:159 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpBridgeReloadHandler.cs:192 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpBridgeReloadHandler.cs:199 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpBridgeReloadHandler.cs:204 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpBridgeReloadHandler.cs:215 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/HttpBridgeReloadHandler.cs:68 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/McpEditorShutdownCleanup.cs:52 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/McpEditorShutdownCleanup.cs:66 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/PackageDeploymentService.cs:131 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/PackageDeploymentService.cs:170 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/PackageJobManager.cs:122 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/PackageJobManager.cs:143 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/PackageJobManager.cs:151 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/PackageJobManager.cs:161 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/PackageJobManager.cs:169 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/PackageJobManager.cs:175 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/PackageJobManager.cs:253 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/PackageUpdateService.cs:374 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/PackageUpdateService.cs:410 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/PathResolverService.cs:87 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ResourceDiscoveryService.cs:143 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ResourceDiscoveryService.cs:35 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ResourceDiscoveryService.cs:49 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/Server/ProcessDetector.cs:168 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/Server/ProcessTerminator.cs:84 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:163 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:187 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:371 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:668 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:681 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:708 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:714 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:756 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:764 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:793 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:819 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:828 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:847 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:856 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:863 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:870 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/ServerManagementService.cs:885 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/StartupConfigRewrite.cs:55 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/StartupConfigRewrite.cs:59 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/StdioBridgeReloadHandler.cs:108 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/StdioBridgeReloadHandler.cs:147 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/StdioBridgeReloadHandler.cs:152 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/StdioBridgeReloadHandler.cs:169 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/StdioBridgeReloadHandler.cs:177 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | opengrep/csharp.lang.best-practice.structured-logging |
MCPForUnity/Editor/Services/StdioBridgeReloadHandler.cs:87 | String interpolation in log message obscures the distinction between variables and the log message. Use structured logging instead, where the variables are passed as additional arguments and the interpolation is performed by the logging... | Lint |
| low | zizmor/artipacked |
.github/workflows/beta-release.yml:168 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| low | zizmor/self-repository |
.github/workflows/beta-release.yml:19 | use GitHub's dedicated self-repository syntax [confidence high] | CI workflows (zizmor) |
| low | zizmor/self-repository |
.github/workflows/beta-release.yml:25 | use GitHub's dedicated self-repository syntax [confidence high] | CI workflows (zizmor) |
| low | zizmor/artipacked |
.github/workflows/beta-release.yml:41 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| low | zizmor/self-repository |
.github/workflows/release.yml:24 | use GitHub's dedicated self-repository syntax [confidence high] | CI workflows (zizmor) |
| low | zizmor/self-repository |
.github/workflows/release.yml:31 | use GitHub's dedicated self-repository syntax [confidence high] | CI workflows (zizmor) |
| low | zizmor/artipacked |
.github/workflows/release.yml:326 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| low | zizmor/artipacked |
.github/workflows/release.yml:482 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| low | zizmor/self-repository |
.github/workflows/release.yml:489 | use GitHub's dedicated self-repository syntax [confidence high] | CI workflows (zizmor) |
| low | zizmor/artipacked |
.github/workflows/release.yml:512 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| low | zizmor/artipacked |
.github/workflows/release.yml:544 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| low | zizmor/artipacked |
.github/workflows/release.yml:56 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| low | gitleaks/generic-api-key |
Server/tests/integration/test_api_key_service.py:217 | Possible generic-api-key secret in the current tree (test/docs/example file) | Secrets (gitleaks) |
| low | osv/GHSA-5239-wwwm-4pmq |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-2987, GHSA-5239-wwwm-4pmq | Dependencies (osv-scanner) |
| low | osv/GHSA-6jv3-5f52-599m |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-3037, GHSA-6jv3-5f52-599m | Dependencies (osv-scanner) |
| low | osv/GHSA-fhv5-28vv-h8m8 |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-177, GHSA-fhv5-28vv-h8m8 | Dependencies (osv-scanner) |
| low | osv/GHSA-jj7h-c3hg-m23x |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-4354, GHSA-jj7h-c3hg-m23x | Dependencies (osv-scanner) |
| low | osv/GHSA-v9pg-7xvm-68hf |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-3040, GHSA-v9pg-7xvm-68hf | Dependencies (osv-scanner) |
| low | osv/GHSA-vffw-93wf-4j4q |
Server/uv.lock | [email protected] (PyPI) is affected by PYSEC-2026-3041, GHSA-vffw-93wf-4j4q | Dependencies (osv-scanner) |
| low | gitleaks/generic-api-key |
docs/superpowers/plans/2026-06-28-ai-asset-generation.md:1416 | Possible generic-api-key secret in history (commit d0a6ef01f5); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | osv/GHSA-2gqq-gqf2-x968 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-2gqq-gqf2-x968 | Dependencies (osv-scanner) |
| low | osv/GHSA-333x-w4r6-6crp |
website/package-lock.json | [email protected] (npm) is affected by GHSA-333x-w4r6-6crp | Dependencies (osv-scanner) |
| low | osv/GHSA-35p6-xmwp-9g52 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-35p6-xmwp-9g52 | Dependencies (osv-scanner) |
| low | osv/GHSA-4x5r-pxfx-6jf8 |
website/package-lock.json | @babel/[email protected] (npm) is affected by GHSA-4x5r-pxfx-6jf8 | Dependencies (osv-scanner) |
| low | osv/GHSA-6w3j-5fw6-r9vr |
website/package-lock.json | [email protected] (npm) is affected by GHSA-6w3j-5fw6-r9vr | Dependencies (osv-scanner) |
| low | osv/GHSA-8436-99hf-9mmv |
website/package-lock.json | [email protected] (npm) is affected by GHSA-8436-99hf-9mmv | Dependencies (osv-scanner) |
| low | osv/GHSA-g8m3-5g58-fq7m |
website/package-lock.json | [email protected] (npm) is affected by GHSA-g8m3-5g58-fq7m | Dependencies (osv-scanner) |
| low | osv/GHSA-gg4h-3hg2-grpc |
website/package-lock.json | [email protected] (npm) is affected by GHSA-gg4h-3hg2-grpc | Dependencies (osv-scanner) |
| low | osv/GHSA-m5mm-p8h7-m29v |
website/package-lock.json | [email protected] (npm) is affected by GHSA-m5mm-p8h7-m29v | Dependencies (osv-scanner) |
| low | osv/GHSA-r53p-7pc4-xj5r |
website/package-lock.json | [email protected] (npm) is affected by GHSA-r53p-7pc4-xj5r | Dependencies (osv-scanner) |
| low | osv/GHSA-v422-hmwv-36x6 |
website/package-lock.json | [email protected] (npm) is affected by GHSA-v422-hmwv-36x6 | Dependencies (osv-scanner) |
| low | osv/GHSA-xhq7-xmqj-769h |
website/package-lock.json | [email protected] (npm) is affected by GHSA-xhq7-xmqj-769h | Dependencies (osv-scanner) |
| info | zizmor/template-injection |
.github/workflows/claude-nl-suite.yml:152 | code injection via template expansion [confidence low] | CI workflows (zizmor) |
| info | zizmor/template-injection |
.github/workflows/compile-check.yml:101 | code injection via template expansion [confidence low] | CI workflows (zizmor) |
| info | zizmor/template-injection |
.github/workflows/compile-check.yml:110 | code injection via template expansion [confidence low] | CI workflows (zizmor) |
| info | zizmor/template-injection |
.github/workflows/compile-check.yml:86 | code injection via template expansion [confidence low] | CI workflows (zizmor) |
| info | zizmor/template-injection |
.github/workflows/compile-check.yml:90 | code injection via template expansion [confidence low] | CI workflows (zizmor) |
| info | zizmor/template-injection |
.github/workflows/compile-check.yml:96 | code injection via template expansion [confidence low] | CI workflows (zizmor) |
| info | zizmor/superfluous-actions |
.github/workflows/release.yml:311 | action functionality is already included by the runner [confidence high] | CI workflows (zizmor) |
| info | zizmor/superfluous-actions |
.github/workflows/release.yml:571 | action functionality is already included by the runner [confidence high] | CI workflows (zizmor) |
Tools and coverage
Every analyzer that ran on this commit. A failed or skipped tool is a coverage gap: its share of the score is left out and the coverage figure drops.
| Analyzer | Pillar | Status | Version | Findings | Note |
|---|---|---|---|---|---|
| AI tool configuration | AI provenance | ok | signatures-v1 | 0 | |
| Explicit AI attribution | AI provenance | ok | signatures-v1 | 0 | |
| Release velocity | AI provenance | ok | prov-5 | 0 | |
| Coding style | AI provenance | ok | — | 0 | |
| Commit velocity | AI provenance | ok | prov-5 | 0 | |
| Findings in AI-written lines | AI provenance | ok | git-blame | 0 | |
| Complexity (lizard) | Code quality | ok | lizard 1.25.1 | 0 | |
| Documentation | Code quality | ok | — | 0 | |
| Duplication (jscpd) | Code quality | ok | repotrust-dup-w6 | 0 | |
| Lint | Code quality | ok | opengrep 1.33.1; rules f1d2b562b414 | 200 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | ok | — | 0 | |
| CI workflows (zizmor) | Security | ok | zizmor 1.32.0 | 94 | |
| Dependencies (osv-scanner) | Security | ok | osv-scanner version: 2.7.1 | 193 | |
| Release downloads | Security | ok | — | 0 | |
| Security posture | Security | ok | — | 0 | |
| Package registries | Security | ok | — | 0 | |
| Static analysis (opengrep) | Security | ok | opengrep 1.33.1; rules f1d2b562b414 | 32 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 2 |
Score history
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 5914ce5bd9d1 | prov-5+qual-2+sec-2 | 22% | 70 | 52 |
Full text report
- Repository: https://github.com/CoplayDev/unity-mcp
- Commit:
5914ce5bd9d11d66a7896ce72e395b0a2f049c2a - Generated: 2026-11-14T15:20:15+00:00
- Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2
Scores
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 22 | explicit | 95% | 100% |
| Code quality | 70 | adequate | 90% | 100% |
| Security | 52 | weak | 85% | 100% |
AI provenance
Explicit AI attribution on 22% of first-party code added; an estimated 22% including velocity signals.
- Explicitly attributed share (lower bound): 21.8%
- Unattributed share in AI-consistent velocity bursts: 11.5%
- Estimated AI-generated share: 21.8%
| AI tool | Attributed commits | Lines added |
|---|---|---|
| Claude Code | 203 | 61,568 |
| OpenAI Codex | 39 | 7,673 |
| GitHub Copilot coding agent | 5 | 8,725 |
| Cursor agent | 1 | 16 |
- AI tooling configured in repo: claude-code
Current source lines last changed by AI-attributed commits: 33,199 of 152,717.
| Findings per 1,000 lines | AI-attributed | Other | Ratio |
|---|---|---|---|
| Quality | 0.663 | 1.489 | 0.45x |
| Security | 0.181 | 0.201 | 0.9x |
- Stylometry index: 0.30 per 1,000 lines (narrated steps 38, placeholders 0, assistant phrasing 0, emoji 15). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2025-12 | 9,524 | 2% |
| 2026-01 | 84,418 | 28% |
| 2026-02 | 20,959 | 70% |
| 2026-03 | 39,831 | 18% |
| 2026-04 | 3,431 | 45% |
| 2026-05 | 5,463 | 8% |
| 2026-06 | 12,747 | 67% |
| 2026-07 | 5,976 | 52% |
| 2026-08 | 6,687 | 1% |
| 2026-09 | 7,696 | 24% |
| 2026-10 | 6,923 | 52% |
| 2026-11 | 32 | 0% |
Evidence
- OpenAI Codex: on merged branch (88f1e4db73) (5a013ad824d3)
- OpenAI Codex: on merged branch (ff7f6d3db6) (2c109c8277cd)
- OpenAI Codex: on merged branch (ff7f6d3db6) (d173c5ef0a87)
- OpenAI Codex: on merged branch (ff7f6d3db6) (9b9393e12388)
- OpenAI Codex: on merged branch (ff7f6d3db6) (93bd97408812)
- OpenAI Codex: on merged branch (ff7f6d3db6) (2b8d046f6199)
- OpenAI Codex: on merged branch (ff7f6d3db6) (e34b2c8a58df)
- OpenAI Codex: on merged branch (ff7f6d3db6) (837f2d131584)
- OpenAI Codex: on merged branch (6abce3e0f5) (0abe62dffc3b)
- OpenAI Codex: on merged branch (6abce3e0f5) (b7a2f5a0b807)
- OpenAI Codex: on merged branch (6abce3e0f5) (b128e61f69ec)
- OpenAI Codex: on merged branch (6abce3e0f5) (5fcd6711e628)
- OpenAI Codex: on merged branch (6abce3e0f5) (5fb770362036)
- OpenAI Codex: on merged branch (6abce3e0f5) (f11fc1d2c6c6)
- OpenAI Codex: on merged branch (6abce3e0f5) (a1ae80ae88d2)
AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.
Code quality
Code quality is adequate: test-to-source ratio 0.40, CI runs tests; 27% of function code in complex or long functions; 5% duplicated lines. Weakest area: type safety.
| Area | Score |
|---|---|
| Complexity (lizard) | 44 |
| Duplication | 74 |
| Code smells (Opengrep) | 77 |
| Tests and CI | 95 |
| Documentation | 80 |
| Type safety | 0 |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 5,663; mean complexity 4.7, 90th percentile 11; 303 complex and 102 long functions
- Duplicated lines: 5.0% of 96,587 compared
- Tests: 61,242 test lines for 152,717 source lines (ratio 0.40); CI test commands: pytest; 73% of recent source commits also change tests
- Docs missing or thin: changelog
Most complex functions:
- ManageProBuilder::CreateShapeViaGenerator in MCPForUnity/Editor/Tools/ProBuilder/ManageProBuilder.cs: complexity 203, 186 lines
- script_apply_edits in Server/src/services/tools/script_apply_edits.py: complexity 173, 438 lines
- _iter_csharp_tokens in Server/src/services/tools/script_apply_edits.py: complexity 135, 304 lines
- FalModelSchema::Parse in MCPForUnity/Editor/Services/AssetGen/FalModelSchema.cs: complexity 126, 109 lines
- ManageScript::EditScript in MCPForUnity/Editor/Tools/ManageScript.cs: complexity 121, 412 lines
Security
Security posture is weak: 193 known vulnerabilities in 52 dependencies; 14 high-severity SAST findings; 59 high-severity workflow issues. Weakest area: ci actions.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 94 |
| Static analysis (Opengrep) | 95 |
| Vulnerable dependencies (OSV) | 0 |
| CI workflows (zizmor) | 0 |
| Posture (policy, updates, signing, lockfiles) | 40 |
| OpenSSF Scorecard | n/a |
-
Known vulnerabilities: 193 in 52 packages (critical 15, high 83, medium 77, low 18)
-
Posture checks passed: security policy; missing: dependency updates, signed commits, lockfiles
Top findings
| Severity | Finding | Location |
|---|---|---|
| critical | osv/GHSA-82r6-8w77-94w6: [email protected] (PyPI) is affected by PYSEC-2026-4025, GHSA-82r6-8w77-94w6 |
Server/uv.lock |
| critical | osv/GHSA-7wc2-qxgw-g8gg: [email protected] (PyPI) is affected by PYSEC-2026-2118, GHSA-7wc2-qxgw-g8gg |
Server/uv.lock |
| critical | osv/GHSA-wvwj-cvrp-7pv5: [email protected] (PyPI) is affected by PYSEC-2026-287, GHSA-wvwj-cvrp-7pv5 |
Server/uv.lock |
| critical | osv/GHSA-7vr2-2fgp-9w7p: [email protected] (PyPI) is affected by PYSEC-2026-4355, GHSA-7vr2-2fgp-9w7p |
Server/uv.lock |
| critical | osv/GHSA-8m4g-j4wp-wgcg: [email protected] (PyPI) is affected by PYSEC-2026-4356, GHSA-8m4g-j4wp-wgcg |
Server/uv.lock |
| critical | osv/GHSA-6v38-4h7w-rj9h: [email protected] (PyPI) is affected by GHSA-6v38-4h7w-rj9h |
Server/uv.lock |
| critical | osv/GHSA-6q48-6c7w-9gw2: [email protected] (PyPI) is affected by PYSEC-2026-4320, GHSA-6q48-6c7w-9gw2 |
Server/uv.lock |
| critical | osv/GHSA-p423-j2cm-9vmq: [email protected] (PyPI) is affected by PYSEC-2026-36, GHSA-p423-j2cm-9vmq |
Server/uv.lock |
| critical | osv/GHSA-vv7q-7jx5-f767: [email protected] (PyPI) is affected by PYSEC-2026-338, GHSA-vv7q-7jx5-f767 |
Server/uv.lock |
| critical | osv/GHSA-ffc3-869f-jxw9: [email protected] (PyPI) is affected by PYSEC-2026-4145, GHSA-ffc3-869f-jxw9 |
Server/uv.lock |
| critical | osv/GHSA-jqcg-44mw-7w3h: [email protected] (npm) is affected by GHSA-jqcg-44mw-7w3h |
website/package-lock.json |
| critical | osv/GHSA-pqg4-j6r4-53mv: [email protected] (npm) is affected by GHSA-pqg4-j6r4-53mv |
website/package-lock.json |
| critical | osv/GHSA-5gmw-xhrv-c9v3: [email protected] (npm) is affected by GHSA-5gmw-xhrv-c9v3 |
website/package-lock.json |
| critical | osv/GHSA-85c8-ppgw-ccpr: [email protected] (npm) is affected by GHSA-85c8-ppgw-ccpr |
website/package-lock.json |
| critical | osv/GHSA-xv26-6w52-cph6: [email protected] (npm) is affected by GHSA-xv26-6w52-cph6 |
website/package-lock.json |
| high | opengrep/python.lang.security.use-defused-xml: The Python documentation recommends using defusedxml instead of xml because the native Python xml library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause denial of service. [confidence low] |
.github/scripts/mark_skipped.py:15 |
| high | opengrep/python.lang.security.use-defused-xml-parse: The native Python xml library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause denial of service. Do not use this library to parse untrusted input. Instead the Python documentation recommends using defusedxml. [confidence medium] |
.github/scripts/mark_skipped.py:65 |
| high | opengrep/dockerfile.security.missing-user-entrypoint: By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile is a USER other than 'root'. [confidence medium] |
Server/Dockerfile:35 |
| high | opengrep/dockerfile.security.missing-user: By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile is a USER other than 'root'. [confidence medium] |
Server/Dockerfile:36 |
| high | opengrep/python.lang.security.use-defused-xml: The Python documentation recommends using defusedxml instead of xml because the native Python xml library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause denial of service. [confidence low] |
tools/check_unity_test_results.py:6 |
| high | opengrep/python.lang.security.use-defused-xml-parse: The native Python xml library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause denial of service. Do not use this library to parse untrusted input. Instead the Python documentation recommends using defusedxml. [confidence medium] |
tools/check_unity_test_results.py:22 |
| high | opengrep/python.lang.security.use-defused-xml: The Python documentation recommends using defusedxml instead of xml because the native Python xml library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause denial of service. [confidence low] |
tools/ci_unity_license.py:17 |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] |
tools/ci_unity_license.py:123 |
| high | opengrep/python.lang.security.use-defused-xml: The Python documentation recommends using defusedxml instead of xml because the native Python xml library is vulnerable to XML External Entity (XXE) attacks. These attacks can leak confidential data and "XML bombs" can cause denial of service. [confidence low] |
tools/local_harness.py:71 |
| high | opengrep/python.lang.security.audit.dangerous-subprocess-use-audit: Detected subprocess function 'Popen' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. [confidence low] |
tools/local_harness.py:796 |
Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.
Repository profile
- Source lines: 152,717; test lines: 61,242
| Language | Lines |
|---|---|
| C# | 148,922 |
| Python | 63,037 |
| JavaScript | 1,069 |
| Shell | 692 |
| PowerShell | 239 |