RepoTrust

Leaderboard github.com

Snipeon/Logitech-battery-widget

Fully vibe coded. Fully lazy me. Still works. Cuz I audited the code.

  • View repository ↗
  • Rust
  • ★ 0
  • commit 9c8aea6ee066
  • scored 2026-11-14
  • scoring prov-5+qual-2+sec-2

AI provenance

0%

none-detected

Confidence
45%
Coverage
100%

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

Code quality

55/100

weak

Confidence
90%
Coverage
100%

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

Security

77/100

adequate

Confidence
85%
Coverage
100%

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

AI provenance

0% none-detected

No AI attribution or AI-consistent velocity signals detected.

How the score is built

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

Lines added per month all AI-attributed share

  1. 2026-101,136 · 0% AI

Evidence by analyzer

Explicit AI attributionok
attributed_commit_share
0.0%
attributed_commits
0
attributed_loc
0
attributed_loc_share
0.0%
commits
18
effective_loc
1,136
tools_detected
0
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
270.94
measured_loc
1,136
median_loc_per_hour
270.94
pr_timed_units
0
pre_ai_era_burst_loc
0
pre_ai_era_bursts
0
pre_ai_era_measured_loc
0
work_units
2
Release velocityskipped
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
1,135
per_kloc:assistant_voice
0
per_kloc:emoji_in_code
0
per_kloc:narrated_steps
0
per_kloc:placeholder
0

Code quality

55 weak

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

How the score is built

  • Complexity64
  • Duplication100
  • Lint and smells100
  • Tests and CI0
  • Documentation40
  • Type safetynot measured
  • Review processnot measured

Evidence by analyzer

Complexity (lizard)ok2 items
complex_functions
2
function_nloc
819
functions
36
long_functions
0
many_param_functions
1
mean_ccn
5.97
p90_ccn
11
risky_nloc_share
15.0%
Duplication (jscpd)ok
compared_lines
883
duplicated_lines
0
duplicated_share
0.0%
files
2
Lintok
findings
0
scanned_lines
992
weighted_findings
0
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
3
cochange_share
0.0%
source_lines
1,135
test_lines
0
test_ratio
0
Documentationok1 item
  • README.md README.md
check:changelog
no
check:contributing
no
check:license
no
check:readme
yes
readme_lines
50
Type safetyskipped

Security

77 adequate

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

How the score is built

  • Secrets100
  • Static analysis (SAST)77
  • Vulnerable dependenciesnot measured
  • CI workflowsnot measured
  • Security posture20
  • 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
3
findings_high
0
findings_low
3
findings_medium
0
parse_errors
0
scanned_lines
992
weighted_findings
0.75
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok
check:dependency_updates
no
check:lockfiles
yes
check:security_policy
no
check:signed_commits
yes
signed_commit_share
100.0%
unpinned_manifests
0
Release downloadsok
binary_assets
0
signals
0
suspicious
0

Findings

3 low

SeverityRuleLocationMessageTool
low opengrep/rust.lang.security.unsafe-usage @Resources/main.rs:483 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)
low opengrep/rust.lang.security.current-exe @Resources/main.rs:61 current_exe should not be used for security operations. From the docs: "The output of this function should not be trusted for anything that might have security implications. Basically, if users can run the executable, they can change... Static analysis (opengrep)
low opengrep/rust.lang.security.unsafe-usage @Resources/main.rs:971 Detected 'unsafe' usage, please audit for secure usage [confidence high] Static analysis (opengrep)

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 provenanceskipped—0
Coding styleAI provenanceok—0
Commit velocityAI provenanceokprov-40
Complexity (lizard)Code qualityoklizard 1.25.10
DocumentationCode qualityok—0
Duplication (jscpd)Code qualityokrepotrust-dup-w60
LintCode qualityokopengrep 1.33.1; rules f1d2b562b4140
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 f1d2b562b4143
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-149c8aea6ee066prov-5+qual-2+sec-20%5577
2026-11-149c8aea6ee066prov-4+qual-2+sec-20%5577

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/Snipeon/Logitech-battery-widget/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/Snipeon/Logitech-battery-widget/)
[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/Snipeon/Logitech-battery-widget/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/Snipeon/Logitech-battery-widget/)
[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/Snipeon/Logitech-battery-widget/security.svg)](https://repotrust.synapticcyber.com/r/github.com/Snipeon/Logitech-battery-widget/)
Full text report

Scores

Pillar Score Signal Confidence Coverage
AI provenance (estimated AI-generated share) 0 none-detected 45% 100%
Code quality 55 weak 90% 100%
Security 77 adequate 85% 100%

AI provenance

No AI attribution or AI-consistent velocity signals detected.

  • Explicitly attributed share (lower bound): 0.0%
  • Unattributed share in AI-consistent velocity bursts: 0.0%
  • Estimated AI-generated share: 0.0%
Month Lines added Attributed to AI
2026-10 1,136 0%

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

Area Score
Complexity (lizard) 64
Duplication 100
Code smells (Opengrep) 100
Tests and CI 0
Documentation 40
Type safety n/a
Process (Scorecard review/maintenance) n/a
  • Functions: 36; mean complexity 6.0, 90th percentile 11; 2 complex and 0 long functions
  • Duplicated lines: 0.0% of 883 compared
  • Tests: 0 test lines for 1,135 source lines (ratio 0.00); CI test commands: none detected; 0% of recent source commits also change tests
  • Docs missing or thin: license, 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) 77
Vulnerable dependencies (OSV) n/a
CI workflows (zizmor) n/a
Posture (policy, updates, signing, lockfiles) 20
OpenSSF Scorecard n/a
  • Posture checks passed: signed commits, lockfiles; missing: security policy, dependency updates

Top findings

Severity Finding Location
low opengrep/rust.lang.security.current-exe: current_exe should not be used for security operations. From the docs: "The output of this function should not be trusted for anything that might have security implications. Basically, if users can run the executable, they can change the output arbitrarily." [confidence high] @Resources/main.rs:61
low opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] @Resources/main.rs:483
low opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] @Resources/main.rs:971

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: 1,135; test lines: 0
Language Lines
Rust 992
Lua 143