Leaderboard github.com
sirTob1/pebble-pushup-reminder
AI provenance
0%
possible
- Confidence
- 52%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
50/100
weak
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
83/100
adequate
- 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
- 2026-062,504 · 0% AI
- 2026-07126 · 0% AI
- 2026-0884 · 0% AI
- 2026-09620 · 0% AI
- 2026-1054 · 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
- 47
- effective_loc
- 3,388
- tools_detected
- 0
AI tool configurationok1 item
- artifacts
- 1
- earliest_adoption
- 2026-08-23
- tools_configured
- 1
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 0
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 366
- measured_loc
- 3,388
- median_loc_per_hour
- 127.69
- pr_timed_units
- 1
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 0
- work_units
- 19
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
- 2,507
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0
- per_kloc:narrated_steps
- 0
- per_kloc:placeholder
- 0
Code quality
50 weak
Code quality is weak: test-to-source ratio 0.00, no CI test run detected; 23% of function code in complex or long functions; 3% duplicated lines. Weakest area: testing.
How the score is built
- Complexity49
- Duplication84
- Lint and smells100
- Tests and CI0
- Documentation60
- Type safety40
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok5 items
- run_adaptive_algorithm in src/c/main.c: complexity 27, 109 lines
- renderDashboard in src/pkjs/custom-clay.js: complexity 26, 125 lines
- (anonymous) in src/pkjs/index.js: complexity 18, 57 lines
- load_settings in src/c/main.c: complexity 17, 54 lines
- inbox_received_handler in src/c/main.c: complexity 17, 55 lines
- complex_functions
- 5
- function_nloc
- 1,703
- functions
- 100
- long_functions
- 2
- many_param_functions
- 0
- mean_ccn
- 3.90
- p90_ccn
- 10
- risky_nloc_share
- 23.5%
Duplication (jscpd)ok1 item
- compared_lines
- 1,876
- duplicated_lines
- 56
- duplicated_share
- 3.0%
- files
- 7
Lintok
- findings
- 0
- scanned_lines
- 2,507
- 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
- 32
- cochange_share
- 0.0%
- source_lines
- 2,507
- test_lines
- 0
- test_ratio
- 0
Documentationok2 items
- README.md
README.md - CHANGELOG.md
CHANGELOG.md
- check:changelog
- yes
- check:contributing
- no
- check:license
- no
- check:readme
- yes
- readme_lines
- 30
Type safetyok
- check:low_escape_density
- yes
- check:strict_config
- no
- escapes
- 0
- escapes_per_kloc
- 0
Security
83 adequate
Security posture is adequate: no high-impact findings. Weakest area: posture.
How the score is built
- Secrets100
- Static analysis (SAST)86
- Vulnerable dependencies100
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesok
- checked
- 1
- declared
- 1
- 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
- 3
- findings_high
- 0
- findings_low
- 0
- findings_medium
- 3
- parse_errors
- 0
- scanned_lines
- 2,507
- weighted_findings
- 1.10
Dependencies (osv-scanner)ok
- penalty
- 0
- vulnerabilities
- 0
- vulnerable_packages
- 0
- vulns_critical
- 0
- vulns_high
- 0
- vulns_low
- 0
- vulns_medium
- 0
- vulns_unknown
- 0
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 downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
3 medium
3 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| medium | opengrep/c.lang.security.insecure-use-memset |
src/c/main.c:210 | When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While `memset()` is commonly used for this purpose, it can leave sensitive information... | Static analysis (opengrep) |
| medium | opengrep/javascript.browser.security.insufficient-postmessage-origin-validation |
src/pkjs/custom-clay.js:190 | No validation of origin is done by the addEventListener API. It may be possible to exploit this flaw to perform Cross Origin attacks such as Cross-Site Scripting(XSS). [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.browser.security.wildcard-postmessage-configuration |
src/pkjs/custom-clay.js:194 | The target origin of the window.postMessage() API is set to "*". This could allow for information disclosure due to the possibility of any origin allowed to receive the message. [confidence medium] | 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 | ok | — | 0 | |
| CI workflows (zizmor) | Security | skipped | — | 0 | |
| Dependencies (osv-scanner) | Security | ok | osv-scanner version: 2.7.1 | 0 | |
| 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 | 3 | |
| 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 | ec0b2a5bf566 | prov-5+qual-2+sec-2 | 0% | 50 | 83 |
| 2026-11-14 | ec0b2a5bf566 | prov-4+qual-2+sec-2 | 0% | 50 | 83 |
Full text report
- Repository: https://github.com/sirTob1/pebble-pushup-reminder
- Commit:
ec0b2a5bf566fa16e7861d8552bf73fff8d74b19 - Generated: 2026-11-14T14:52:07+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 | 52% | 100% |
| Code quality | 50 | weak | 90% | 100% |
| Security | 83 | adequate | 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: generic-agent
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2026-06 | 2,504 | 0% |
| 2026-07 | 126 | 0% |
| 2026-08 | 84 | 0% |
| 2026-09 | 620 | 0% |
| 2026-10 | 54 | 0% |
Evidence
- .agents/AGENTS.md (generic-agent configuration) (.agents/AGEN)
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; 23% of function code in complex or long functions; 3% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 49 |
| Duplication | 84 |
| Code smells (Opengrep) | 100 |
| Tests and CI | 0 |
| Documentation | 60 |
| Type safety | 40 |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 100; mean complexity 3.9, 90th percentile 10; 5 complex and 2 long functions
- Duplicated lines: 3.0% of 1,876 compared
- Tests: 0 test lines for 2,507 source lines (ratio 0.00); CI test commands: none detected; 0% of recent source commits also change tests
- Docs missing or thin: license, contributing
Most complex functions:
- run_adaptive_algorithm in src/c/main.c: complexity 27, 109 lines
- renderDashboard in src/pkjs/custom-clay.js: complexity 26, 125 lines
- (anonymous) in src/pkjs/index.js: complexity 18, 57 lines
- load_settings in src/c/main.c: complexity 17, 54 lines
- inbox_received_handler in src/c/main.c: complexity 17, 55 lines
Security
Security posture is adequate: no high-impact findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 86 |
| Vulnerable dependencies (OSV) | 100 |
| 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
Top findings
| Severity | Finding | Location |
|---|---|---|
| medium | opengrep/c.lang.security.insecure-use-memset: When handling sensitive information in a buffer, it's important to ensure that the data is securely erased before the buffer is deleted or reused. While memset() is commonly used for this purpose, it can leave sensitive information behind due to compiler optimizations or other factors. To avoi [confidence low] |
src/c/main.c:210 |
| medium | opengrep/javascript.browser.security.insufficient-postmessage-origin-validation: No validation of origin is done by the addEventListener API. It may be possible to exploit this flaw to perform Cross Origin attacks such as Cross-Site Scripting(XSS). [confidence low] |
src/pkjs/custom-clay.js:190 |
| medium | opengrep/javascript.browser.security.wildcard-postmessage-configuration: The target origin of the window.postMessage() API is set to "*". This could allow for information disclosure due to the possibility of any origin allowed to receive the message. [confidence medium] |
src/pkjs/custom-clay.js:194 |
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: 2,507; test lines: 0
| Language | Lines |
|---|---|
| C | 1,729 |
| JavaScript | 534 |
| Python | 203 |
| Shell | 41 |