RepoTrust

Leaderboard github.com

Mohamin007/Lens-AI-Research-Engine

  • View repository ↗
  • TypeScript
  • ★ 1
  • commit f7cd355bc6b6
  • scored 2026-11-14
  • scoring prov-5+qual-2+sec-2

AI provenance

0%

none-detected

Confidence
42%
Coverage
100%

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

Code quality

41/100

poor

Confidence
90%
Coverage
100%

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

Security

68/100

weak

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.87

Lines added per month all AI-attributed share

  1. 2026-038,617 · 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
7
effective_loc
8,617
tools_detected
0
AI tool configurationok
artifacts
0
tools_configured
0
workflow_agents
0
Commit velocityok
excluded_import_loc
8,601
flagged_loc
0
flagged_loc_share
0.0%
flagged_units
0
max_loc_per_hour
4
measured_loc
16
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
1
Release velocityskipped
Coding styleok4 items
count:assistant_voice
0
count:emoji_in_code
7
count:narrated_steps
4
count:placeholder
0
files:assistant_voice
0
files:emoji_in_code
2
files:narrated_steps
1
files:placeholder
0
index
0.87
lines_scanned
8,615
per_kloc:assistant_voice
0
per_kloc:emoji_in_code
0.81
per_kloc:narrated_steps
0.46
per_kloc:placeholder
0

Code quality

41 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; 6% duplicated lines. Weakest area: lint.

How the score is built

  • Complexity87
  • Duplication72
  • Lint and smells0
  • Tests and CI0
  • Documentation40
  • Type safety100
  • Review processnot measured

Evidence by analyzer

Complexity (lizard)ok2 items
complex_functions
0
function_nloc
5,665
functions
492
long_functions
2
many_param_functions
0
mean_ccn
1.74
p90_ccn
4
risky_nloc_share
4.5%
Duplication (jscpd)ok5 items
compared_lines
5,939
duplicated_lines
328
duplicated_share
5.5%
files
77
Lintok
category:best-practice
306
category:correctness
7
findings
313
scanned_lines
8,615
weighted_findings
308.50
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
2
cochange_share
0.0%
source_lines
8,615
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
77
Type safetyok1 item
  • TypeScript strict type checking: tsconfig.json tsconfig.json
check:low_escape_density
yes
check:strict_config
yes
escapes
7
escapes_per_kloc
0.81

Security

68 weak

Security posture is weak: 60 known vulnerabilities in 12 dependencies. Weakest area: posture.

How the score is built

  • Secrets100
  • Static analysis (SAST)100
  • Vulnerable dependencies21
  • CI workflowsnot measured
  • Security posture20
  • OpenSSF Scorecardnot measured

Evidence by analyzer

OpenSSF Scorecardskipped

no published OpenSSF Scorecard result for this repo

Package registriesok
checked
60
declared
60
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
0
findings_high
0
findings_low
0
findings_medium
0
parse_errors
0
scanned_lines
8,615
weighted_findings
0
Dependencies (osv-scanner)ok
penalty
93
vulnerabilities
60
vulnerable_packages
12
vulns_critical
5
vulns_high
31
vulns_low
2
vulns_medium
22
vulns_unknown
0
CI workflows (zizmor)skipped
Security postureok
check:dependency_updates
no
check:lockfiles
yes
check:security_policy
no
check:signed_commits
yes
signed_commit_share
57.1%
unpinned_manifests
0
Release downloadsok
binary_assets
0
signals
0
suspicious
0

Findings

5 critical31 high222 medium2 low

SeverityRuleLocationMessageTool
critical osv/GHSA-2464-fhr4-w9xw package-lock.json [email protected] (npm) is affected by GHSA-2464-fhr4-w9xw; also in pnpm-lock.yaml Dependencies (osv-scanner)
critical osv/GHSA-2xp9-vwfh-vxw4 package-lock.json [email protected] (npm) is affected by GHSA-2xp9-vwfh-vxw4; also in pnpm-lock.yaml Dependencies (osv-scanner)
critical osv/GHSA-673q-mjm6-r5xr package-lock.json [email protected] (npm) is affected by GHSA-673q-mjm6-r5xr; also in pnpm-lock.yaml Dependencies (osv-scanner)
critical osv/GHSA-p293-qw3h-jr36 package-lock.json [email protected] (npm) is affected by GHSA-p293-qw3h-jr36; also in pnpm-lock.yaml Dependencies (osv-scanner)
critical osv/GHSA-vcvr-r3jv-pc5j package-lock.json [email protected] (npm) is affected by GHSA-vcvr-r3jv-pc5j; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-267c-6grr-h53f package-lock.json [email protected] (npm) is affected by GHSA-267c-6grr-h53f; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-26hh-7cqf-hhc6 package-lock.json [email protected] (npm) is affected by GHSA-26hh-7cqf-hhc6; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-28wg-ghj8-5hjv package-lock.json [email protected] (npm) is affected by GHSA-28wg-ghj8-5hjv; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-2v37-7h3g-55p8 package-lock.json [email protected] (npm) is affected by GHSA-2v37-7h3g-55p8; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-36qx-fr4f-26g5 package-lock.json [email protected] (npm) is affected by GHSA-36qx-fr4f-26g5; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-492v-c6pp-mqqv package-lock.json [email protected] (npm) is affected by GHSA-492v-c6pp-mqqv; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-68fv-2mgg-jv7q package-lock.json [email protected] (npm) is affected by GHSA-68fv-2mgg-jv7q; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-6g55-p6wh-862q package-lock.json [email protected] (npm) is affected by GHSA-6g55-p6wh-862q; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-6g55-p6wh-862q package-lock.json [email protected] (npm) is affected by GHSA-6g55-p6wh-862q Dependencies (osv-scanner)
high osv/GHSA-6gpp-xcg3-4w24 package-lock.json [email protected] (npm) is affected by GHSA-6gpp-xcg3-4w24; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-73wf-gq98-2v4g package-lock.json [email protected] (npm) is affected by GHSA-73wf-gq98-2v4g; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-89xv-2m56-2m9x package-lock.json [email protected] (npm) is affected by GHSA-89xv-2m56-2m9x; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-8h8q-6873-q5fj package-lock.json [email protected] (npm) is affected by GHSA-8h8q-6873-q5fj; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-c4j6-fc7j-m34r package-lock.json [email protected] (npm) is affected by GHSA-c4j6-fc7j-m34r; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-c83g-rgw3-j3cx package-lock.json [email protected] (npm) is affected by GHSA-c83g-rgw3-j3cx; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-cjq9-62q9-8jv4 package-lock.json [email protected] (npm) is affected by GHSA-cjq9-62q9-8jv4; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-f88m-g3jw-g9cj package-lock.json [email protected] (npm) is affected by GHSA-f88m-g3jw-g9cj; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-m99w-x7hq-7vfj package-lock.json [email protected] (npm) is affected by GHSA-m99w-x7hq-7vfj; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-mg66-mrh9-m8jx package-lock.json [email protected] (npm) is affected by GHSA-mg66-mrh9-m8jx; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-mrhx-c7xc-m3w5 package-lock.json [email protected] (npm) is affected by GHSA-mrhx-c7xc-m3w5; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-p3m5-59mp-jv5r package-lock.json [email protected] (npm) is affected by GHSA-p3m5-59mp-jv5r; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-p9j2-gv94-2wf4 package-lock.json [email protected] (npm) is affected by GHSA-p9j2-gv94-2wf4; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-q4gf-8mx6-v5v3 package-lock.json [email protected] (npm) is affected by GHSA-q4gf-8mx6-v5v3; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-r28c-9q8g-f849 package-lock.json [email protected] (npm) is affected by GHSA-r28c-9q8g-f849; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-r28c-9q8g-f849 package-lock.json [email protected] (npm) is affected by GHSA-r28c-9q8g-f849 Dependencies (osv-scanner)
high osv/GHSA-r5fr-rjxr-66jc package-lock.json [email protected] (npm) is affected by GHSA-r5fr-rjxr-66jc; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-rgj7-g3m4-5g8c package-lock.json [email protected] (npm) is affected by GHSA-rgj7-g3m4-5g8c; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-wq5f-xc86-pv6w package-lock.json [email protected] (npm) is affected by GHSA-wq5f-xc86-pv6w; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-xwg4-73v4-xw9w package-lock.json [email protected] (npm) is affected by GHSA-xwg4-73v4-xw9w; also in pnpm-lock.yaml Dependencies (osv-scanner)
high osv/GHSA-6g55-p6wh-862q pnpm-lock.yaml [email protected] (npm) is affected by GHSA-6g55-p6wh-862q Dependencies (osv-scanner)
high osv/GHSA-r28c-9q8g-f849 pnpm-lock.yaml [email protected] (npm) is affected by GHSA-r28c-9q8g-f849 Dependencies (osv-scanner)
medium opengrep/javascript.lang.correctness.no-stringify-keys app/research/page.tsx:193 JSON stringify does not produce a stable key ordering, and should not be relied on for producing object keys. Consider using json-stable-stringify instead. Lint
medium opengrep/typescript.react.best-practice.react-props-spreading app/result/page.tsx:100 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 app/result/page.tsx:108 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 app/result/page.tsx:13 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 app/result/page.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 app/result/page.tsx:27 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 app/result/page.tsx:32 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 app/result/page.tsx:37 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 app/result/page.tsx:47 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 app/result/page.tsx:48 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 app/result/page.tsx:55 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 app/result/page.tsx:60 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 app/result/page.tsx:65 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 app/result/page.tsx:72 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 app/result/page.tsx:77 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 app/result/page.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-props-spreading app/result/page.tsx:84 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 app/result/page.tsx:91 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 components/theme-provider.tsx:10 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 components/ui/accordion.tsx:12 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 components/ui/accordion.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 components/ui/accordion.tsx:41 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 components/ui/accordion.tsx:59 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 components/ui/alert-dialog.tsx:103 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 components/ui/alert-dialog.tsx:116 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 components/ui/alert-dialog.tsx:12 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 components/ui/alert-dialog.tsx:128 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 components/ui/alert-dialog.tsx:140 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 components/ui/alert-dialog.tsx:19 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 components/ui/alert-dialog.tsx:27 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 components/ui/alert-dialog.tsx:42 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 components/ui/alert-dialog.tsx:60 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 components/ui/alert-dialog.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 components/ui/alert-dialog.tsx:90 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 components/ui/alert.tsx:32 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 components/ui/alert.tsx:45 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 components/ui/alert.tsx:61 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 components/ui/aspect-ratio.tsx:8 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 components/ui/avatar.tsx:19 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 components/ui/avatar.tsx:32 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 components/ui/avatar.tsx:48 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 components/ui/badge.tsx:41 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 components/ui/breadcrumb.tsx:19 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 components/ui/breadcrumb.tsx:29 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 components/ui/breadcrumb.tsx:47 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 components/ui/breadcrumb.tsx:60 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 components/ui/breadcrumb.tsx:76 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 components/ui/breadcrumb.tsx:8 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 components/ui/breadcrumb.tsx:93 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 components/ui/button-group.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 components/ui/button-group.tsx:55 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 components/ui/button-group.tsx:73 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 components/ui/button.tsx:55 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 components/ui/calendar.tsx:134 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 components/ui/calendar.tsx:141 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 components/ui/calendar.tsx:149 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 components/ui/calendar.tsx:155 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 components/ui/calendar.tsx:161 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 components/ui/calendar.tsx:170 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 components/ui/calendar.tsx:208 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 components/ui/card.tsx:13 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 components/ui/card.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 components/ui/card.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 components/ui/card.tsx:46 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 components/ui/card.tsx:59 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 components/ui/card.tsx:69 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 components/ui/card.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-props-spreading components/ui/carousel.tsx:127 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 components/ui/carousel.tsx:150 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 components/ui/carousel.tsx:169 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 components/ui/carousel.tsx:196 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 components/ui/carousel.tsx:226 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 components/ui/chart.tsx:61 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 components/ui/checkbox.tsx:20 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 components/ui/collapsible.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 components/ui/collapsible.tsx:28 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 components/ui/collapsible.tsx:8 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 components/ui/command.tsx:108 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 components/ui/command.tsx:124 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 components/ui/command.tsx:137 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 components/ui/command.tsx:153 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 components/ui/command.tsx:169 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 components/ui/command.tsx:27 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 components/ui/command.tsx:46 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 components/ui/command.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-props-spreading components/ui/command.tsx:96 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 components/ui/context-menu.tsx:108 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 components/ui/context-menu.tsx:12 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 components/ui/context-menu.tsx:132 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 components/ui/context-menu.tsx:151 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 components/ui/context-menu.tsx:175 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 components/ui/context-menu.tsx:19 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 components/ui/context-menu.tsx:202 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 components/ui/context-menu.tsx:215 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 components/ui/context-menu.tsx:231 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 components/ui/context-menu.tsx:27 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 components/ui/context-menu.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 components/ui/context-menu.tsx:42 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 components/ui/context-menu.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 components/ui/context-menu.tsx:72 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 components/ui/context-menu.tsx:91 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 components/ui/dialog.tsx:101 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 components/ui/dialog.tsx:114 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 components/ui/dialog.tsx:12 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 components/ui/dialog.tsx:127 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 components/ui/dialog.tsx:18 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 components/ui/dialog.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 components/ui/dialog.tsx:30 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 components/ui/dialog.tsx:44 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 components/ui/dialog.tsx:66 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 components/ui/dialog.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-props-spreading components/ui/drawer.tsx:106 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 components/ui/drawer.tsx:11 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 components/ui/drawer.tsx:119 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 components/ui/drawer.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 components/ui/drawer.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 components/ui/drawer.tsx:29 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 components/ui/drawer.tsx:43 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 components/ui/drawer.tsx:66 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 components/ui/drawer.tsx:83 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 components/ui/drawer.tsx:93 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 components/ui/dropdown-menu.tsx:117 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 components/ui/dropdown-menu.tsx:12 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 components/ui/dropdown-menu.tsx:134 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 components/ui/dropdown-menu.tsx:161 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 components/ui/dropdown-menu.tsx:174 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 components/ui/dropdown-menu.tsx:19 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 components/ui/dropdown-menu.tsx:190 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 components/ui/dropdown-menu.tsx:198 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 components/ui/dropdown-menu.tsx:217 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 components/ui/dropdown-menu.tsx:236 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 components/ui/dropdown-menu.tsx:29 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 components/ui/dropdown-menu.tsx:48 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 components/ui/dropdown-menu.tsx:58 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 components/ui/dropdown-menu.tsx:80 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 components/ui/dropdown-menu.tsx:99 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 components/ui/empty.tsx:13 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 components/ui/empty.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 components/ui/empty.tsx:56 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 components/ui/empty.tsx:66 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 components/ui/empty.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-props-spreading components/ui/empty.tsx:92 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 components/ui/field.tsx:105 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 components/ui/field.tsx:123 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 components/ui/field.tsx:136 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 components/ui/field.tsx:151 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 components/ui/field.tsx:171 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 components/ui/field.tsx:19 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 components/ui/field.tsx:226 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 components/ui/field.tsx:39 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 components/ui/field.tsx:52 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 components/ui/field.tsx:92 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 components/ui/form.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 components/ui/form.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 components/ui/form.tsx:133 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 components/ui/form.tsx:151 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 components/ui/form.tsx:40 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 components/ui/form.tsx:84 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 components/ui/hover-card.tsx:11 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 components/ui/hover-card.tsx:18 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 components/ui/hover-card.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 components/ui/input-group.tsx:113 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 components/ui/input-group.tsx:125 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 components/ui/input-group.tsx:141 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 components/ui/input-group.tsx:157 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 components/ui/input-group.tsx:33 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 components/ui/input-group.tsx:76 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 components/ui/input-otp.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 components/ui/input-otp.tsx:34 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 components/ui/input-otp.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 components/ui/input-otp.tsx:71 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 components/ui/input.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 components/ui/item.tsx:101 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 components/ui/item.tsx:114 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 components/ui/item.tsx:127 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 components/ui/item.tsx:14 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 components/ui/item.tsx:141 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 components/ui/item.tsx:151 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 components/ui/item.tsx:164 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 components/ui/item.tsx:177 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 components/ui/item.tsx:28 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 components/ui/item.tsx:69 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 components/ui/kbd.tsx:13 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 components/ui/kbd.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 components/ui/label.tsx:19 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 components/ui/menubar.tsx:109 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 components/ui/menubar.tsx:128 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 components/ui/menubar.tsx:152 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 components/ui/menubar.tsx:179 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 components/ui/menubar.tsx:192 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 components/ui/menubar.tsx:20 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 components/ui/menubar.tsx:208 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 components/ui/menubar.tsx:216 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 components/ui/menubar.tsx:235 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 components/ui/menubar.tsx:28 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 components/ui/menubar.tsx:34 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 components/ui/menubar.tsx:40 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 components/ui/menubar.tsx:47 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 components/ui/menubar.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 components/ui/menubar.tsx:85 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 osv/GHSA-39w2-rjm5-chcv package-lock.json [email protected] (npm) is affected by GHSA-39w2-rjm5-chcv; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-4633-3j49-mh5q package-lock.json [email protected] (npm) is affected by GHSA-4633-3j49-mh5q; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-4c39-4ccg-62r3 package-lock.json [email protected] (npm) is affected by GHSA-4c39-4ccg-62r3; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-4jqv-mc3x-m676 package-lock.json [email protected] (npm) is affected by GHSA-4jqv-mc3x-m676; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-68g3-v927-f742 package-lock.json [email protected] (npm) is affected by GHSA-68g3-v927-f742; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-955p-x3mx-jcvp package-lock.json [email protected] (npm) is affected by GHSA-955p-x3mx-jcvp; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-f23m-r3pf-42rh package-lock.json [email protected] (npm) is affected by GHSA-f23m-r3pf-42rh; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-f87g-xv8r-7p7x package-lock.json [email protected] (npm) is affected by GHSA-f87g-xv8r-7p7x; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-ffhc-5mcf-pf4q package-lock.json [email protected] (npm) is affected by GHSA-ffhc-5mcf-pf4q; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-fxqj-rqcc-2cmp package-lock.json [email protected] (npm) is affected by GHSA-fxqj-rqcc-2cmp; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-fxqj-rqcc-2cmp package-lock.json [email protected] (npm) is affected by GHSA-fxqj-rqcc-2cmp Dependencies (osv-scanner)
medium osv/GHSA-gx5p-jg67-6x7h package-lock.json [email protected] (npm) is affected by GHSA-gx5p-jg67-6x7h; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-h64f-5h5j-jqjh package-lock.json [email protected] (npm) is affected by GHSA-h64f-5h5j-jqjh; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-mcj8-r9mp-w47p package-lock.json [email protected] (npm) is affected by GHSA-mcj8-r9mp-w47p; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-q8wf-6r8g-63ch package-lock.json [email protected] (npm) is affected by GHSA-q8wf-6r8g-63ch; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-qx2v-qp2m-jg93 package-lock.json [email protected] (npm) is affected by GHSA-qx2v-qp2m-jg93; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-qx2v-qp2m-jg93 package-lock.json [email protected] (npm) is affected by GHSA-qx2v-qp2m-jg93 Dependencies (osv-scanner)
medium osv/GHSA-w5vr-8v7q-w6rv package-lock.json [email protected] (npm) is affected by GHSA-w5vr-8v7q-w6rv Dependencies (osv-scanner)
medium osv/GHSA-wfc6-r584-vfw7 package-lock.json [email protected] (npm) is affected by GHSA-wfc6-r584-vfw7; also in pnpm-lock.yaml Dependencies (osv-scanner)
medium osv/GHSA-fxqj-rqcc-2cmp pnpm-lock.yaml [email protected] (npm) is affected by GHSA-fxqj-rqcc-2cmp Dependencies (osv-scanner)
medium osv/GHSA-qx2v-qp2m-jg93 pnpm-lock.yaml [email protected] (npm) is affected by GHSA-qx2v-qp2m-jg93 Dependencies (osv-scanner)
medium osv/GHSA-w5vr-8v7q-w6rv pnpm-lock.yaml [email protected] (npm) is affected by GHSA-w5vr-8v7q-w6rv Dependencies (osv-scanner)
low osv/GHSA-3g8h-86w9-wvmq package-lock.json [email protected] (npm) is affected by GHSA-3g8h-86w9-wvmq; also in pnpm-lock.yaml Dependencies (osv-scanner)
low osv/GHSA-vfv6-92ff-j949 package-lock.json [email protected] (npm) is affected by GHSA-vfv6-92ff-j949; also in pnpm-lock.yaml Dependencies (osv-scanner)

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 f1d2b562b414200
Tests and CICode qualityok—0
Type safetyCode qualityok—0
CI workflows (zizmor)Securityskipped—0
Dependencies (osv-scanner)Securityokosv-scanner version: 2.7.160
Release downloadsSecurityok—0
Security postureSecurityok—0
Package registriesSecurityok—0
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-14f7cd355bc6b6prov-5+qual-2+sec-20%4168
2026-11-14f7cd355bc6b6prov-4+qual-2+sec-20%4168

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/Mohamin007/Lens-AI-Research-Engine/ai.svg)](https://repotrust.synapticcyber.com/r/github.com/Mohamin007/Lens-AI-Research-Engine/)
[![RepoTrust quality](https://repotrust.synapticcyber.com/badge/github.com/Mohamin007/Lens-AI-Research-Engine/quality.svg)](https://repotrust.synapticcyber.com/r/github.com/Mohamin007/Lens-AI-Research-Engine/)
[![RepoTrust security](https://repotrust.synapticcyber.com/badge/github.com/Mohamin007/Lens-AI-Research-Engine/security.svg)](https://repotrust.synapticcyber.com/r/github.com/Mohamin007/Lens-AI-Research-Engine/)
Full text report

Scores

Pillar Score Signal Confidence Coverage
AI provenance (estimated AI-generated share) 0 none-detected 42% 100%
Code quality 41 poor 90% 100%
Security 68 weak 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.87 per 1,000 lines (narrated steps 4, placeholders 0, assistant phrasing 0, emoji 7). Reported as a signal, not scored.

Month Lines added Attributed to AI
2026-03 8,617 0%

Evidence

  • step-by-step narration comment: // STEP 1: Search Agent (app/research)
  • step-by-step narration comment: // STEP 2: Scrape Agent (app/research)
  • step-by-step narration comment: // STEP 2: Scrape Agent (app/research)
  • step-by-step narration comment: // STEP 3: Synthesis Agent (app/research)

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; 6% duplicated lines. Weakest area: lint.

Area Score
Complexity (lizard) 87
Duplication 72
Code smells (Opengrep) 0
Tests and CI 0
Documentation 40
Type safety 100
Process (Scorecard review/maintenance) n/a
  • Functions: 492; mean complexity 1.7, 90th percentile 4; 0 complex and 2 long functions
  • Duplicated lines: 5.5% of 5,939 compared
  • Tests: 0 test lines for 8,615 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 weak: 60 known vulnerabilities in 12 dependencies. Weakest area: posture.

Area Score
Secrets (gitleaks, tree + history) 100
Static analysis (Opengrep) 100
Vulnerable dependencies (OSV) 21
CI workflows (zizmor) n/a
Posture (policy, updates, signing, lockfiles) 20
OpenSSF Scorecard n/a
  • Known vulnerabilities: 60 in 12 packages (critical 5, high 31, medium 22, low 2)

  • Posture checks passed: signed commits, lockfiles; missing: security policy, dependency updates

Top findings

Severity Finding Location
critical osv/GHSA-2464-fhr4-w9xw: [email protected] (npm) is affected by GHSA-2464-fhr4-w9xw; also in pnpm-lock.yaml package-lock.json
critical osv/GHSA-2xp9-vwfh-vxw4: [email protected] (npm) is affected by GHSA-2xp9-vwfh-vxw4; also in pnpm-lock.yaml package-lock.json
critical osv/GHSA-673q-mjm6-r5xr: [email protected] (npm) is affected by GHSA-673q-mjm6-r5xr; also in pnpm-lock.yaml package-lock.json
critical osv/GHSA-p293-qw3h-jr36: [email protected] (npm) is affected by GHSA-p293-qw3h-jr36; also in pnpm-lock.yaml package-lock.json
critical osv/GHSA-vcvr-r3jv-pc5j: [email protected] (npm) is affected by GHSA-vcvr-r3jv-pc5j; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-73wf-gq98-2v4g: [email protected] (npm) is affected by GHSA-73wf-gq98-2v4g; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-c83g-rgw3-j3cx: [email protected] (npm) is affected by GHSA-c83g-rgw3-j3cx; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-r5fr-rjxr-66jc: [email protected] (npm) is affected by GHSA-r5fr-rjxr-66jc; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-28wg-ghj8-5hjv: [email protected] (npm) is affected by GHSA-28wg-ghj8-5hjv; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-2v37-7h3g-55p8: [email protected] (npm) is affected by GHSA-2v37-7h3g-55p8; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-xwg4-73v4-xw9w: [email protected] (npm) is affected by GHSA-xwg4-73v4-xw9w; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-267c-6grr-h53f: [email protected] (npm) is affected by GHSA-267c-6grr-h53f; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-26hh-7cqf-hhc6: [email protected] (npm) is affected by GHSA-26hh-7cqf-hhc6; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-36qx-fr4f-26g5: [email protected] (npm) is affected by GHSA-36qx-fr4f-26g5; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-492v-c6pp-mqqv: [email protected] (npm) is affected by GHSA-492v-c6pp-mqqv; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-6gpp-xcg3-4w24: [email protected] (npm) is affected by GHSA-6gpp-xcg3-4w24; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-89xv-2m56-2m9x: [email protected] (npm) is affected by GHSA-89xv-2m56-2m9x; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-8h8q-6873-q5fj: [email protected] (npm) is affected by GHSA-8h8q-6873-q5fj; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-c4j6-fc7j-m34r: [email protected] (npm) is affected by GHSA-c4j6-fc7j-m34r; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-cjq9-62q9-8jv4: [email protected] (npm) is affected by GHSA-cjq9-62q9-8jv4; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-m99w-x7hq-7vfj: [email protected] (npm) is affected by GHSA-m99w-x7hq-7vfj; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-mg66-mrh9-m8jx: [email protected] (npm) is affected by GHSA-mg66-mrh9-m8jx; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-p3m5-59mp-jv5r: [email protected] (npm) is affected by GHSA-p3m5-59mp-jv5r; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-p9j2-gv94-2wf4: [email protected] (npm) is affected by GHSA-p9j2-gv94-2wf4; also in pnpm-lock.yaml package-lock.json
high osv/GHSA-q4gf-8mx6-v5v3: [email protected] (npm) is affected by GHSA-q4gf-8mx6-v5v3; also in pnpm-lock.yaml package-lock.json

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: 8,615; test lines: 0
Language Lines
TypeScript 8,596
JavaScript 19