Leaderboard github.com
Foveluy/Dragact
a dragger layout system with React style .
AI provenance
0%
none-detected
- Confidence
- 65%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
43/100
poor
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
80/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 pace0
- Coding-style index (1.0+ means possible)0.15
Lines added per month all AI-attributed share
- 2017-091,578 · 0% AI
- 2017-1056 · 0% AI
- 2018-025,217 · 0% AI
- 2018-031,691 · 0% AI
- 2018-040 · 0% AI
- 2018-0847 · 0% AI
- 2018-090 · 0% AI
- 2018-12100 · 0% AI
- 2019-010 · 0% AI
- 2019-030 · 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
- 170
- effective_loc
- 8,689
- 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
- 310.66
- measured_loc
- 8,689
- median_loc_per_hour
- 47
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 8,689
- work_units
- 88
Release velocityok
- flagged_releases
- 0
- max_loc_per_day
- 418.70
- releases
- 3
Coding styleok
- count:assistant_voice
- 0
- count:emoji_in_code
- 1
- count:narrated_steps
- 0
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 1
- files:narrated_steps
- 0
- files:placeholder
- 0
- index
- 0.15
- lines_scanned
- 3,297
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 0.30
- per_kloc:narrated_steps
- 0
- per_kloc:placeholder
- 0
Code quality
43 poor
Code quality is poor: test-to-source ratio 0.00, no CI test run detected; 4% of function code in complex or long functions; 27% duplicated lines. Weakest area: lint.
How the score is built
- Complexity89
- Duplication20
- Lint and smells8
- Tests and CI21
- Documentation85
- Type safety60
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok1 item
- complex_functions
- 1
- function_nloc
- 1,977
- functions
- 181
- long_functions
- 0
- many_param_functions
- 0
- mean_ccn
- 2.31
- p90_ccn
- 4
- risky_nloc_share
- 4.0%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: example/AddRemove/index.tsx:4 and example/HandleLayout/index.tsx:7
- 6+ duplicated lines: example/HandleLayout/index.tsx:8 and example/LayoutRestore/index.tsx:7
- 6+ duplicated lines: example/HistoryLayout/index.tsx:7 and example/NormalLayout/index.tsx:9
- 6+ duplicated lines: example/HistoryLayout/largedata.ts:1 and example/NormalLayout/largedata.ts:1
- 6+ duplicated lines: example/HistoryLayout/largedata.ts:2 and example/HistoryLayout/largedata.ts:7
- 6+ duplicated lines: example/NormalLayout/index.tsx:72 and example/mobileLayout/index.tsx:60
- 6+ duplicated lines: src/lib/dragact.tsx:40 and src/lib/dragact.tsx:108
- 6+ duplicated lines: src/lib/dragger/base.tsx:68 and src/lib/dragger/index.tsx:29
- 6+ duplicated lines: src/lib/dragger/index.tsx:67 and src/lib/dragger/index.tsx:169
- 6+ duplicated lines: webpack.config.js:9 and webpack.pro.config.js:8
- compared_lines
- 2,244
- duplicated_lines
- 598
- duplicated_share
- 26.7%
- files
- 29
Lintok
- category:best-practice
- 34
- findings
- 34
- scanned_lines
- 3,297
- weighted_findings
- 34
Tests and CIok
- check:ci_present
- no
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- yes
- check:test_ratio
- no
- check:tests_cochange
- no
- ci_files
- 0
- cochange_commits
- 116
- cochange_share
- 0.9%
- source_lines
- 3,297
- test_lines
- 15
- test_ratio
- 0.00
Documentationok3 items
- README.md
README.md - LICENSE
LICENSE - docs/changelog.md
docs/changelog.md
- check:changelog
- yes
- check:contributing
- no
- check:license
- yes
- check:readme
- yes
- readme_lines
- 62
Type safetyok1 item
- TypeScript strict type checking: tsconfig.json
tsconfig.json
- check:low_escape_density
- no
- check:strict_config
- yes
- escapes
- 103
- escapes_per_kloc
- 32.56
Security
80 adequate
Security posture is adequate: no high-impact findings. Weakest area: posture.
How the score is built
- Secrets97
- 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 registriesok
- checked
- 31
- declared
- 31
- lookup_errors
- 0
- missing
- 0
- recent
- 0
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 1
- secrets_nonprod
- 0
Static analysis (opengrep)ok
- findings
- 0
- findings_high
- 0
- findings_low
- 0
- findings_medium
- 0
- parse_errors
- 0
- scanned_lines
- 3,297
- weighted_findings
- 0
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok1 item
- package.json has no lockfile alongside it (unpinned dependencies)
package.json
- check:dependency_updates
- no
- check:lockfiles
- no
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 3.5%
- unpinned_manifests
- 1
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
34 medium1 low
35 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/AddRemove/index.tsx:102 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/AddRemove/index.tsx:16 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/AddRemove/index.tsx:17 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/HandleLayout/index.tsx:35 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/HandleLayout/index.tsx:36 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/HandleLayout/index.tsx:51 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/HandleLayout/index.tsx:54 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/HandleLayout/index.tsx:79 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-legacy-component |
example/HistoryLayout/HistoryLayout.tsx:105 | Legacy component lifecycle was detected - componentWillReceiveProps. | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/HistoryLayout/HistoryLayout.tsx:120 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/HistoryLayout/index.tsx:21 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/HistoryLayout/index.tsx:22 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/HistoryLayout/index.tsx:36 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/HistoryLayout/index.tsx:88 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-legacy-component |
example/LayoutRestore/index.tsx:36 | Legacy component lifecycle was detected - componentWillMount. | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/LayoutRestore/index.tsx:57 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/NormalLayout/index.tsx:23 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/NormalLayout/index.tsx:24 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/NormalLayout/index.tsx:38 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/NormalLayout/index.tsx:74 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/StaticWidget/index.tsx:25 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/StaticWidget/index.tsx:26 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/mobileLayout/index.tsx:21 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/mobileLayout/index.tsx:22 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
example/mobileLayout/index.tsx:62 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
src/lib/dragact.tsx:210 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-legacy-component |
src/lib/dragact.tsx:215 | Legacy component lifecycle was detected - componentWillReceiveProps. | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
src/lib/dragact.tsx:324 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-legacy-component |
src/lib/dragger/base.tsx:372 | Legacy component lifecycle was detected - componentWillReceiveProps. | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
src/lib/dragger/base.tsx:451 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
src/lib/dragger/base.tsx:456 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-in-state |
src/lib/dragger/base.tsx:76 | Copying a prop into state in React -- this is bad practice as all updates to it are ignored. Instead, read props directly in your component and avoid copying props into state. | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-in-state |
src/lib/dragger/index.tsx:37 | Copying a prop into state in React -- this is bad practice as all updates to it are ignored. Instead, read props directly in your component and avoid copying props into state. | Lint |
| medium | opengrep/typescript.react.best-practice.react-legacy-component |
src/lib/dragger/index.tsx:410 | Legacy component lifecycle was detected - componentWillReceiveProps. | Lint |
| low | gitleaks/generic-api-key |
build/GridItem.js:109 | Possible generic-api-key secret in history (commit 8532d2c13f); removed from the current tree but still retrievable | Secrets (gitleaks) |
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-4 | 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 | 34 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | ok | — | 0 | |
| CI workflows (zizmor) | Security | skipped | — | 0 | |
| Dependencies (osv-scanner) | Security | skipped | — | 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 | 0 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 1 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 4679af2c3bad | prov-5+qual-2+sec-2 | 0% | 43 | 80 |
| 2026-11-14 | 4679af2c3bad | prov-4+qual-2+sec-2 | 0% | 43 | 80 |
Full text report
- Repository: https://github.com/Foveluy/Dragact
- Commit:
4679af2c3badcb627b54154a69947b580b7044b7 - 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 | none-detected | 65% | 100% |
| Code quality | 43 | poor | 90% | 100% |
| Security | 80 | 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%
-
Stylometry index: 0.15 per 1,000 lines (narrated steps 0, placeholders 0, assistant phrasing 0, emoji 1). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2017-09 | 1,578 | 0% |
| 2017-10 | 56 | 0% |
| 2018-02 | 5,217 | 0% |
| 2018-03 | 1,691 | 0% |
| 2018-08 | 47 | 0% |
| 2018-12 | 100 | 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 poor: test-to-source ratio 0.00, no CI test run detected; 4% of function code in complex or long functions; 27% duplicated lines. Weakest area: lint.
| Area | Score |
|---|---|
| Complexity (lizard) | 89 |
| Duplication | 20 |
| Code smells (Opengrep) | 8 |
| Tests and CI | 21 |
| Documentation | 85 |
| Type safety | 60 |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 181; mean complexity 2.3, 90th percentile 4; 1 complex and 0 long functions
- Duplicated lines: 26.7% of 2,244 compared
- Tests: 15 test lines for 3,297 source lines (ratio 0.00); CI test commands: none detected; 1% of recent source commits also change tests
- Docs missing or thin: contributing
Most complex functions:
Security
Security posture is adequate: no high-impact findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 97 |
| 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: none; missing: security policy, dependency updates, signed commits, lockfiles
Top findings
| Severity | Finding | Location |
|---|---|---|
| low | gitleaks/generic-api-key: Possible generic-api-key secret in history (commit 8532d2c13f); removed from the current tree but still retrievable |
build/GridItem.js:109 |
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,297; test lines: 15
| Language | Lines |
|---|---|
| TypeScript | 3,163 |
| JavaScript | 149 |