RepoTrust

Leaderboard github.com

Morveus/everquest-spell-keys

Your EverQuest spell gems live on your keys — plugins for Logitech MX Creative Console and Elgato Stream Deck

  • View repository ↗
  • C#
  • ★ 0
  • commit 0c89d6e00c20
  • scored 2026-11-14
  • scoring prov-5+qual-2+sec-2

unreviewed-ai-risk

AI provenance

100%

explicit

Confidence
79%
Coverage
100%

Estimated share of AI-generated code. Explicit attribution is a lower bound.

Code quality

47/100

poor

Confidence
90%
Coverage
100%

Complexity, duplication, lint density, tests, CI, docs and review process.

Security

82/100

adequate

Confidence
85%
Coverage
100%

Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.

AI provenance

100% explicit

Explicit AI attribution on 100% of first-party code added; an estimated 100% including velocity signals.

How the score is built

  • Explicitly attributed share100%
  • Unattributed share in AI-pace bursts0%
  • Estimated AI-generated share100%
  • AI tool configuration files0
  • Work sessions at AI pace0
  • Releases at AI pace0
  • Coding-style index (1.0+ means possible)0.00

Attributed AI tools

ToolCommitsLines addedFirst seenLast seen
Claude Code354,5412026-08-022026-08-13

Lines added per month all AI-attributed share

  1. 2026-084,541 · 100% AI

Findings in AI-attributed lines vs the rest

From git blame: 3,242 lines trace to AI-attributed commits, 0 to others. Too few lines in one group for a fair comparison. Reported, not scored.

Findings per 1,000 linesAI-attributedOtherRatio
Code quality5.86——
Security0.00——

Evidence by analyzer

Explicit AI attributionok26 items
attributed_commit_share
97.2%
attributed_commits
35
attributed_loc
4,541
attributed_loc_share
100.0%
commits
36
effective_loc
4,541
tools_detected
1
AI tool configurationok
artifacts
0
tools_configured
0
workflow_agents
0
Commit velocityok
excluded_import_loc
0
flagged_loc
0
flagged_loc_share
0.0%
flagged_units
0
max_loc_per_hour
390.28
measured_loc
4,541
median_loc_per_hour
294.10
pr_timed_units
0
pre_ai_era_burst_loc
0
pre_ai_era_bursts
0
pre_ai_era_measured_loc
0
work_units
10
Release velocityok
flagged_releases
0
max_loc_per_day
429.30
releases
1
Coding styleok
count:assistant_voice
0
count:emoji_in_code
0
count:narrated_steps
0
count:placeholder
0
files:assistant_voice
0
files:emoji_in_code
0
files:narrated_steps
0
files:placeholder
0
index
0
lines_scanned
3,242
per_kloc:assistant_voice
0
per_kloc:emoji_in_code
0
per_kloc:narrated_steps
0
per_kloc:placeholder
0
Findings in AI-written linesok
ai_lines
3,242
blame_failures
0
files_blamed
18
other_lines
0
quality:ai_findings
19
quality:ai_per_kloc
5.86
quality:other_findings
0
security:ai_findings
0
security:ai_per_kloc
0
security:other_findings
0

Code quality

47 poor

Code quality is poor: test-to-source ratio 0.00, no CI test run detected; 30% of function code in complex or long functions; 1% duplicated lines. Weakest area: testing.

How the score is built

  • Complexity41
  • Duplication97
  • Lint and smells69
  • Tests and CI0
  • Documentation65
  • Type safetynot measured
  • Review processnot measured

Evidence by analyzer

Complexity (lizard)ok9 items
complex_functions
9
function_nloc
2,136
functions
123
long_functions
1
many_param_functions
2
mean_ccn
5.07
p90_ccn
13
risky_nloc_share
29.7%
Duplication (jscpd)ok1 item
compared_lines
2,069
duplicated_lines
12
duplicated_share
0.6%
files
18
Lintok
category:best-practice
19
findings
19
scanned_lines
3,242
weighted_findings
4.75
Tests and CIok
check:ci_present
no
check:ci_runs_lint
no
check:ci_runs_tests
no
check:has_tests
no
check:test_ratio
no
check:tests_cochange
no
ci_files
0
cochange_commits
28
cochange_share
0.0%
source_lines
3,242
test_lines
0
test_ratio
0
Documentationok2 items
  • README.md README.md
  • LICENSE LICENSE
check:changelog
no
check:contributing
no
check:license
yes
check:readme
yes
readme_lines
152
Type safetyskipped

Security

82 adequate

Security posture is adequate: no high-impact findings. Weakest area: posture.

How the score is built

  • Secrets100
  • Static analysis (SAST)100
  • Vulnerable dependenciesnot measured
  • CI workflowsnot measured
  • Security posture0
  • OpenSSF Scorecardnot measured

Evidence by analyzer

OpenSSF Scorecardskipped

no published OpenSSF Scorecard result for this repo

Package registriesskipped

no registry dependencies declared

Secrets (gitleaks)ok
secrets_current
0
secrets_history
0
secrets_low_confidence
0
secrets_nonprod
0
Static analysis (opengrep)ok
findings
0
findings_high
0
findings_low
0
findings_medium
0
parse_errors
0
scanned_lines
3,242
weighted_findings
0
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok
check:dependency_updates
no
check:lockfiles
yes
check:security_policy
no
check:signed_commits
no
signed_commit_share
0.0%
unpinned_manifests
0
Release downloadsok2 items
binary_assets
2
signals
1
suspicious
0

Findings

19 low

SeverityRuleLocationMessageTool
low opengrep/csharp.lang.best-practice.structured-logging core/IconUpdater.cs:148 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 core/IconUpdater.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 core/IconUpdater.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 core/SpellBarReader.cs:1005 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 core/SpellBarReader.cs:1017 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 core/SpellBarReader.cs:1039 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 core/SpellBarReader.cs:1206 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 core/SpellBarReader.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 core/SpellBarReader.cs:286 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 core/SpellBarReader.cs:362 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 core/SpellBarReader.cs:610 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 core/SpellBarReader.cs:838 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 core/SpellBarReader.cs:846 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 core/SpellBarReader.cs:889 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 plugin/EverQuestPlugin/EverQuestPlugin.cs:40 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 streamdeck/EverQuestStreamDeck/Program.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 streamdeck/EverQuestStreamDeck/Program.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 streamdeck/EverQuestStreamDeck/SpellKeys.cs:64 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 streamdeck/EverQuestStreamDeck/SpellKeys.cs:70 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

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.

AnalyzerPillarStatusVersionFindingsNote
AI tool configurationAI provenanceoksignatures-v10
Explicit AI attributionAI provenanceoksignatures-v10
Release velocityAI provenanceokprov-40
Coding styleAI provenanceok—0
Commit velocityAI provenanceokprov-40
Findings in AI-written linesAI provenanceokgit-blame0
Complexity (lizard)Code qualityoklizard 1.25.10
DocumentationCode qualityok—0
Duplication (jscpd)Code qualityokrepotrust-dup-w60
LintCode qualityokopengrep 1.33.1; rules f1d2b562b41419
Tests and CICode qualityok—0
Type safetyCode qualityskipped—0
CI workflows (zizmor)Securityskipped—0
Dependencies (osv-scanner)Securityskipped—0
Release downloadsSecurityok—0
Security postureSecurityok—0
Package registriesSecurityskipped—0no registry dependencies declared
Static analysis (opengrep)Securityokopengrep 1.33.1; rules f1d2b562b4140
OpenSSF ScorecardSecurityskipped—0no published OpenSSF Scorecard result for this repo
Secrets (gitleaks)Securityokgitleaks 8.30.10

Score history

Scores from different scoring versions aren't directly comparable.

ScoredCommitScoringAI provenanceQualitySecurity
2026-11-140c89d6e00c20prov-5+qual-2+sec-2100%4782
2026-11-140c89d6e00c20prov-4+qual-2+sec-2100%4782

Embed a badge

Maintainers can show these in a README. Badges update when the repository is re-scored.

[![RepoTrust ai](https://repotrust.synapticcyber.com/badge/github.com/Morveus/everquest-spell-keys/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/Morveus/everquest-spell-keys/)
[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/Morveus/everquest-spell-keys/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/Morveus/everquest-spell-keys/)
[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/Morveus/everquest-spell-keys/security.svg)](https://repotrust.synapticcyber.com/r/github.com/Morveus/everquest-spell-keys/)
Full text report

Scores

Unreviewed AI code risk: a large share of this code is explicitly AI-attributed, and its tests or review process are weak while quality or security scores are low.

Pillar Score Signal Confidence Coverage
AI provenance (estimated AI-generated share) 100 explicit 79% 100%
Code quality 47 poor 90% 100%
Security 82 adequate 85% 100%

AI provenance

Explicit AI attribution on 100% of first-party code added; an estimated 100% including velocity signals.

  • Explicitly attributed share (lower bound): 100.0%
  • Unattributed share in AI-consistent velocity bursts: 0.0%
  • Estimated AI-generated share: 100.0%
AI tool Attributed commits Lines added
Claude Code 35 4,541

Current source lines last changed by AI-attributed commits: 3,242 of 3,242.

Too few lines in one group to compare finding densities.

Month Lines added Attributed to AI
2026-08 4,541 100%

Evidence

  • Claude Code: trailer 'Co-Authored-By: Claude' (0c89d6e00c20)
  • Claude Code: trailer 'Co-Authored-By: Claude' (8c99894da42d)
  • Claude Code: trailer 'Co-Authored-By: Claude' (278d059be691)
  • Claude Code: trailer 'Co-Authored-By: Claude' (25b0dea8c195)
  • Claude Code: trailer 'Co-Authored-By: Claude' (3af4fbb33214)
  • Claude Code: trailer 'Co-Authored-By: Claude' (b8edeed779ba)
  • Claude Code: trailer 'Co-Authored-By: Claude' (08d9b42b2ded)
  • Claude Code: trailer 'Co-Authored-By: Claude' (738f8160e477)
  • Claude Code: trailer 'Co-Authored-By: Claude' (5329e9af8eb9)
  • Claude Code: trailer 'Co-Authored-By: Claude' (35827c8caaf4)
  • Claude Code: trailer 'Co-Authored-By: Claude' (2c5bb8a98cd5)
  • Claude Code: trailer 'Co-Authored-By: Claude' (58433da983e4)
  • Claude Code: trailer 'Co-Authored-By: Claude' (097c0092be0e)
  • Claude Code: trailer 'Co-Authored-By: Claude' (a1f490d2bfbc)
  • Claude Code: trailer 'Co-Authored-By: Claude' (3bb5437f3f6b)

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 poor: test-to-source ratio 0.00, no CI test run detected; 30% of function code in complex or long functions; 1% duplicated lines. Weakest area: testing.

Area Score
Complexity (lizard) 41
Duplication 97
Code smells (Opengrep) 69
Tests and CI 0
Documentation 65
Type safety n/a
Process (Scorecard review/maintenance) n/a
  • Functions: 123; mean complexity 5.1, 90th percentile 13; 9 complex and 1 long functions
  • Duplicated lines: 0.6% of 2,069 compared
  • Tests: 0 test lines for 3,242 source lines (ratio 0.00); CI test commands: none detected; 0% of recent source commits also change tests
  • Docs missing or thin: contributing, changelog

Most complex functions:

Security

Security posture is adequate: no high-impact findings. Weakest area: posture.

Area Score
Secrets (gitleaks, tree + history) 100
Static analysis (Opengrep) 100
Vulnerable dependencies (OSV) n/a
CI workflows (zizmor) n/a
Posture (policy, updates, signing, lockfiles) 0
OpenSSF Scorecard n/a
  • Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits

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.

Distribution signals

Signals consistent with a repository that exists to distribute a download. They are heuristics, not a verdict; release files were not downloaded or inspected.

Repository profile

  • Source lines: 3,242; test lines: 0
Language Lines
C# 3,242