Leaderboard github.com
Fabian2000/pc_watcher
Windows tool for monitoring window focus events with GUI, tray icon, and detailed process hierarchy
AI provenance
0%
possible
- Confidence
- 41%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
49/100
poor
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
66/100
weak
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
0% possible
Weak signals consistent with AI-assisted development.
How the score is built
- Explicitly attributed share0%
- Unattributed share in AI-pace bursts0%
- Estimated AI-generated share0%
- AI tool configuration files1
- 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
- 2025-123,339 · 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
- 3
- effective_loc
- 3,339
- tools_detected
- 0
AI tool configurationok1 item
- artifacts
- 1
- earliest_adoption
- 2025-12-14
- tools_configured
- 1
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 3,339
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 0
- measured_loc
- 0
- median_loc_per_hour
- 0
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 0
- work_units
- 0
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
- 3,339
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0
- per_kloc:placeholder
- 0
Code quality
49 poor
Code quality is poor: test-to-source ratio 0.00, no CI test run detected; 26% of function code in complex or long functions; 5% duplicated lines. Weakest area: testing.
How the score is built
- Complexity46
- Duplication73
- Lint and smells100
- Tests and CI0
- Documentation65
- Type safetynot measured
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok5 items
- window_proc in src/alert_window.rs: complexity 60, 230 lines
- event_worker in src/event_hook.rs: complexity 21, 81 lines
- win_event_proc in src/event_hook.rs: complexity 20, 39 lines
- details_window_proc in src/alert_window.rs: complexity 19, 113 lines
- set_hooks in src/event_hook.rs: complexity 9, 116 lines
- complex_functions
- 4
- function_nloc
- 2,235
- functions
- 79
- long_functions
- 3
- many_param_functions
- 0
- mean_ccn
- 5.65
- p90_ccn
- 14
- risky_nloc_share
- 25.9%
Duplication (jscpd)ok4 items
- 6+ duplicated lines: src/alert_window.rs:434 and src/tray.rs:78
- 6+ duplicated lines: src/alert_window.rs:610 and src/alert_window.rs:690
- 6+ duplicated lines: src/logger.rs:69 and src/process_info.rs:26
- 6+ duplicated lines: src/process_info.rs:192 and src/process_info.rs:224
- compared_lines
- 2,325
- duplicated_lines
- 120
- duplicated_share
- 5.2%
- files
- 9
Lintok
- findings
- 0
- scanned_lines
- 3,339
- 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
- 1
- cochange_share
- 0.0%
- source_lines
- 3,339
- 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
- 83
Type safetyskipped
Security
66 weak
Security posture is weak: 4 known vulnerabilities in 4 dependencies. Weakest area: posture.
How the score is built
- Secrets100
- Static analysis (SAST)41
- Vulnerable dependencies82
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesok
- checked
- 19
- declared
- 19
- lookup_errors
- 0
- missing
- 0
- recent
- 0
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 0
- secrets_nonprod
- 0
Static analysis (opengrep)ok
- findings
- 34
- findings_high
- 0
- findings_low
- 34
- findings_medium
- 0
- parse_errors
- 0
- scanned_lines
- 3,339
- weighted_findings
- 8.50
Dependencies (osv-scanner)ok
- penalty
- 12
- vulnerabilities
- 4
- vulnerable_packages
- 4
- vulns_critical
- 0
- vulns_high
- 0
- vulns_low
- 0
- vulns_medium
- 2
- vulns_unknown
- 2
CI workflows (zizmor)skipped
Security postureok
- check:dependency_updates
- no
- check:lockfiles
- yes
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 33.3%
- unpinned_manifests
- 0
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
4 medium34 low
38 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| medium | osv/GHSA-434x-w66g-qw3r |
Cargo.lock | [email protected] (crates.io) is affected by RUSTSEC-2026-0007, GHSA-434x-w66g-qw3r | Dependencies (osv-scanner) |
| medium | osv/GHSA-r6v5-fh4h-64xc |
Cargo.lock | [email protected] (crates.io) is affected by RUSTSEC-2026-0009, GHSA-r6v5-fh4h-64xc | Dependencies (osv-scanner) |
| medium | osv/RUSTSEC-2026-0190 |
Cargo.lock | [email protected] (crates.io) is affected by RUSTSEC-2026-0190 | Dependencies (osv-scanner) |
| medium | osv/RUSTSEC-2026-0386 |
Cargo.lock | [email protected] (crates.io) is affected by RUSTSEC-2026-0386 | Dependencies (osv-scanner) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/alert_window.rs:1184 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/alert_window.rs:1195 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/alert_window.rs:1210 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.current-exe |
src/alert_window.rs:141 | 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 |
src/alert_window.rs:211 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/alert_window.rs:226 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/alert_window.rs:251 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/alert_window.rs:381 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/alert_window.rs:390 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/event_hook.rs:290 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/event_hook.rs:421 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/event_hook.rs:437 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/event_hook.rs:452 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/event_hook.rs:507 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/event_hook.rs:523 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.current-exe |
src/logger.rs:17 | 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 |
src/main.rs:106 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.current-exe |
src/main.rs:112 | 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 |
src/main.rs:155 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/main.rs:48 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/process_info.rs:167 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/process_info.rs:188 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/process_info.rs:204 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/process_info.rs:248 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/process_info.rs:285 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/process_info.rs:319 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/process_info.rs:375 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/process_info.rs:52 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/process_info.rs:70 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/screenshot.rs:147 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/screenshot.rs:167 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.current-exe |
src/screenshot.rs:27 | 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 |
src/tray.rs:47 | Detected 'unsafe' usage, please audit for secure usage [confidence high] | Static analysis (opengrep) |
| low | opengrep/rust.lang.security.unsafe-usage |
src/tray.rs:55 | 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.
| 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 | skipped | — | 0 | |
| Coding style | AI provenance | ok | — | 0 | |
| Commit velocity | AI provenance | ok | prov-4 | 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 | 0 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | skipped | — | 0 | |
| CI workflows (zizmor) | Security | skipped | — | 0 | |
| Dependencies (osv-scanner) | Security | ok | osv-scanner version: 2.7.1 | 4 | |
| 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 | 34 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 0 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | f10d8674a015 | prov-5+qual-2+sec-2 | 0% | 49 | 66 |
| 2026-11-14 | f10d8674a015 | prov-4+qual-2+sec-2 | 0% | 49 | 66 |
Full text report
- Repository: https://github.com/Fabian2000/pc_watcher
- Commit:
f10d8674a01553965069cc22f071ba4cb39a7100 - Generated: 2026-11-14T14:52:00+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) | 0 | possible | 41% | 100% |
| Code quality | 49 | poor | 90% | 100% |
| Security | 66 | weak | 85% | 100% |
AI provenance
Weak signals consistent with AI-assisted development.
-
Explicitly attributed share (lower bound): 0.0%
-
Unattributed share in AI-consistent velocity bursts: 0.0%
-
Estimated AI-generated share: 0.0%
-
AI tooling configured in repo: claude-code
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2025-12 | 3,339 | 0% |
Evidence
- .claude/settings.local.json (claude-code configuration) (.claude/sett)
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; 26% of function code in complex or long functions; 5% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 46 |
| Duplication | 73 |
| Code smells (Opengrep) | 100 |
| Tests and CI | 0 |
| Documentation | 65 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 79; mean complexity 5.7, 90th percentile 14; 4 complex and 3 long functions
- Duplicated lines: 5.2% of 2,325 compared
- Tests: 0 test lines for 3,339 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:
- window_proc in src/alert_window.rs: complexity 60, 230 lines
- event_worker in src/event_hook.rs: complexity 21, 81 lines
- win_event_proc in src/event_hook.rs: complexity 20, 39 lines
- details_window_proc in src/alert_window.rs: complexity 19, 113 lines
- set_hooks in src/event_hook.rs: complexity 9, 116 lines
Security
Security posture is weak: 4 known vulnerabilities in 4 dependencies. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 41 |
| Vulnerable dependencies (OSV) | 82 |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
-
Known vulnerabilities: 4 in 4 packages (critical 0, high 0, medium 2, low 0)
-
Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits
Top findings
| Severity | Finding | Location |
|---|---|---|
| medium | osv/RUSTSEC-2026-0190: [email protected] (crates.io) is affected by RUSTSEC-2026-0190 |
Cargo.lock |
| medium | osv/GHSA-434x-w66g-qw3r: [email protected] (crates.io) is affected by RUSTSEC-2026-0007, GHSA-434x-w66g-qw3r |
Cargo.lock |
| medium | osv/GHSA-r6v5-fh4h-64xc: [email protected] (crates.io) is affected by RUSTSEC-2026-0009, GHSA-r6v5-fh4h-64xc |
Cargo.lock |
| medium | osv/RUSTSEC-2026-0386: [email protected] (crates.io) is affected by RUSTSEC-2026-0386 |
Cargo.lock |
| 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] |
src/alert_window.rs:141 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/alert_window.rs:211 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/alert_window.rs:226 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/alert_window.rs:251 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/alert_window.rs:381 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/alert_window.rs:390 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/alert_window.rs:1184 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/alert_window.rs:1195 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/alert_window.rs:1210 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/event_hook.rs:290 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/event_hook.rs:421 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/event_hook.rs:437 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/event_hook.rs:452 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/event_hook.rs:507 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/event_hook.rs:523 |
| 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] |
src/logger.rs:17 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/main.rs:48 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/main.rs:106 |
| 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] |
src/main.rs:112 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/main.rs:155 |
| low | opengrep/rust.lang.security.unsafe-usage: Detected 'unsafe' usage, please audit for secure usage [confidence high] |
src/process_info.rs:52 |
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: 3,339; test lines: 0
| Language | Lines |
|---|---|
| Rust | 3,339 |