Leaderboard github.com
xavi129/escribetucancion-dashboard
Dashboard operativo de Escribe Tu Canción — proyecto construido 100% con IA.
AI provenance
0%
possible
- Confidence
- 40%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
35/100
poor
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
60/100
weak
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
0% possible
Weak signals consistent with AI-assisted development. Comments and strings use phrasing typical of LLM-written code (see the coding style evidence).
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)2.96
Lines added per month all AI-attributed share
- 2026-0733,933 · 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
- 1
- effective_loc
- 33,933
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 33,933
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 0
- measured_loc
- 0
- median_loc_per_hour
- 0
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 0
- work_units
- 0
Release velocityskipped
Coding styleok3 items
- step-by-step narration comment: // First, fetch the order to get spotify_upload and video flags
- step-by-step narration comment: // First, fetch the order to get spotify_upload and video flags
- step-by-step narration comment: // First, get the media URL
- count:assistant_voice
- 0
- count:emoji_in_code
- 190
- count:narrated_steps
- 3
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 18
- files:narrated_steps
- 3
- files:placeholder
- 0
- index
- 2.96
- lines_scanned
- 33,113
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 5.74
- per_kloc:narrated_steps
- 0.09
- per_kloc:placeholder
- 0
Code quality
35 poor
Code quality is poor: test-to-source ratio 0.02, no CI test run detected; 42% of function code in complex or long functions; 12% duplicated lines. Weakest area: lint.
How the score is built
- Complexity29
- Duplication49
- Lint and smells12
- Tests and CI31
- Documentation40
- Type safety100
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok10 items
- POST in app/api/webhook/suno/route.ts: complexity 98, 356 lines
- POST in app/api/suno/song-operations/route.ts: complexity 79, 268 lines
- TransactionsTable in components/transactions-table.tsx: complexity 68, 565 lines
- POST in app/api/whatsapp/send-to-leads/route.ts: complexity 61, 318 lines
- POST in app/api/dlocal/webhook/route.ts: complexity 52, 299 lines
- POST in app/api/gemini/generate-style/route.ts: complexity 47, 480 lines
- POST in app/api/orders/generate-song/route.ts: complexity 45, 194 lines
- detectGenre in app/api/gemini/generate-style/route.ts: complexity 42, 122 lines
- POST in app/api/orders/edit-lyric/route.ts: complexity 42, 207 lines
- GET in app/api/orders/[orderId]/route.ts: complexity 39, 113 lines
- complex_functions
- 52
- function_nloc
- 21,652
- functions
- 1,051
- long_functions
- 48
- many_param_functions
- 2
- mean_ccn
- 4.05
- p90_ccn
- 9
- risky_nloc_share
- 41.6%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: app/api/dlocal/create-checkout/route.ts:9 and app/api/stripe/create-checkout/route.ts:10
- 6+ duplicated lines: app/api/dlocal/create-checkout/route.ts:115 and app/api/orders/[orderId]/route.ts:48
- 6+ duplicated lines: app/api/dlocal/webhook/route.ts:279 and app/api/stripe/webhook/route.ts:67
- 6+ duplicated lines: app/api/dlocal/webhook/route.ts:355 and app/api/orders/upsell/route.ts:296
- 6+ duplicated lines: app/api/dlocal/webhook/route.ts:383 and app/api/dlocal/webhook/route.ts:453
- 6+ duplicated lines: app/api/gemini/generate-lyrics/route.ts:18 and app/api/orders/generate-and-save-lyric/route.ts:99
- 6+ duplicated lines: app/api/orders/[orderId]/route.ts:8 and app/api/stripe/create-checkout/route.ts:14
- 6+ duplicated lines: app/api/orders/complete-order/route.ts:19 and app/api/orders/generate-song/route.ts:33
- 6+ duplicated lines: app/api/orders/complete-order/route.ts:64 and app/api/orders/spotify-addon/route.ts:288
- 6+ duplicated lines: app/api/orders/edit-lyric/route.ts:43 and app/api/orders/generate-and-save-lyric/route.ts:26
- compared_lines
- 23,417
- duplicated_lines
- 2,773
- duplicated_share
- 11.8%
- files
- 186
Lintok
- category:best-practice
- 271
- category:correctness
- 5
- findings
- 276
- scanned_lines
- 33,063
- weighted_findings
- 276
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
- yes
- ci_files
- 0
- cochange_commits
- 1
- cochange_share
- 100.0%
- source_lines
- 33,113
- test_lines
- 820
- test_ratio
- 0.02
Documentationok1 item
- README.md
README.md
- check:changelog
- no
- check:contributing
- no
- check:license
- no
- check:readme
- yes
- readme_lines
- 67
Type safetyok1 item
- TypeScript strict type checking: tsconfig.json
tsconfig.json
- check:low_escape_density
- yes
- check:strict_config
- yes
- escapes
- 33
- escapes_per_kloc
- 1.01
Security
60 weak
Security posture is weak: 135 known vulnerabilities in 37 dependencies. Weakest area: posture.
How the score is built
- Secrets100
- Static analysis (SAST)99
- Vulnerable dependencies1
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesok
- checked
- 71
- declared
- 71
- 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
- 13
- findings_high
- 0
- findings_low
- 10
- findings_medium
- 3
- parse_errors
- 0
- scanned_lines
- 33,063
- weighted_findings
- 1.38
Dependencies (osv-scanner)ok
- penalty
- 282
- vulnerabilities
- 135
- vulnerable_packages
- 37
- vulns_critical
- 7
- vulns_high
- 67
- vulns_low
- 9
- vulns_medium
- 52
- vulns_unknown
- 0
CI workflows (zizmor)skipped
Security postureok
- check:dependency_updates
- no
- check:lockfiles
- yes
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 0.0%
- unpinned_manifests
- 0
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
7 critical67 high255 medium19 low
348 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| critical | osv/GHSA-2464-fhr4-w9xw |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-2464-fhr4-w9xw | Dependencies (osv-scanner) |
| critical | osv/GHSA-2xp9-vwfh-vxw4 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-2xp9-vwfh-vxw4 | Dependencies (osv-scanner) |
| critical | osv/GHSA-5xrq-8626-4rwp |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-5xrq-8626-4rwp | Dependencies (osv-scanner) |
| critical | osv/GHSA-m7jm-9gc2-mpf2 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-m7jm-9gc2-mpf2 | Dependencies (osv-scanner) |
| critical | osv/GHSA-p293-qw3h-jr36 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-p293-qw3h-jr36 | Dependencies (osv-scanner) |
| critical | osv/GHSA-vqx2-fgx2-5wq9 |
pnpm-lock.yaml | @clerk/[email protected] (npm) is affected by GHSA-vqx2-fgx2-5wq9 | Dependencies (osv-scanner) |
| critical | osv/GHSA-vqx2-fgx2-5wq9 |
pnpm-lock.yaml | @clerk/[email protected] (npm) is affected by GHSA-vqx2-fgx2-5wq9 | Dependencies (osv-scanner) |
| high | osv/GHSA-23c5-xmqv-rm74 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-23c5-xmqv-rm74 | Dependencies (osv-scanner) |
| high | osv/GHSA-23c5-xmqv-rm74 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-23c5-xmqv-rm74 | Dependencies (osv-scanner) |
| high | osv/GHSA-25h7-pfq9-p65f |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-25h7-pfq9-p65f | Dependencies (osv-scanner) |
| high | osv/GHSA-267c-6grr-h53f |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-267c-6grr-h53f | Dependencies (osv-scanner) |
| high | osv/GHSA-26hh-7cqf-hhc6 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-26hh-7cqf-hhc6 | Dependencies (osv-scanner) |
| high | osv/GHSA-2883-xcg3-v3hh |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-2883-xcg3-v3hh | Dependencies (osv-scanner) |
| high | osv/GHSA-28wg-ghj8-5hjv |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-28wg-ghj8-5hjv | Dependencies (osv-scanner) |
| high | osv/GHSA-2v37-7h3g-55p8 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-2v37-7h3g-55p8 | Dependencies (osv-scanner) |
| high | osv/GHSA-36qx-fr4f-26g5 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-36qx-fr4f-26g5 | Dependencies (osv-scanner) |
| high | osv/GHSA-37qj-frw5-hhjh |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-37qj-frw5-hhjh | Dependencies (osv-scanner) |
| high | osv/GHSA-3jxr-9vmj-r5cp |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-3jxr-9vmj-r5cp | Dependencies (osv-scanner) |
| high | osv/GHSA-3jxr-9vmj-r5cp |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-3jxr-9vmj-r5cp | Dependencies (osv-scanner) |
| high | osv/GHSA-3ppc-4f35-3m26 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-3ppc-4f35-3m26 | Dependencies (osv-scanner) |
| high | osv/GHSA-3ppc-4f35-3m26 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-3ppc-4f35-3m26 | Dependencies (osv-scanner) |
| high | osv/GHSA-492v-c6pp-mqqv |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-492v-c6pp-mqqv | Dependencies (osv-scanner) |
| high | osv/GHSA-52cp-r559-cp3m |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-52cp-r559-cp3m | Dependencies (osv-scanner) |
| high | osv/GHSA-587h-7wmj-h5pm |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-587h-7wmj-h5pm | Dependencies (osv-scanner) |
| high | osv/GHSA-5j98-mcp5-4vw2 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-5j98-mcp5-4vw2 | Dependencies (osv-scanner) |
| high | osv/GHSA-5p4m-2wfm-xmqj |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-5p4m-2wfm-xmqj | Dependencies (osv-scanner) |
| high | osv/GHSA-68fv-2mgg-jv7q |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-68fv-2mgg-jv7q | 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-6g55-p6wh-862q |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-6g55-p6wh-862q | 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-6j4f-fj2g-mc7p |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-6j4f-fj2g-mc7p | Dependencies (osv-scanner) |
| high | osv/GHSA-6j4f-fj2g-mc7p |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-6j4f-fj2g-mc7p | Dependencies (osv-scanner) |
| high | osv/GHSA-73wf-gq98-2v4g |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-73wf-gq98-2v4g | Dependencies (osv-scanner) |
| high | osv/GHSA-7r86-cg39-jmmj |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-7r86-cg39-jmmj | Dependencies (osv-scanner) |
| high | osv/GHSA-7r86-cg39-jmmj |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-7r86-cg39-jmmj | Dependencies (osv-scanner) |
| high | osv/GHSA-89xv-2m56-2m9x |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-89xv-2m56-2m9x | Dependencies (osv-scanner) |
| high | osv/GHSA-8gc5-j5rx-235r |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-8gc5-j5rx-235r | Dependencies (osv-scanner) |
| high | osv/GHSA-8h8q-6873-q5fj |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-8h8q-6873-q5fj | Dependencies (osv-scanner) |
| high | osv/GHSA-96hv-2xvq-fx4p |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-96hv-2xvq-fx4p | Dependencies (osv-scanner) |
| high | osv/GHSA-9mp4-77wg-rwx9 |
pnpm-lock.yaml | @clerk/[email protected] (npm) is affected by GHSA-9mp4-77wg-rwx9 | Dependencies (osv-scanner) |
| high | osv/GHSA-c2c7-rcm5-vvqj |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-c2c7-rcm5-vvqj | Dependencies (osv-scanner) |
| high | osv/GHSA-c2c7-rcm5-vvqj |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-c2c7-rcm5-vvqj | Dependencies (osv-scanner) |
| high | osv/GHSA-c4j6-fc7j-m34r |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-c4j6-fc7j-m34r | Dependencies (osv-scanner) |
| high | osv/GHSA-c83g-rgw3-j3cx |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-c83g-rgw3-j3cx | Dependencies (osv-scanner) |
| high | osv/GHSA-f88m-g3jw-g9cj |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-f88m-g3jw-g9cj | Dependencies (osv-scanner) |
| high | osv/GHSA-h25m-26qc-wcjf |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-h25m-26qc-wcjf | Dependencies (osv-scanner) |
| high | osv/GHSA-jmr7-xgp7-cmfj |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-jmr7-xgp7-cmfj | Dependencies (osv-scanner) |
| high | osv/GHSA-m99w-x7hq-7vfj |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-m99w-x7hq-7vfj | Dependencies (osv-scanner) |
| high | osv/GHSA-mg66-mrh9-m8jx |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-mg66-mrh9-m8jx | Dependencies (osv-scanner) |
| high | osv/GHSA-mh99-v99m-4gvg |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-mh99-v99m-4gvg | Dependencies (osv-scanner) |
| high | osv/GHSA-mh99-v99m-4gvg |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-mh99-v99m-4gvg | Dependencies (osv-scanner) |
| high | osv/GHSA-mrhx-c7xc-m3w5 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-mrhx-c7xc-m3w5 | Dependencies (osv-scanner) |
| high | osv/GHSA-mw96-cpmx-2vgc |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-mw96-cpmx-2vgc | Dependencies (osv-scanner) |
| high | osv/GHSA-p3m5-59mp-jv5r |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-p3m5-59mp-jv5r | Dependencies (osv-scanner) |
| high | osv/GHSA-p9ff-h696-f583 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-p9ff-h696-f583 | Dependencies (osv-scanner) |
| high | osv/GHSA-p9j2-gv94-2wf4 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-p9j2-gv94-2wf4 | Dependencies (osv-scanner) |
| high | osv/GHSA-q4gf-8mx6-v5v3 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-q4gf-8mx6-v5v3 | Dependencies (osv-scanner) |
| high | osv/GHSA-qhr7-859c-m2p7 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-qhr7-859c-m2p7 | Dependencies (osv-scanner) |
| high | osv/GHSA-qhr7-859c-m2p7 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-qhr7-859c-m2p7 | Dependencies (osv-scanner) |
| high | osv/GHSA-qjx8-664m-686j |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-qjx8-664m-686j | 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) |
| high | osv/GHSA-r28c-9q8g-f849 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-r28c-9q8g-f849 | 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) |
| high | osv/GHSA-r5fr-rjxr-66jc |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-r5fr-rjxr-66jc | Dependencies (osv-scanner) |
| high | osv/GHSA-rf6f-7fwh-wjgh |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-rf6f-7fwh-wjgh | Dependencies (osv-scanner) |
| high | osv/GHSA-rgj7-g3m4-5g8c |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-rgj7-g3m4-5g8c | Dependencies (osv-scanner) |
| high | osv/GHSA-rgw5-rvv9-x895 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-rgw5-rvv9-x895 | Dependencies (osv-scanner) |
| high | osv/GHSA-rgw5-rvv9-x895 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-rgw5-rvv9-x895 | Dependencies (osv-scanner) |
| high | osv/GHSA-v2wj-q39q-566r |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-v2wj-q39q-566r | Dependencies (osv-scanner) |
| high | osv/GHSA-w24r-5266-9c3c |
pnpm-lock.yaml | @clerk/[email protected] (npm) is affected by GHSA-w24r-5266-9c3c | Dependencies (osv-scanner) |
| high | osv/GHSA-w24r-5266-9c3c |
pnpm-lock.yaml | @clerk/[email protected] (npm) is affected by GHSA-w24r-5266-9c3c | Dependencies (osv-scanner) |
| high | osv/GHSA-w24r-5266-9c3c |
pnpm-lock.yaml | @clerk/[email protected] (npm) is affected by GHSA-w24r-5266-9c3c | Dependencies (osv-scanner) |
| high | osv/GHSA-wq5f-xc86-pv6w |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-wq5f-xc86-pv6w | Dependencies (osv-scanner) |
| high | osv/GHSA-xwg4-73v4-xw9w |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-xwg4-73v4-xw9w | Dependencies (osv-scanner) |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
components/suno-generation-form.tsx:327 | 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 |
components/suno-generation-form.tsx:449 | 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/suno-generation-form.tsx:501 | 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/suno-generation-form.tsx:523 | 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/suno-generation-form.tsx:538 | 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/suno-generation-form.tsx:582 | 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/transaction-form.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/transaction-form.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/transaction-form.tsx:205 | 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/transaction-form.tsx:219 | 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/transaction-form.tsx:233 | 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/transaction-form.tsx:247 | 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/transaction-form.tsx:353 | 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/transaction-form.tsx:368 | 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/transaction-form.tsx:439 | 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/transaction-form.tsx:455 | 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/transaction-form.tsx:473 | 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/transaction-form.tsx:546 | 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/transaction-form.tsx:570 | 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/transaction-form.tsx:594 | 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/transaction-form.tsx:640 | 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/transaction-form.tsx:655 | 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/transaction-form.tsx:693 | 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/transaction-form.tsx:712 | 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/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1016 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1024 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1028 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1043 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1048 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1053 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1074 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1080 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1084 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1149 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1187 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1192 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1196 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1215 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1220 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1227 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1259 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1281 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1287 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1291 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1310 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
components/transactions-table.tsx:1316 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-prompt |
components/transactions-table.tsx:1333 | found prompt() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1335 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-prompt |
components/transactions-table.tsx:1339 | found prompt() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1341 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1365 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1374 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:1378 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.correctness.no-stringify-keys |
components/transactions-table.tsx:218 | 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/javascript.lang.correctness.no-stringify-keys |
components/transactions-table.tsx:219 | 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/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:590 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:707 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:709 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:713 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:723 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:737 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:743 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:749 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:772 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:777 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:781 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:788 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
components/transactions-table.tsx:794 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:818 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:827 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:831 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:837 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:842 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:859 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:861 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:865 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:879 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:885 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:890 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-alert |
components/transactions-table.tsx:895 | found alert() call; should this be in production code? | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/accordion.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/accordion.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/accordion.tsx:50 | 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: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/alert-dialog.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/alert-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/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: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/alert-dialog.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/alert-dialog.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/alert-dialog.tsx:95 | 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: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/alert.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.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 |
components/ui/avatar.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/avatar.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/avatar.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/badge.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/breadcrumb.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/breadcrumb.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 |
components/ui/breadcrumb.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 |
components/ui/breadcrumb.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 |
components/ui/breadcrumb.tsx:70 | 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: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/breadcrumb.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/button.tsx:49 | 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: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/card.tsx:15 | 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: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/card.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/card.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 |
components/ui/card.tsx:63 | 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: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/carousel.tsx:143 | 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:168 | 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:191 | 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: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/carousel.tsx:246 | 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: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/checkbox.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/command.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/command.tsx:121 | 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: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 |
components/ui/command.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/command.tsx:50 | 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:64 | 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: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 |
components/ui/command.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/context-menu.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/context-menu.tsx:126 | 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:163 | 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:178 | 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: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/context-menu.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/context-menu.tsx:68 | 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:87 | 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: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/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/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: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 |
components/ui/dialog.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/dialog.tsx:94 | 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: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/drawer.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/drawer.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/drawer.tsx:49 | 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:64 | 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:75 | 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: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/dropdown-menu.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/dropdown-menu.tsx:129 | 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:154 | 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:166 | 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:178 | 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: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/dropdown-menu.tsx:53 | 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: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/dropdown-menu.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/form.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 |
components/ui/form.tsx:122 | 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:139 | 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: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/form.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/form.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/hover-card.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: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/input-otp.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/input-otp.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/input-otp.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 |
components/ui/input.tsx:15 | 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: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 |
components/ui/menubar.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/menubar.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/menubar.tsx:139 | 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: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/menubar.tsx:186 | 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: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/menubar.tsx:213 | 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: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/menubar.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/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: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/navigation-menu.tsx:110 | 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/navigation-menu.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/navigation-menu.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/navigation-menu.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 |
components/ui/navigation-menu.tsx:75 | 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/navigation-menu.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/pagination.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/pagination.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/pagination.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/pagination.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/pagination.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/pagination.tsx:70 | 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/pagination.tsx:86 | 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/popover.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 |
components/ui/progress.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/javascript.lang.security.html-in-template-string |
app/api/email/send/route.ts:27 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-regexp |
app/api/gemini/generate-style/route.ts:351 | RegExp() called with a `genreType` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.html-in-template-string |
components/transactions-table.tsx:1160 | This template literal looks like HTML and has interpolated variables. These variables are not HTML-encoded by default. If the variables contain HTML tags, these may be interpreted by the browser, resulting in cross-site scripting (XSS).... | Static analysis (opengrep) |
| medium | osv/GHSA-2g4f-4pwh-qvx6 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-2g4f-4pwh-qvx6 | Dependencies (osv-scanner) |
| medium | osv/GHSA-3g3m-2fjr-6pw4 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-3g3m-2fjr-6pw4 | Dependencies (osv-scanner) |
| medium | osv/GHSA-3v7f-55p6-f55p |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-3v7f-55p6-f55p | Dependencies (osv-scanner) |
| medium | osv/GHSA-3v7f-55p6-f55p |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-3v7f-55p6-f55p | Dependencies (osv-scanner) |
| medium | osv/GHSA-3x4c-7xq6-9pq8 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-3x4c-7xq6-9pq8 | Dependencies (osv-scanner) |
| medium | osv/GHSA-4633-3j49-mh5q |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-4633-3j49-mh5q | Dependencies (osv-scanner) |
| medium | osv/GHSA-48c2-rrv3-qjmp |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-48c2-rrv3-qjmp | Dependencies (osv-scanner) |
| medium | osv/GHSA-4c39-4ccg-62r3 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-4c39-4ccg-62r3 | Dependencies (osv-scanner) |
| medium | osv/GHSA-4jqv-mc3x-m676 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-4jqv-mc3x-m676 | Dependencies (osv-scanner) |
| medium | osv/GHSA-4mjr-xmp4-gh2g |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-4mjr-xmp4-gh2g | Dependencies (osv-scanner) |
| medium | osv/GHSA-4w7w-66w2-5vf9 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-4w7w-66w2-5vf9 | Dependencies (osv-scanner) |
| medium | osv/GHSA-58qx-3vcg-4xpx |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-58qx-3vcg-4xpx | Dependencies (osv-scanner) |
| medium | osv/GHSA-68g3-v927-f742 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-68g3-v927-f742 | Dependencies (osv-scanner) |
| medium | osv/GHSA-698v-4r3x-3vcv |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-698v-4r3x-3vcv | Dependencies (osv-scanner) |
| medium | osv/GHSA-6pq8-jhm2-2vcw |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-6pq8-jhm2-2vcw | Dependencies (osv-scanner) |
| medium | osv/GHSA-6rw7-vpxm-498p |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-6rw7-vpxm-498p | Dependencies (osv-scanner) |
| medium | osv/GHSA-82fw-gwwq-j7x9 |
pnpm-lock.yaml | @vitest/[email protected] (npm) is affected by GHSA-82fw-gwwq-j7x9 | Dependencies (osv-scanner) |
| medium | osv/GHSA-82fw-gwwq-j7x9 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-82fw-gwwq-j7x9 | Dependencies (osv-scanner) |
| medium | osv/GHSA-866g-f22w-33x8 |
pnpm-lock.yaml | @ai-sdk/[email protected] (npm) is affected by GHSA-866g-f22w-33x8 | Dependencies (osv-scanner) |
| medium | osv/GHSA-955p-x3mx-jcvp |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-955p-x3mx-jcvp | Dependencies (osv-scanner) |
| medium | osv/GHSA-9g9p-9gw9-jx7f |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-9g9p-9gw9-jx7f | Dependencies (osv-scanner) |
| medium | osv/GHSA-f886-m6hf-6m8v |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-f886-m6hf-6m8v | Dependencies (osv-scanner) |
| medium | osv/GHSA-f886-m6hf-6m8v |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-f886-m6hf-6m8v | Dependencies (osv-scanner) |
| medium | osv/GHSA-ffhc-5mcf-pf4q |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-ffhc-5mcf-pf4q | Dependencies (osv-scanner) |
| medium | osv/GHSA-fx2h-pf6j-xcff |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-fx2h-pf6j-xcff | 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-fxqj-rqcc-2cmp |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-fxqj-rqcc-2cmp | 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-g3hv-75wg-m249 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-g3hv-75wg-m249 | Dependencies (osv-scanner) |
| medium | osv/GHSA-ggv3-7p47-pfv8 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-ggv3-7p47-pfv8 | Dependencies (osv-scanner) |
| medium | osv/GHSA-gh4j-gqv2-49f6 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-gh4j-gqv2-49f6 | Dependencies (osv-scanner) |
| medium | osv/GHSA-gx5p-jg67-6x7h |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-gx5p-jg67-6x7h | Dependencies (osv-scanner) |
| medium | osv/GHSA-h64f-5h5j-jqjh |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-h64f-5h5j-jqjh | Dependencies (osv-scanner) |
| medium | osv/GHSA-h67p-54hq-rp68 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-h67p-54hq-rp68 | Dependencies (osv-scanner) |
| medium | osv/GHSA-jp2q-39xq-3w4g |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-jp2q-39xq-3w4g | Dependencies (osv-scanner) |
| medium | osv/GHSA-mcj8-r9mp-w47p |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-mcj8-r9mp-w47p | Dependencies (osv-scanner) |
| medium | osv/GHSA-p498-v437-472g |
pnpm-lock.yaml | @humanfs/[email protected] (npm) is affected by GHSA-p498-v437-472g | Dependencies (osv-scanner) |
| medium | osv/GHSA-q2hr-2g5m-vwhr |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-q2hr-2g5m-vwhr | Dependencies (osv-scanner) |
| medium | osv/GHSA-q2hr-2g5m-vwhr |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-q2hr-2g5m-vwhr | Dependencies (osv-scanner) |
| medium | osv/GHSA-q8mj-m7cp-5q26 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-q8mj-m7cp-5q26 | Dependencies (osv-scanner) |
| medium | osv/GHSA-q8wf-6r8g-63ch |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-q8wf-6r8g-63ch | 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-qx2v-qp2m-jg93 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-qx2v-qp2m-jg93 | 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-qxg6-89mg-rqv8 |
pnpm-lock.yaml | @vitest/[email protected] (npm) is affected by GHSA-qxg6-89mg-rqv8 | Dependencies (osv-scanner) |
| medium | osv/GHSA-r825-w8mm-5pxw |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-r825-w8mm-5pxw | Dependencies (osv-scanner) |
| medium | osv/GHSA-rj75-hqrm-r3gf |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-rj75-hqrm-r3gf | Dependencies (osv-scanner) |
| medium | osv/GHSA-rq7h-c2jc-7f22 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-rq7h-c2jc-7f22 | Dependencies (osv-scanner) |
| medium | osv/GHSA-v6wh-96g9-6wx3 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-v6wh-96g9-6wx3 | Dependencies (osv-scanner) |
| medium | osv/GHSA-w9m9-85wc-3x92 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-w9m9-85wc-3x92 | Dependencies (osv-scanner) |
| medium | osv/GHSA-wfc6-r584-vfw7 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-wfc6-r584-vfw7 | Dependencies (osv-scanner) |
| medium | osv/GHSA-xxjr-mmjv-4gpg |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-xxjr-mmjv-4gpg | Dependencies (osv-scanner) |
| low | opengrep/javascript.lang.security.audit.unsafe-formatstring |
app/api/cron/generate-songs/route.ts:153 | Detected string concatenation with a non-literal variable in a util.format / console.log function. If an attacker injects a format specifier in the string, it will forge the log message. Try to use constant values for the format string.... | Static analysis (opengrep) |
| low | opengrep/javascript.lang.security.audit.unsafe-formatstring |
app/api/cron/generate-songs/route.ts:162 | Detected string concatenation with a non-literal variable in a util.format / console.log function. If an attacker injects a format specifier in the string, it will forge the log message. Try to use constant values for the format string.... | Static analysis (opengrep) |
| low | opengrep/javascript.lang.security.audit.unsafe-formatstring |
app/api/suno/tasks/route.ts:46 | Detected string concatenation with a non-literal variable in a util.format / console.log function. If an attacker injects a format specifier in the string, it will forge the log message. Try to use constant values for the format string.... | Static analysis (opengrep) |
| low | opengrep/javascript.lang.security.audit.unsafe-formatstring |
app/api/video/webhook/route.ts:98 | Detected string concatenation with a non-literal variable in a util.format / console.log function. If an attacker injects a format specifier in the string, it will forge the log message. Try to use constant values for the format string.... | Static analysis (opengrep) |
| low | opengrep/javascript.lang.security.audit.unsafe-formatstring |
app/api/whatsapp/send-to-leads/route.ts:35 | Detected string concatenation with a non-literal variable in a util.format / console.log function. If an attacker injects a format specifier in the string, it will forge the log message. Try to use constant values for the format string.... | Static analysis (opengrep) |
| low | opengrep/javascript.lang.security.audit.unsafe-formatstring |
app/api/whatsapp/send-to-leads/route.ts:41 | Detected string concatenation with a non-literal variable in a util.format / console.log function. If an attacker injects a format specifier in the string, it will forge the log message. Try to use constant values for the format string.... | Static analysis (opengrep) |
| low | opengrep/javascript.lang.security.audit.unsafe-formatstring |
app/api/whatsapp/send-to-leads/route.ts:43 | Detected string concatenation with a non-literal variable in a util.format / console.log function. If an attacker injects a format specifier in the string, it will forge the log message. Try to use constant values for the format string.... | Static analysis (opengrep) |
| low | opengrep/javascript.lang.security.audit.unsafe-formatstring |
app/api/whatsapp/send-to-leads/route.ts:48 | Detected string concatenation with a non-literal variable in a util.format / console.log function. If an attacker injects a format specifier in the string, it will forge the log message. Try to use constant values for the format string.... | Static analysis (opengrep) |
| low | opengrep/javascript.lang.security.audit.unsafe-formatstring |
app/api/whatsapp/send-to-leads/route.ts:609 | Detected string concatenation with a non-literal variable in a util.format / console.log function. If an attacker injects a format specifier in the string, it will forge the log message. Try to use constant values for the format string.... | Static analysis (opengrep) |
| low | opengrep/javascript.lang.security.audit.unsafe-formatstring |
components/transactions-table.tsx:194 | Detected string concatenation with a non-literal variable in a util.format / console.log function. If an attacker injects a format specifier in the string, it will forge the log message. Try to use constant values for the format string.... | Static analysis (opengrep) |
| low | osv/GHSA-3g8h-86w9-wvmq |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-3g8h-86w9-wvmq | Dependencies (osv-scanner) |
| low | osv/GHSA-474x-hrwr-fgx4 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-474x-hrwr-fgx4 | Dependencies (osv-scanner) |
| low | osv/GHSA-4x5r-pxfx-6jf8 |
pnpm-lock.yaml | @babel/[email protected] (npm) is affected by GHSA-4x5r-pxfx-6jf8 | Dependencies (osv-scanner) |
| low | osv/GHSA-8r88-6cj9-9fh5 |
pnpm-lock.yaml | @supabase/[email protected] (npm) is affected by GHSA-8r88-6cj9-9fh5 | Dependencies (osv-scanner) |
| low | osv/GHSA-9jrq-w75r-8gcw |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-9jrq-w75r-8gcw | Dependencies (osv-scanner) |
| low | osv/GHSA-fj3w-jwp8-x2g3 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-fj3w-jwp8-x2g3 | Dependencies (osv-scanner) |
| low | osv/GHSA-v6h2-p8h4-qcjw |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-v6h2-p8h4-qcjw | Dependencies (osv-scanner) |
| low | osv/GHSA-vfv6-92ff-j949 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-vfv6-92ff-j949 | Dependencies (osv-scanner) |
| low | osv/GHSA-w7fw-mjwx-w883 |
pnpm-lock.yaml | [email protected] (npm) is affected by GHSA-w7fw-mjwx-w883 | 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.
| Analyzer | Pillar | Status | Version | Findings | Note |
|---|---|---|---|---|---|
| AI tool configuration | AI provenance | ok | signatures-v1 | 0 | |
| Explicit AI attribution | AI provenance | ok | signatures-v1 | 0 | |
| Release velocity | AI provenance | skipped | — | 0 | |
| Coding style | AI provenance | ok | — | 0 | |
| Commit velocity | AI provenance | ok | prov-4 | 0 | |
| Complexity (lizard) | Code quality | ok | lizard 1.25.1 | 0 | |
| Documentation | Code quality | ok | — | 0 | |
| Duplication (jscpd) | Code quality | ok | repotrust-dup-w6 | 0 | |
| Lint | Code quality | ok | opengrep 1.33.1; rules f1d2b562b414 | 200 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | ok | — | 0 | |
| CI workflows (zizmor) | Security | skipped | — | 0 | |
| Dependencies (osv-scanner) | Security | ok | osv-scanner version: 2.7.1 | 135 | |
| 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 | 13 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 0 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | ec1d3e425e3e | prov-5+qual-2+sec-2 | 0% | 35 | 60 |
| 2026-11-14 | ec1d3e425e3e | prov-4+qual-2+sec-2 | 0% | 35 | 60 |
Full text report
- Repository: https://github.com/xavi129/escribetucancion-dashboard
- Commit:
ec1d3e425e3e020d727afa359e94b70d4640a79d - Generated: 2026-11-14T14:52:08+00:00
- Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2
Scores
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 0 | possible | 40% | 100% |
| Code quality | 35 | poor | 90% | 100% |
| Security | 60 | weak | 85% | 100% |
AI provenance
Weak signals consistent with AI-assisted development. Comments and strings use phrasing typical of LLM-written code (see the coding style evidence).
-
Explicitly attributed share (lower bound): 0.0%
-
Unattributed share in AI-consistent velocity bursts: 0.0%
-
Estimated AI-generated share: 0.0%
-
Stylometry index: 2.96 per 1,000 lines (narrated steps 3, placeholders 0, assistant phrasing 0, emoji 190). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2026-07 | 33,933 | 0% |
Evidence
- step-by-step narration comment: // First, fetch the order to get spotify_upload and video flags (app/api/dloc)
- step-by-step narration comment: // First, fetch the order to get spotify_upload and video flags (app/api/stri)
- step-by-step narration comment: // First, get the media URL (lib/whatsapp)
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.02, no CI test run detected; 42% of function code in complex or long functions; 12% duplicated lines. Weakest area: lint.
| Area | Score |
|---|---|
| Complexity (lizard) | 29 |
| Duplication | 49 |
| Code smells (Opengrep) | 12 |
| Tests and CI | 31 |
| Documentation | 40 |
| Type safety | 100 |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 1,051; mean complexity 4.0, 90th percentile 9; 52 complex and 48 long functions
- Duplicated lines: 11.8% of 23,417 compared
- Tests: 820 test lines for 33,113 source lines (ratio 0.02); CI test commands: none detected; 100% of recent source commits also change tests
- Docs missing or thin: license, contributing, changelog
Most complex functions:
- POST in app/api/webhook/suno/route.ts: complexity 98, 356 lines
- POST in app/api/suno/song-operations/route.ts: complexity 79, 268 lines
- TransactionsTable in components/transactions-table.tsx: complexity 68, 565 lines
- POST in app/api/whatsapp/send-to-leads/route.ts: complexity 61, 318 lines
- POST in app/api/dlocal/webhook/route.ts: complexity 52, 299 lines
Security
Security posture is weak: 135 known vulnerabilities in 37 dependencies. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 99 |
| Vulnerable dependencies (OSV) | 1 |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
-
Known vulnerabilities: 135 in 37 packages (critical 7, high 67, medium 52, low 9)
-
Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits
Top findings
| Severity | Finding | Location |
|---|---|---|
| critical | osv/GHSA-vqx2-fgx2-5wq9: @clerk/[email protected] (npm) is affected by GHSA-vqx2-fgx2-5wq9 |
pnpm-lock.yaml |
| critical | osv/GHSA-vqx2-fgx2-5wq9: @clerk/[email protected] (npm) is affected by GHSA-vqx2-fgx2-5wq9 |
pnpm-lock.yaml |
| critical | osv/GHSA-m7jm-9gc2-mpf2: [email protected] (npm) is affected by GHSA-m7jm-9gc2-mpf2 |
pnpm-lock.yaml |
| critical | osv/GHSA-2464-fhr4-w9xw: [email protected] (npm) is affected by GHSA-2464-fhr4-w9xw |
pnpm-lock.yaml |
| critical | osv/GHSA-2xp9-vwfh-vxw4: [email protected] (npm) is affected by GHSA-2xp9-vwfh-vxw4 |
pnpm-lock.yaml |
| critical | osv/GHSA-p293-qw3h-jr36: [email protected] (npm) is affected by GHSA-p293-qw3h-jr36 |
pnpm-lock.yaml |
| critical | osv/GHSA-5xrq-8626-4rwp: [email protected] (npm) is affected by GHSA-5xrq-8626-4rwp |
pnpm-lock.yaml |
| high | osv/GHSA-w24r-5266-9c3c: @clerk/[email protected] (npm) is affected by GHSA-w24r-5266-9c3c |
pnpm-lock.yaml |
| high | osv/GHSA-9mp4-77wg-rwx9: @clerk/[email protected] (npm) is affected by GHSA-9mp4-77wg-rwx9 |
pnpm-lock.yaml |
| high | osv/GHSA-w24r-5266-9c3c: @clerk/[email protected] (npm) is affected by GHSA-w24r-5266-9c3c |
pnpm-lock.yaml |
| high | osv/GHSA-w24r-5266-9c3c: @clerk/[email protected] (npm) is affected by GHSA-w24r-5266-9c3c |
pnpm-lock.yaml |
| high | osv/GHSA-3jxr-9vmj-r5cp: [email protected] (npm) is affected by GHSA-3jxr-9vmj-r5cp |
pnpm-lock.yaml |
| high | osv/GHSA-6j4f-fj2g-mc7p: [email protected] (npm) is affected by GHSA-6j4f-fj2g-mc7p |
pnpm-lock.yaml |
| high | osv/GHSA-mh99-v99m-4gvg: [email protected] (npm) is affected by GHSA-mh99-v99m-4gvg |
pnpm-lock.yaml |
| high | osv/GHSA-qhr7-859c-m2p7: [email protected] (npm) is affected by GHSA-qhr7-859c-m2p7 |
pnpm-lock.yaml |
| high | osv/GHSA-rgw5-rvv9-x895: [email protected] (npm) is affected by GHSA-rgw5-rvv9-x895 |
pnpm-lock.yaml |
| high | osv/GHSA-3jxr-9vmj-r5cp: [email protected] (npm) is affected by GHSA-3jxr-9vmj-r5cp |
pnpm-lock.yaml |
| high | osv/GHSA-6j4f-fj2g-mc7p: [email protected] (npm) is affected by GHSA-6j4f-fj2g-mc7p |
pnpm-lock.yaml |
| high | osv/GHSA-mh99-v99m-4gvg: [email protected] (npm) is affected by GHSA-mh99-v99m-4gvg |
pnpm-lock.yaml |
| high | osv/GHSA-qhr7-859c-m2p7: [email protected] (npm) is affected by GHSA-qhr7-859c-m2p7 |
pnpm-lock.yaml |
| high | osv/GHSA-rgw5-rvv9-x895: [email protected] (npm) is affected by GHSA-rgw5-rvv9-x895 |
pnpm-lock.yaml |
| high | osv/GHSA-73wf-gq98-2v4g: [email protected] (npm) is affected by GHSA-73wf-gq98-2v4g |
pnpm-lock.yaml |
| high | osv/GHSA-c83g-rgw3-j3cx: [email protected] (npm) is affected by GHSA-c83g-rgw3-j3cx |
pnpm-lock.yaml |
| high | osv/GHSA-37qj-frw5-hhjh: [email protected] (npm) is affected by GHSA-37qj-frw5-hhjh |
pnpm-lock.yaml |
| high | osv/GHSA-8gc5-j5rx-235r: [email protected] (npm) is affected by GHSA-8gc5-j5rx-235r |
pnpm-lock.yaml |
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: 33,113; test lines: 820
| Language | Lines |
|---|---|
| TypeScript | 33,601 |
| JavaScript | 282 |
| SQL | 50 |