Leaderboard github.com
isuryanarayanan/supers
thoughts, reflections and intrests.
AI provenance
0%
possible
- Confidence
- 48%
- 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
43/100
poor
- 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 files2
- Work sessions at AI pace0
- Releases at AI pacenot measured
- Coding-style index (1.0+ means possible)5.32
Lines added per month all AI-attributed share
- 2025-0814,894 · 0% AI
- 2025-11441 · 0% AI
- 2026-0174 · 0% AI
- 2026-093,358 · 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
- 32
- effective_loc
- 18,767
- tools_detected
- 0
AI tool configurationok2 items
- AGENTS.md (generic-agent configuration)
- .github/copilot-instructions.md (github-copilot configuration)
- artifacts
- 2
- earliest_adoption
- 2025-08-15
- tools_configured
- 2
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 12,714
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 318.25
- measured_loc
- 6,053
- median_loc_per_hour
- 57.75
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 0
- work_units
- 15
Release velocityskipped
Coding styleok8 items
- step-by-step narration comment: // First, let's check if bucket exists anywhere
- step-by-step narration comment: // Step 1: Get pre-signed URL
- step-by-step narration comment: // Step 2: Upload directly to S3
- step-by-step narration comment: // Step 1: Pre-build checks (only if not skipped)
- step-by-step narration comment: // Step 2: Sync posts from API
- step-by-step narration comment: // Step 3: Lint check
- step-by-step narration comment: // Step 4: Next.js build
- step-by-step narration comment: // Step 5: Create deployment summary
- count:assistant_voice
- 0
- count:emoji_in_code
- 147
- count:narrated_steps
- 8
- count:placeholder
- 0
- files:assistant_voice
- 0
- files:emoji_in_code
- 9
- files:narrated_steps
- 3
- files:placeholder
- 0
- index
- 5.32
- lines_scanned
- 15,333
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 9.59
- per_kloc:narrated_steps
- 0.52
- per_kloc:placeholder
- 0
Code quality
35 poor
Code quality is poor: test-to-source ratio 0.00, no CI test run detected; 25% of function code in complex or long functions; 10% duplicated lines. Weakest area: lint.
How the score is built
- Complexity48
- Duplication54
- Lint and smells7
- Tests and CI15
- Documentation40
- Type safety100
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok10 items
- PostsDashboard in components/admin/posts-dashboard.tsx: complexity 41, 192 lines
- exports.handler in functions/aws/files-presigned-url.js: complexity 27, 132 lines
- exports.handler in functions/aws/auth-login.js: complexity 24, 117 lines
- createPost in functions/aws/db.js: complexity 23, 65 lines
- createS3Bucket in aws/scripts/s3-init.js: complexity 21, 111 lines
- normalizeCell in components/admin/posts-dashboard.tsx: complexity 21, 32 lines
- PostsManager in components/post/posts-manager.tsx: complexity 20, 340 lines
- exports.handler in functions/aws/posts-update.js: complexity 19, 175 lines
- (anonymous) in components/ui/matrix-grid-background.tsx: complexity 18, 73 lines
- TerminalTypewriter in components/ui/terminal-typewriter.tsx: complexity 17, 72 lines
- complex_functions
- 13
- function_nloc
- 10,825
- functions
- 739
- long_functions
- 15
- many_param_functions
- 0
- mean_ccn
- 2.64
- p90_ccn
- 6
- risky_nloc_share
- 24.8%
Duplication (jscpd)ok10 items
- 6+ duplicated lines: app/(pages)/posts/blog/page.tsx:13 and app/(pages)/projects/page.tsx:13
- 6+ duplicated lines: app/(pages)/posts/page.tsx:1 and components/editor/visual-editor.tsx:1
- 6+ duplicated lines: app/(pages)/posts/page.tsx:53 and components/post/posts-manager.tsx:197
- 6+ duplicated lines: components/admin/posts-dashboard.tsx:617 and components/admin/posts-dashboard.tsx:645
- 6+ duplicated lines: components/admin/posts-dashboard.tsx:738 and components/post/posts-manager.tsx:518
- 6+ duplicated lines: components/admin/posts-dashboard.tsx:1023 and components/editor/visual-editor.tsx:452
- 6+ duplicated lines: components/files/file-browser.tsx:17 and components/files/file-card.tsx:26
- 6+ duplicated lines: components/files/file-card.tsx:70 and components/files/file-preview.tsx:45
- 6+ duplicated lines: components/files/file-preview.tsx:190 and components/post/file-cell.tsx:133
- 6+ duplicated lines: components/post/article-post-card.tsx:14 and components/post/paper-post-card.tsx:14
- compared_lines
- 10,994
- duplicated_lines
- 1,112
- duplicated_share
- 10.1%
- files
- 120
Lintok
- category:best-practice
- 155
- category:correctness
- 29
- findings
- 184
- scanned_lines
- 15,333
- weighted_findings
- 165
Tests and CIok1 item
- CI config: .github/workflows/deploy.yml
.github/workflows/deploy.yml
- check:ci_present
- yes
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- no
- check:test_ratio
- no
- check:tests_cochange
- no
- ci_files
- 1
- cochange_commits
- 23
- cochange_share
- 0.0%
- source_lines
- 15,333
- test_lines
- 0
- test_ratio
- 0
Documentationok1 item
- README.md
README.md
- check:changelog
- no
- check:contributing
- no
- check:license
- no
- check:readme
- yes
- readme_lines
- 22
Type safetyok1 item
- TypeScript strict type checking: tsconfig.json
tsconfig.json
- check:low_escape_density
- yes
- check:strict_config
- yes
- escapes
- 0
- escapes_per_kloc
- 0
Security
43 poor
Security posture is poor: 225 known vulnerabilities in 51 dependencies; 4 high-severity SAST findings; 11 high-severity workflow issues. Weakest area: posture.
How the score is built
- Secrets90
- Static analysis (SAST)72
- Vulnerable dependencies0
- CI workflows10
- Security posture0
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesok
- checked
- 72
- declared
- 72
- lookup_errors
- 0
- missing
- 0
- recent
- 0
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 0
- secrets_nonprod
- 3
Static analysis (opengrep)ok
- findings
- 44
- findings_high
- 4
- findings_low
- 3
- findings_medium
- 37
- parse_errors
- 0
- scanned_lines
- 15,333
- weighted_findings
- 14.19
Dependencies (osv-scanner)ok
- penalty
- 396
- vulnerabilities
- 225
- vulnerable_packages
- 51
- vulns_critical
- 14
- vulns_high
- 120
- vulns_low
- 12
- vulns_medium
- 79
- vulns_unknown
- 0
CI workflows (zizmor)ok
- findings
- 15
- findings_high
- 11
- findings_low
- 3
- findings_medium
- 1
- penalty
- 136.20
- workflows
- 1
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
14 critical136 high272 medium49 low
471 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| critical | osv/GHSA-23hp-3jrh-7fpw |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-23hp-3jrh-7fpw; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| critical | osv/GHSA-7gfh-x38p-prh3 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-7gfh-x38p-prh3; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| critical | osv/GHSA-hffm-xvc3-vprc |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-hffm-xvc3-vprc; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| critical | osv/GHSA-hrh2-vp3x-79xf |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-hrh2-vp3x-79xf; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| critical | osv/GHSA-m7jm-9gc2-mpf2 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-m7jm-9gc2-mpf2; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| critical | osv/GHSA-mp2f-45pm-3cg9 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-mp2f-45pm-3cg9; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| critical | osv/GHSA-r275-fr43-pm7q |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-r275-fr43-pm7q; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| critical | osv/GHSA-x6jw-m9v5-85vh |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-x6jw-m9v5-85vh; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| critical | osv/GHSA-23hp-3jrh-7fpw |
package-lock.json | [email protected] (npm) is affected by GHSA-23hp-3jrh-7fpw; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| critical | osv/GHSA-2464-fhr4-w9xw |
package-lock.json | [email protected] (npm) is affected by GHSA-2464-fhr4-w9xw; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| critical | osv/GHSA-2xp9-vwfh-vxw4 |
package-lock.json | [email protected] (npm) is affected by GHSA-2xp9-vwfh-vxw4; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| critical | osv/GHSA-9qr9-h5gf-34mp |
package-lock.json | [email protected] (npm) is affected by GHSA-9qr9-h5gf-34mp; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| critical | osv/GHSA-p293-qw3h-jr36 |
package-lock.json | [email protected] (npm) is affected by GHSA-p293-qw3h-jr36; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| critical | osv/GHSA-w7jw-789q-3m8p |
package-lock.json | [email protected] (npm) is affected by GHSA-w7jw-789q-3m8p; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | opengrep/typescript.lang.correctness.useless-ternary |
components/post/video-cell.tsx:20 | It looks like no matter how provider === "vimeo" is evaluated, this expression returns "16/9". This is probably a copy-paste error. | Lint |
| high | zizmor/unpinned-uses |
.github/workflows/deploy.yml:100 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/excessive-permissions |
.github/workflows/deploy.yml:33 | overly broad permissions [confidence high] | CI workflows (zizmor) |
| high | zizmor/excessive-permissions |
.github/workflows/deploy.yml:34 | overly broad permissions [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/deploy.yml:49 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/deploy.yml:52 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/deploy.yml:57 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | zizmor/template-injection |
.github/workflows/deploy.yml:80 | code injection via template expansion [confidence high] | CI workflows (zizmor) |
| high | zizmor/template-injection |
.github/workflows/deploy.yml:81 | code injection via template expansion [confidence high] | CI workflows (zizmor) |
| high | zizmor/template-injection |
.github/workflows/deploy.yml:82 | code injection via template expansion [confidence high] | CI workflows (zizmor) |
| high | zizmor/template-injection |
.github/workflows/deploy.yml:83 | code injection via template expansion [confidence high] | CI workflows (zizmor) |
| high | zizmor/unpinned-uses |
.github/workflows/deploy.yml:87 | unpinned action reference [confidence high] | CI workflows (zizmor) |
| high | opengrep/dockerfile.security.missing-user |
functions/aws/Dockerfile:20 | By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile... | Static analysis (opengrep) |
| high | osv/GHSA-23c5-xmqv-rm74 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-23c5-xmqv-rm74; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-23c5-xmqv-rm74 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-23c5-xmqv-rm74; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-2883-xcg3-v3hh |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-2883-xcg3-v3hh; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-2883-xcg3-v3hh |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-2883-xcg3-v3hh; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-34x7-hfp2-rc4v |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-34x7-hfp2-rc4v; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-35jp-ww65-95wh |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-35jp-ww65-95wh; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-36hh-x5p5-jgc8 |
functions/aws/package-lock.json | @hapi/[email protected] (npm) is affected by GHSA-36hh-x5p5-jgc8; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-37qj-frw5-hhjh |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-37qj-frw5-hhjh; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-3g43-6gmg-66jw |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-3g43-6gmg-66jw; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-3jxr-9vmj-r5cp |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-3jxr-9vmj-r5cp; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-3jxr-9vmj-r5cp |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-3jxr-9vmj-r5cp; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-3ppc-4f35-3m26 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-3ppc-4f35-3m26; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-3ppc-4f35-3m26 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-3ppc-4f35-3m26; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-43fc-jf86-j433 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-43fc-jf86-j433; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-4c8g-83qw-93j6 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-4c8g-83qw-93j6; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-4hjh-wcwx-xvwj |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-4hjh-wcwx-xvwj; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-52cp-r559-cp3m |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-52cp-r559-cp3m; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-52cp-r559-cp3m |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-52cp-r559-cp3m; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-5p4m-2wfm-xmqj |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-5p4m-2wfm-xmqj; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-5p4m-2wfm-xmqj |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-5p4m-2wfm-xmqj; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-62hf-57xw-28j9 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-62hf-57xw-28j9; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-6chq-wfr3-2hj9 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-6chq-wfr3-2hj9; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-6j4f-fj2g-mc7p |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-6j4f-fj2g-mc7p; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-6j4f-fj2g-mc7p |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-6j4f-fj2g-mc7p; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-777c-7fjr-54vf |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-777c-7fjr-54vf; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-7p8r-x3mc-p8w7 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-7p8r-x3mc-p8w7; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-7q85-xj36-vmfc |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-7q85-xj36-vmfc; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-7r86-cg39-jmmj |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-7r86-cg39-jmmj; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-7r86-cg39-jmmj |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-7r86-cg39-jmmj; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-8238-w5pm-2374 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-8238-w5pm-2374; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-83g3-92jg-28cx |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-83g3-92jg-28cx; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-8494-f6mr-cjpv |
functions/aws/package-lock.json | @hapi/[email protected] (npm) is affected by GHSA-8494-f6mr-cjpv; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-858h-whjf-mvg5 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-858h-whjf-mvg5; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-869p-cjfg-cm3x |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-869p-cjfg-cm3x; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-8gc5-j5rx-235r |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-8gc5-j5rx-235r; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-8qq5-rm4j-mr97 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-8qq5-rm4j-mr97; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-8x88-c5mf-7j5w |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-8x88-c5mf-7j5w; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-96hv-2xvq-fx4p |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-96hv-2xvq-fx4p; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-96hv-2xvq-fx4p |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-96hv-2xvq-fx4p; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-9ppj-qmqm-q256 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-9ppj-qmqm-q256; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-c2c7-rcm5-vvqj |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-c2c7-rcm5-vvqj; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-f65p-4m7j-42xc |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-f65p-4m7j-42xc; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-g4wm-2vf7-vfgr |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-g4wm-2vf7-vfgr; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-hfxv-24rg-xrqf |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-hfxv-24rg-xrqf; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-hmw2-7cc7-3qxx |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-hmw2-7cc7-3qxx; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-j5f4-cc29-5x44 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-j5f4-cc29-5x44; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-j5f8-grm9-p9fc |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-j5f8-grm9-p9fc; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-j658-c2gf-x6pq |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-j658-c2gf-x6pq; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-jcxm-m3jx-f287 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-jcxm-m3jx-f287; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-jg4p-7fhp-p32p |
functions/aws/package-lock.json | @hapi/[email protected] (npm) is affected by GHSA-jg4p-7fhp-p32p; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-jmr7-xgp7-cmfj |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-jmr7-xgp7-cmfj; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-jqff-g426-hqxp |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-jqff-g426-hqxp; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-mh99-v99m-4gvg |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-mh99-v99m-4gvg; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-mh99-v99m-4gvg |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-mh99-v99m-4gvg; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-p92q-9vqr-4j8v |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-p92q-9vqr-4j8v; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-pf86-5x62-jrwf |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-pf86-5x62-jrwf; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-pmwg-cvhr-8vh7 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-pmwg-cvhr-8vh7; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-q3j6-qgpj-74h6 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-q3j6-qgpj-74h6; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-q8qp-cvcw-x6jj |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-q8qp-cvcw-x6jj; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-qffp-2rhf-9h96 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-qffp-2rhf-9h96; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-qhr7-859c-m2p7 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-qhr7-859c-m2p7; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-qhr7-859c-m2p7 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-qhr7-859c-m2p7; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-qw65-cvwx-89v3 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-qw65-cvwx-89v3; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-r292-9mhp-454m |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-r292-9mhp-454m; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-r5fr-rjxr-66jc |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-r5fr-rjxr-66jc; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-r6q2-hw4h-h46w |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-r6q2-hw4h-h46w; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-rcw4-f5rp-g42v |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-rcw4-f5rp-g42v; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-rgw5-rvv9-x895 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-rgw5-rvv9-x895; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-rgw5-rvv9-x895 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-rgw5-rvv9-x895; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-v2hh-gcrm-f6hx |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-v2hh-gcrm-f6hx; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-v39h-62p7-jpjc |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-v39h-62p7-jpjc; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-w5hq-g745-h8pq |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-w5hq-g745-h8pq; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-w5hq-g745-h8pq |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-w5hq-g745-h8pq; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-w5hq-g745-h8pq |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-w5hq-g745-h8pq; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-wm7h-9275-46v2 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-wm7h-9275-46v2; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-xcpc-8h2w-3j85 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-xcpc-8h2w-3j85; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-23c5-xmqv-rm74 |
package-lock.json | [email protected] (npm) is affected by GHSA-23c5-xmqv-rm74; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-25h7-pfq9-p65f |
package-lock.json | [email protected] (npm) is affected by GHSA-25h7-pfq9-p65f; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-267c-6grr-h53f |
package-lock.json | [email protected] (npm) is affected by GHSA-267c-6grr-h53f; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-26hh-7cqf-hhc6 |
package-lock.json | [email protected] (npm) is affected by GHSA-26hh-7cqf-hhc6; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-28wg-ghj8-5hjv |
package-lock.json | [email protected] (npm) is affected by GHSA-28wg-ghj8-5hjv; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-28wg-ghj8-5hjv |
package-lock.json | [email protected] (npm) is affected by GHSA-28wg-ghj8-5hjv; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-2v37-7h3g-55p8 |
package-lock.json | [email protected] (npm) is affected by GHSA-2v37-7h3g-55p8; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-2v37-7h3g-55p8 |
package-lock.json | [email protected] (npm) is affected by GHSA-2v37-7h3g-55p8; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-34x7-hfp2-rc4v |
package-lock.json | [email protected] (npm) is affected by GHSA-34x7-hfp2-rc4v; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-36qx-fr4f-26g5 |
package-lock.json | [email protected] (npm) is affected by GHSA-36qx-fr4f-26g5; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-395f-4hp3-45gv |
package-lock.json | [email protected] (npm) is affected by GHSA-395f-4hp3-45gv; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-3ppc-4f35-3m26 |
package-lock.json | [email protected] (npm) is affected by GHSA-3ppc-4f35-3m26; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-68fv-2mgg-jv7q |
package-lock.json | [email protected] (npm) is affected by GHSA-68fv-2mgg-jv7q; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-6g55-p6wh-862q |
package-lock.json | [email protected] (npm) is affected by GHSA-6g55-p6wh-862q; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-6g55-p6wh-862q |
package-lock.json | [email protected] (npm) is affected by GHSA-6g55-p6wh-862q; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-7r86-cg39-jmmj |
package-lock.json | [email protected] (npm) is affected by GHSA-7r86-cg39-jmmj; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-83g3-92jg-28cx |
package-lock.json | [email protected] (npm) is affected by GHSA-83g3-92jg-28cx; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-89xv-2m56-2m9x |
package-lock.json | [email protected] (npm) is affected by GHSA-89xv-2m56-2m9x; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-8h8q-6873-q5fj |
package-lock.json | [email protected] (npm) is affected by GHSA-8h8q-6873-q5fj; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-8qq5-rm4j-mr97 |
package-lock.json | [email protected] (npm) is affected by GHSA-8qq5-rm4j-mr97; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-8x88-c5mf-7j5w |
package-lock.json | [email protected] (npm) is affected by GHSA-8x88-c5mf-7j5w; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-9ppj-qmqm-q256 |
package-lock.json | [email protected] (npm) is affected by GHSA-9ppj-qmqm-q256; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-c2c7-rcm5-vvqj |
package-lock.json | [email protected] (npm) is affected by GHSA-c2c7-rcm5-vvqj; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-c4j6-fc7j-m34r |
package-lock.json | [email protected] (npm) is affected by GHSA-c4j6-fc7j-m34r; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-f88m-g3jw-g9cj |
package-lock.json | [email protected] (npm) is affected by GHSA-f88m-g3jw-g9cj; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-h25m-26qc-wcjf |
package-lock.json | [email protected] (npm) is affected by GHSA-h25m-26qc-wcjf; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-m99w-x7hq-7vfj |
package-lock.json | [email protected] (npm) is affected by GHSA-m99w-x7hq-7vfj; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-mg66-mrh9-m8jx |
package-lock.json | [email protected] (npm) is affected by GHSA-mg66-mrh9-m8jx; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-mrhx-c7xc-m3w5 |
package-lock.json | [email protected] (npm) is affected by GHSA-mrhx-c7xc-m3w5; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-mwv6-3258-q52c |
package-lock.json | [email protected] (npm) is affected by GHSA-mwv6-3258-q52c; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-p3m5-59mp-jv5r |
package-lock.json | [email protected] (npm) is affected by GHSA-p3m5-59mp-jv5r; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-p9j2-gv94-2wf4 |
package-lock.json | [email protected] (npm) is affected by GHSA-p9j2-gv94-2wf4; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-px8p-9vwx-vf98 |
package-lock.json | [email protected] (npm) is affected by GHSA-px8p-9vwx-vf98; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-q4gf-8mx6-v5v3 |
package-lock.json | [email protected] (npm) is affected by GHSA-q4gf-8mx6-v5v3; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-qffp-2rhf-9h96 |
package-lock.json | [email protected] (npm) is affected by GHSA-qffp-2rhf-9h96; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-r28c-9q8g-f849 |
package-lock.json | [email protected] (npm) is affected by GHSA-r28c-9q8g-f849; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-r28c-9q8g-f849 |
package-lock.json | [email protected] (npm) is affected by GHSA-r28c-9q8g-f849; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-r292-9mhp-454m |
package-lock.json | [email protected] (npm) is affected by GHSA-r292-9mhp-454m; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-r6q2-hw4h-h46w |
package-lock.json | [email protected] (npm) is affected by GHSA-r6q2-hw4h-h46w; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-rf6f-7fwh-wjgh |
package-lock.json | [email protected] (npm) is affected by GHSA-rf6f-7fwh-wjgh; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-rgj7-g3m4-5g8c |
package-lock.json | [email protected] (npm) is affected by GHSA-rgj7-g3m4-5g8c; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-wq5f-xc86-pv6w |
package-lock.json | [email protected] (npm) is affected by GHSA-wq5f-xc86-pv6w; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-xwg4-73v4-xw9w |
package-lock.json | [email protected] (npm) is affected by GHSA-xwg4-73v4-xw9w; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | osv/GHSA-xwg4-73v4-xw9w |
package-lock.json | [email protected] (npm) is affected by GHSA-xwg4-73v4-xw9w; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| high | opengrep/javascript.lang.security.detect-child-process |
scripts/deploy-gh-pages.js:19 | Detected calls to child_process from a function argument `command`. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly... | Static analysis (opengrep) |
| high | opengrep/javascript.lang.security.detect-child-process |
scripts/deploy-gh-pages.js:35 | Detected calls to child_process from a function argument `command`. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly... | Static analysis (opengrep) |
| high | opengrep/javascript.lang.security.detect-child-process |
scripts/deploy.js:19 | Detected calls to child_process from a function argument `command`. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly... | Static analysis (opengrep) |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/editor/visual-editor.tsx:136 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/editor/visual-editor.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/editor/visual-editor.tsx:145 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/post/markdown-cell.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/post/markdown-cell.tsx:134 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/post/markdown-cell.tsx:146 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/post/markdown-cell.tsx:273 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/post/markdown-cell.tsx:294 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/post/markdown-cell.tsx:304 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/post/markdown-cell.tsx:312 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/post/markdown-cell.tsx:320 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/post/markdown-cell.tsx:328 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/post/markdown-cell.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/post/markdown-cell.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/post/markdown-cell.tsx:66 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/post/markdown-cell.tsx:72 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/post/markdown-cell.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/post/markdown-cell.tsx:88 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/post/markdown-cell.tsx:96 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/post/post-cell.tsx:55 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
components/post/posts-manager.tsx:244 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/javascript.lang.best-practice.javascript-confirm |
components/post/posts-manager.tsx:267 | found confirm() call; should this be in production code? | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/accordion.tsx:12 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/accordion.tsx:23 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/accordion.tsx:41 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/accordion.tsx:59 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/alert.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/alert.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.tsx:66 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/avatar.tsx:19 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/avatar.tsx:32 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/avatar.tsx:48 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/badge.tsx:41 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/button.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:13 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/card.tsx:26 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/card.tsx:36 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/card.tsx:46 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/card.tsx:59 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/card.tsx:69 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/card.tsx:79 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dialog.tsx:101 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dialog.tsx:114 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dialog.tsx:12 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dialog.tsx:127 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dialog.tsx:18 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dialog.tsx:24 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dialog.tsx:30 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dialog.tsx:44 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dialog.tsx:66 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dialog.tsx:88 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/drawer.tsx:106 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/drawer.tsx:11 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/drawer.tsx:119 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/drawer.tsx:17 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/drawer.tsx:23 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/drawer.tsx:29 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/drawer.tsx:43 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/drawer.tsx:66 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/drawer.tsx:83 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/drawer.tsx:93 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:117 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:12 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:134 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:161 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:174 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:19 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:190 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:198 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:217 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:236 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:29 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:48 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:58 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:80 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/dropdown-menu.tsx:99 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/form.tsx:102 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/form.tsx:120 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/form.tsx:133 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/form.tsx:151 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/form.tsx:40 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/form.tsx:84 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/hover-card.tsx:11 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/hover-card.tsx:18 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/hover-card.tsx:38 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/input.tsx:16 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/label.tsx:19 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:109 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:128 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:152 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:179 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:192 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:20 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:208 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:216 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:235 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:254 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:28 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:34 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:40 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:47 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:62 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/menubar.tsx:85 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/navigation-menu.tsx:118 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to 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:135 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to 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: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/navigation-menu.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/navigation-menu.tsx:43 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/navigation-menu.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/navigation-menu.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/navigation-menu.tsx:97 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to 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:11 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/popover.tsx:17 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/popover.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/popover.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/progress.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/radio-group.tsx:17 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/radio-group.tsx:33 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/select.tsx:113 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/select.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/select.tsx:133 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/select.tsx:149 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/select.tsx:167 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/select.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/select.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/select.tsx:43 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/select.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/select.tsx:96 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/separator.tsx:23 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/sheet.tsx:10 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/sheet.tsx:112 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/sheet.tsx:125 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/sheet.tsx:16 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/sheet.tsx:22 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/sheet.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/sheet.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/sheet.tsx:72 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/sheet.tsx:89 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/sheet.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/sonner.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/switch.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/table.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/table.tsx:16 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/table.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/table.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/table.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/table.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/table.tsx:76 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/table.tsx:89 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/tabs.tsx:16 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/tabs.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/tabs.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/tabs.tsx:61 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/textarea.tsx:13 | It's best practice to explicitly pass props to an HTML component rather than use the spread operator. The spread operator risks passing invalid HTML props to an HTML element, which can cause console warnings or worse, give malicious... | Lint |
| medium | opengrep/typescript.react.best-practice.react-props-spreading |
components/ui/toggle.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 | zizmor/artipacked |
.github/workflows/deploy.yml:48 | credential persistence through GitHub Actions artifacts [confidence low] | CI workflows (zizmor) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
components/admin/posts-dashboard.tsx:239 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.unsafe-dynamic-method |
components/admin/posts-dashboard.tsx:255 | Using non-static data to retrieve and run functions from the object is dangerous. If the data is user-controlled, it may allow executing arbitrary code. [confidence low] | Static analysis (opengrep) |
| medium | opengrep/typescript.react.security.audit.react-dangerouslysetinnerhtml |
components/ui/code-block.tsx:47 | Detection of dangerouslySetInnerHTML from non-constant definition. This can inadvertently expose users to cross-site scripting (XSS) attacks if this comes from user-provided input. If you have to use dangerouslySetInnerHTML, consider... | Static analysis (opengrep) |
| medium | opengrep/typescript.react.security.audit.react-dangerouslysetinnerhtml |
components/ui/server-code-block.tsx:41 | Detection of dangerouslySetInnerHTML from non-constant definition. This can inadvertently expose users to cross-site scripting (XSS) attacks if this comes from user-provided input. If you have to use dangerouslySetInnerHTML, consider... | Static analysis (opengrep) |
| medium | osv/GHSA-2g4f-4pwh-qvx6 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-2g4f-4pwh-qvx6; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-3p68-rc4w-qgx5 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-3p68-rc4w-qgx5; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-3v7f-55p6-f55p |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-3v7f-55p6-f55p; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-3w6x-2g7m-8v23 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-3w6x-2g7m-8v23; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-42h9-826w-cgv3 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-42h9-826w-cgv3; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-445q-vr5w-6q77 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-445q-vr5w-6q77; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-4mjr-xmp4-gh2g |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-4mjr-xmp4-gh2g; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-58qx-3vcg-4xpx |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-58qx-3vcg-4xpx; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-5c9x-8gcm-mpgx |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-5c9x-8gcm-mpgx; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-5v7r-6r5c-r473 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-5v7r-6r5c-r473; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-6pq8-jhm2-2vcw |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-6pq8-jhm2-2vcw; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-6rw7-vpxm-498p |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-6rw7-vpxm-498p; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-7q8q-rj6j-mhjq |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-7q8q-rj6j-mhjq; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-898c-q2cr-xwhg |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-898c-q2cr-xwhg; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-9fr6-4gfg-395g |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-9fr6-4gfg-395g; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-c6fg-446q-cg94 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-c6fg-446q-cg94; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-f886-m6hf-6m8v |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-f886-m6hf-6m8v; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-f886-m6hf-6m8v |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-f886-m6hf-6m8v; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-fvcv-3m26-pcqx |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-fvcv-3m26-pcqx; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-gh4j-gqv2-49f6 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-gh4j-gqv2-49f6; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-gvwx-54wh-qm9j |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-gvwx-54wh-qm9j; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-h39j-r5qq-r9mm |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-h39j-r5qq-r9mm; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-h67p-54hq-rp68 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-h67p-54hq-rp68; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-h67p-54hq-rp68 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-h67p-54hq-rp68; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-hrr3-gc8f-f4qj |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-hrr3-gc8f-f4qj; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-j8rh-479h-cp32 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-j8rh-479h-cp32; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-jp2q-39xq-3w4g |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-jp2q-39xq-3w4g; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-jqh4-m9w3-8hp9 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-jqh4-m9w3-8hp9; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-jwp9-9v96-94mx |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-jwp9-9v96-94mx; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-m7pr-hjqh-92cm |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-m7pr-hjqh-92cm; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-mh29-5h37-fv8m |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-mh29-5h37-fv8m; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-mh29-5h37-fv8m |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-mh29-5h37-fv8m; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-mmx7-hfxf-jppx |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-mmx7-hfxf-jppx; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-p634-w6r4-rjp2 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-p634-w6r4-rjp2; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-pmv8-rq9r-6j72 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-pmv8-rq9r-6j72; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-q2hr-2g5m-vwhr |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-q2hr-2g5m-vwhr; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-q2hr-2g5m-vwhr |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-q2hr-2g5m-vwhr; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-q8mj-m7cp-5q26 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-q8mj-m7cp-5q26; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-r4q5-vmmm-2653 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-r4q5-vmmm-2653; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-vf2m-468p-8v99 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-vf2m-468p-8v99; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-vh66-26gq-q6x8 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-vh66-26gq-q6x8; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-vhjm-w67q-g75c |
functions/aws/package-lock.json | @hapi/[email protected] (npm) is affected by GHSA-vhjm-w67q-g75c; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-vmf3-w455-68vh |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-vmf3-w455-68vh; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-vwc7-r8mq-g2x9 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-vwc7-r8mq-g2x9; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-w74x-v6f9-j3xg |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-w74x-v6f9-j3xg; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-w8wr-v893-vjvp |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-w8wr-v893-vjvp; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-w9j2-pvgh-6h63 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-w9j2-pvgh-6h63; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-x426-x7cc-3fpc |
functions/aws/package-lock.json | @hapi/[email protected] (npm) is affected by GHSA-x426-x7cc-3fpc; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-xx6v-rp6x-q39c |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-xx6v-rp6x-q39c; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-xxjr-mmjv-4gpg |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-xxjr-mmjv-4gpg; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-2g4f-4pwh-qvx6 |
package-lock.json | [email protected] (npm) is affected by GHSA-2g4f-4pwh-qvx6; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-3v7f-55p6-f55p |
package-lock.json | [email protected] (npm) is affected by GHSA-3v7f-55p6-f55p; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-3x4c-7xq6-9pq8 |
package-lock.json | [email protected] (npm) is affected by GHSA-3x4c-7xq6-9pq8; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-4342-x723-ch2f |
package-lock.json | [email protected] (npm) is affected by GHSA-4342-x723-ch2f; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-4633-3j49-mh5q |
package-lock.json | [email protected] (npm) is affected by GHSA-4633-3j49-mh5q; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-4c39-4ccg-62r3 |
package-lock.json | [email protected] (npm) is affected by GHSA-4c39-4ccg-62r3; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-4jqv-mc3x-m676 |
package-lock.json | [email protected] (npm) is affected by GHSA-4jqv-mc3x-m676; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-68g3-v927-f742 |
package-lock.json | [email protected] (npm) is affected by GHSA-68g3-v927-f742; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-955p-x3mx-jcvp |
package-lock.json | [email protected] (npm) is affected by GHSA-955p-x3mx-jcvp; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-9g9p-9gw9-jx7f |
package-lock.json | [email protected] (npm) is affected by GHSA-9g9p-9gw9-jx7f; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-ffhc-5mcf-pf4q |
package-lock.json | [email protected] (npm) is affected by GHSA-ffhc-5mcf-pf4q; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-fxqj-rqcc-2cmp |
package-lock.json | [email protected] (npm) is affected by GHSA-fxqj-rqcc-2cmp; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-fxqj-rqcc-2cmp |
package-lock.json | [email protected] (npm) is affected by GHSA-fxqj-rqcc-2cmp; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-g3hv-75wg-m249 |
package-lock.json | [email protected] (npm) is affected by GHSA-g3hv-75wg-m249; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-g5qg-72qw-gw5v |
package-lock.json | [email protected] (npm) is affected by GHSA-g5qg-72qw-gw5v; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-ggv3-7p47-pfv8 |
package-lock.json | [email protected] (npm) is affected by GHSA-ggv3-7p47-pfv8; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-gvwx-54wh-qm9j |
package-lock.json | [email protected] (npm) is affected by GHSA-gvwx-54wh-qm9j; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-gx5p-jg67-6x7h |
package-lock.json | [email protected] (npm) is affected by GHSA-gx5p-jg67-6x7h; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-h64f-5h5j-jqjh |
package-lock.json | [email protected] (npm) is affected by GHSA-h64f-5h5j-jqjh; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-mcj8-r9mp-w47p |
package-lock.json | [email protected] (npm) is affected by GHSA-mcj8-r9mp-w47p; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-p498-v437-472g |
package-lock.json | @humanfs/[email protected] (npm) is affected by GHSA-p498-v437-472g; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-qx2v-qp2m-jg93 |
package-lock.json | [email protected] (npm) is affected by GHSA-qx2v-qp2m-jg93; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-qx2v-qp2m-jg93 |
package-lock.json | [email protected] (npm) is affected by GHSA-qx2v-qp2m-jg93; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-vmf3-w455-68vh |
package-lock.json | [email protected] (npm) is affected by GHSA-vmf3-w455-68vh; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-w37m-7fhw-fmv9 |
package-lock.json | [email protected] (npm) is affected by GHSA-w37m-7fhw-fmv9; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-w8wr-v893-vjvp |
package-lock.json | [email protected] (npm) is affected by GHSA-w8wr-v893-vjvp; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-wfc6-r584-vfw7 |
package-lock.json | [email protected] (npm) is affected by GHSA-wfc6-r584-vfw7; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-x7hr-w5r2-h6wg |
package-lock.json | [email protected] (npm) is affected by GHSA-x7hr-w5r2-h6wg; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | osv/GHSA-xv57-4mr9-wg8v |
package-lock.json | [email protected] (npm) is affected by GHSA-xv57-4mr9-wg8v; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| medium | opengrep/javascript.lang.security.audit.path-traversal.path-join-resolve-traversal |
scripts/build-posts.js:247 | Detected possible user input going into a `path.join` or `path.resolve` function. This could possibly lead to a path traversal vulnerability, where the attacker can access arbitrary files stored in the file system. Instead, be sure to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/build-posts.js:248 | Detected that function argument `versionTag` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.path-traversal.path-join-resolve-traversal |
scripts/build-posts.js:264 | Detected possible user input going into a `path.join` or `path.resolve` function. This could possibly lead to a path traversal vulnerability, where the attacker can access arbitrary files stored in the file system. Instead, be sure to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/build-posts.js:265 | Detected that function argument `versionTag` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.path-traversal.path-join-resolve-traversal |
scripts/build-posts.js:297 | Detected possible user input going into a `path.join` or `path.resolve` function. This could possibly lead to a path traversal vulnerability, where the attacker can access arbitrary files stored in the file system. Instead, be sure to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/build-posts.js:300 | Detected that function argument `versionTag` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.path-traversal.path-join-resolve-traversal |
scripts/build-posts.js:316 | Detected possible user input going into a `path.join` or `path.resolve` function. This could possibly lead to a path traversal vulnerability, where the attacker can access arbitrary files stored in the file system. Instead, be sure to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/build-posts.js:317 | Detected that function argument `file` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.path-traversal.path-join-resolve-traversal |
scripts/build-posts.js:317 | Detected possible user input going into a `path.join` or `path.resolve` function. This could possibly lead to a path traversal vulnerability, where the attacker can access arbitrary files stored in the file system. Instead, be sure to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/build-posts.js:325 | Detected that function argument `file` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/build-posts.js:331 | Detected that function argument `file` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/build-posts.js:332 | Detected that function argument `file` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/deploy-gh-pages.js:43 | Detected that function argument `dir` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/deploy-gh-pages.js:44 | Detected that function argument `dir` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/deploy-gh-pages.js:46 | Detected that function argument `dir` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.path-traversal.path-join-resolve-traversal |
scripts/deploy-gh-pages.js:46 | Detected possible user input going into a `path.join` or `path.resolve` function. This could possibly lead to a path traversal vulnerability, where the attacker can access arbitrary files stored in the file system. Instead, be sure to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.path-traversal.path-join-resolve-traversal |
scripts/deploy-gh-pages.js:46 | Detected possible user input going into a `path.join` or `path.resolve` function. This could possibly lead to a path traversal vulnerability, where the attacker can access arbitrary files stored in the file system. Instead, be sure to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/deploy-gh-pages.js:51 | Detected that function argument `target` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/deploy-gh-pages.js:52 | Detected that function argument `source` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.path-traversal.path-join-resolve-traversal |
scripts/deploy-gh-pages.js:53 | Detected possible user input going into a `path.join` or `path.resolve` function. This could possibly lead to a path traversal vulnerability, where the attacker can access arbitrary files stored in the file system. Instead, be sure to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.path-traversal.path-join-resolve-traversal |
scripts/deploy-gh-pages.js:53 | Detected possible user input going into a `path.join` or `path.resolve` function. This could possibly lead to a path traversal vulnerability, where the attacker can access arbitrary files stored in the file system. Instead, be sure to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.path-traversal.path-join-resolve-traversal |
scripts/deploy-gh-pages.js:54 | Detected possible user input going into a `path.join` or `path.resolve` function. This could possibly lead to a path traversal vulnerability, where the attacker can access arbitrary files stored in the file system. Instead, be sure to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.path-traversal.path-join-resolve-traversal |
scripts/deploy-gh-pages.js:54 | Detected possible user input going into a `path.join` or `path.resolve` function. This could possibly lead to a path traversal vulnerability, where the attacker can access arbitrary files stored in the file system. Instead, be sure to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/deploy-gh-pages.js:58 | Detected that function argument `source` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/deploy-gh-pages.js:58 | Detected that function argument `source` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/deploy-gh-pages.js:58 | Detected that function argument `target` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/deploy-gh-pages.js:60 | Detected that function argument `source` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/deploy-gh-pages.js:60 | Detected that function argument `source` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/deploy-gh-pages.js:60 | Detected that function argument `target` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.path-traversal.path-join-resolve-traversal |
scripts/versions.js:21 | Detected possible user input going into a `path.join` or `path.resolve` function. This could possibly lead to a path traversal vulnerability, where the attacker can access arbitrary files stored in the file system. Instead, be sure to... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/versions.js:22 | Detected that function argument `file` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/versions.js:27 | Detected that function argument `file` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| medium | opengrep/javascript.lang.security.audit.detect-non-literal-fs-filename |
scripts/versions.js:29 | Detected that function argument `file` has entered the fs module. An attacker could potentially control the location of this file, to include going backwards in the directory with '../'. To address this, ensure that user-controlled... | Static analysis (opengrep) |
| low | opengrep/javascript.lang.correctness.useless-assignment |
aws/scripts/check-aws.js:1 | `const` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
aws/scripts/check-aws.js:2 | `const` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
aws/scripts/check-aws.js:3 | `const` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
aws/scripts/dynamodb-init.js:1 | `const` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
aws/scripts/dynamodb-init.js:2 | `const` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/isovalues-shader-background.tsx:104 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/isovalues-shader-background.tsx:104 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/isovalues-shader-background.tsx:115 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/isovalues-shader-background.tsx:115 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/matrix-grid-background.tsx:245 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/matrix-grid-background.tsx:245 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/matrix-grid-background.tsx:253 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/matrix-grid-background.tsx:253 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/volumetric-shader-background.tsx:91 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/volumetric-shader-background.tsx:91 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/volumetric-shader-background.tsx:99 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/volumetric-shader-background.tsx:99 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/warp-fbm-background.tsx:62 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/warp-fbm-background.tsx:62 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/warp-fbm-background.tsx:70 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
components/ui/warp-fbm-background.tsx:70 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
functions/aws/db.js:1 | `const` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
functions/aws/files-presigned-url.js:1 | `const` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
functions/aws/posts-create.js:1 | `const` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
functions/aws/posts-delete.js:1 | `const` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
functions/aws/posts-update.js:1 | `const` is assigned twice; the first assignment is useless | Lint |
| low | opengrep/javascript.lang.correctness.missing-template-string-indicator |
scripts/build-posts.js:226 | This looks like a JavaScript template string. Are you missing a '$' in front of '{...}'? | Lint |
| low | opengrep/javascript.lang.correctness.useless-assignment |
scripts/deploy.js:8 | `const` is assigned twice; the first assignment is useless | Lint |
| low | zizmor/unsound-ternary |
.github/workflows/deploy.yml:70 | unsound pseudo-ternary expression [confidence high] | CI workflows (zizmor) |
| low | zizmor/unsound-ternary |
.github/workflows/deploy.yml:72 | unsound pseudo-ternary expression [confidence high] | CI workflows (zizmor) |
| low | zizmor/unsound-ternary |
.github/workflows/deploy.yml:73 | unsound pseudo-ternary expression [confidence high] | CI workflows (zizmor) |
| low | gitleaks/generic-api-key |
aws/env/.env.example:12 | Possible generic-api-key secret in the current tree (test/docs/example file) | Secrets (gitleaks) |
| low | gitleaks/curl-auth-header |
docs/features/POSTS_SYSTEM.md:258 | Possible curl-auth-header secret in history (commit 5921f29b71); removed from the current tree but still retrievable | Secrets (gitleaks) |
| low | gitleaks/curl-auth-header |
functions/aws/README.md:141 | Possible curl-auth-header secret in the current tree (test/docs/example file) | Secrets (gitleaks) |
| low | opengrep/javascript.lang.security.audit.unsafe-formatstring |
functions/aws/files-list.js:106 | 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 |
functions/aws/files-upload.js:166 | 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-333x-w4r6-6crp |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-333x-w4r6-6crp; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| low | osv/GHSA-474x-hrwr-fgx4 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-474x-hrwr-fgx4; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| low | osv/GHSA-6475-r3vj-m8vf |
functions/aws/package-lock.json | @smithy/[email protected] (npm) is affected by GHSA-6475-r3vj-m8vf; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| low | osv/GHSA-fj3w-jwp8-x2g3 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-fj3w-jwp8-x2g3; also in package-lock.json; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| low | osv/GHSA-j965-2qgj-vjmq |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-j965-2qgj-vjmq; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| low | osv/GHSA-w7fw-mjwx-w883 |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-w7fw-mjwx-w883; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| low | osv/GHSA-xhjh-pmcv-23jw |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-xhjh-pmcv-23jw; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| low | osv/GHSA-xhq7-xmqj-769h |
functions/aws/package-lock.json | [email protected] (npm) is affected by GHSA-xhq7-xmqj-769h; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| low | opengrep/javascript.lang.security.audit.unsafe-formatstring |
lib/highlight-code.ts:31 | 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 |
package-lock.json | [email protected] (npm) is affected by GHSA-3g8h-86w9-wvmq; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| low | osv/GHSA-vfv6-92ff-j949 |
package-lock.json | [email protected] (npm) is affected by GHSA-vfv6-92ff-j949; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| low | osv/GHSA-xffm-g5w8-qvg7 |
package-lock.json | @eslint/[email protected] (npm) is affected by GHSA-xffm-g5w8-qvg7; also in pnpm-lock.yaml | Dependencies (osv-scanner) |
| low | osv/GHSA-6475-r3vj-m8vf |
pnpm-lock.yaml | @smithy/[email protected] (npm) is affected by GHSA-6475-r3vj-m8vf | 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 | 184 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | ok | — | 0 | |
| CI workflows (zizmor) | Security | ok | zizmor 1.32.0 | 15 | |
| Dependencies (osv-scanner) | Security | ok | osv-scanner version: 2.7.1 | 225 | |
| 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 | 44 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 3 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | 31876aed3ad9 | prov-5+qual-2+sec-2 | 0% | 35 | 43 |
| 2026-11-14 | 31876aed3ad9 | prov-4+qual-2+sec-2 | 0% | 35 | 43 |
Full text report
- Repository: https://github.com/isuryanarayanan/supers
- Commit:
31876aed3ad972af13b6e4c13dbcd17753825104 - Generated: 2026-11-14T14:52:05+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 | 48% | 100% |
| Code quality | 35 | poor | 90% | 100% |
| Security | 43 | poor | 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%
-
AI tooling configured in repo: generic-agent, github-copilot
-
Stylometry index: 5.32 per 1,000 lines (narrated steps 8, placeholders 0, assistant phrasing 0, emoji 147). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2025-08 | 14,894 | 0% |
| 2025-11 | 441 | 0% |
| 2026-01 | 74 | 0% |
| 2026-09 | 3,358 | 0% |
Evidence
- AGENTS.md (generic-agent configuration) (AGENTS.md)
- .github/copilot-instructions.md (github-copilot configuration) (.github/copi)
- step-by-step narration comment: // First, let's check if bucket exists anywhere (aws/scripts/)
- step-by-step narration comment: // Step 1: Get pre-signed URL (lib/file-upl)
- step-by-step narration comment: // Step 2: Upload directly to S3 (lib/file-upl)
- step-by-step narration comment: // Step 1: Pre-build checks (only if not skipped) (scripts/depl)
- step-by-step narration comment: // Step 2: Sync posts from API (scripts/depl)
- step-by-step narration comment: // Step 3: Lint check (scripts/depl)
- step-by-step narration comment: // Step 4: Next.js build (scripts/depl)
- step-by-step narration comment: // Step 5: Create deployment summary (scripts/depl)
AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.
Code quality
Code quality is poor: test-to-source ratio 0.00, no CI test run detected; 25% of function code in complex or long functions; 10% duplicated lines. Weakest area: lint.
| Area | Score |
|---|---|
| Complexity (lizard) | 48 |
| Duplication | 54 |
| Code smells (Opengrep) | 7 |
| Tests and CI | 15 |
| Documentation | 40 |
| Type safety | 100 |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 739; mean complexity 2.6, 90th percentile 6; 13 complex and 15 long functions
- Duplicated lines: 10.1% of 10,994 compared
- Tests: 0 test lines for 15,333 source lines (ratio 0.00); CI test commands: none detected; 0% of recent source commits also change tests
- Docs missing or thin: license, contributing, changelog
Most complex functions:
- PostsDashboard in components/admin/posts-dashboard.tsx: complexity 41, 192 lines
- exports.handler in functions/aws/files-presigned-url.js: complexity 27, 132 lines
- exports.handler in functions/aws/auth-login.js: complexity 24, 117 lines
- createPost in functions/aws/db.js: complexity 23, 65 lines
- createS3Bucket in aws/scripts/s3-init.js: complexity 21, 111 lines
Security
Security posture is poor: 225 known vulnerabilities in 51 dependencies; 4 high-severity SAST findings; 11 high-severity workflow issues. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 90 |
| Static analysis (Opengrep) | 72 |
| Vulnerable dependencies (OSV) | 0 |
| CI workflows (zizmor) | 10 |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
-
Known vulnerabilities: 225 in 51 packages (critical 14, high 120, medium 79, low 12)
-
Posture checks passed: lockfiles; missing: security policy, dependency updates, signed commits
Top findings
| Severity | Finding | Location |
|---|---|---|
| critical | osv/GHSA-hrh2-vp3x-79xf: [email protected] (npm) is affected by GHSA-hrh2-vp3x-79xf; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| critical | osv/GHSA-mp2f-45pm-3cg9: [email protected] (npm) is affected by GHSA-mp2f-45pm-3cg9; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| critical | osv/GHSA-m7jm-9gc2-mpf2: [email protected] (npm) is affected by GHSA-m7jm-9gc2-mpf2; also in package-lock.json; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| critical | osv/GHSA-hffm-xvc3-vprc: [email protected] (npm) is affected by GHSA-hffm-xvc3-vprc; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| critical | osv/GHSA-r275-fr43-pm7q: [email protected] (npm) is affected by GHSA-r275-fr43-pm7q; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| critical | osv/GHSA-x6jw-m9v5-85vh: [email protected] (npm) is affected by GHSA-x6jw-m9v5-85vh; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| critical | osv/GHSA-23hp-3jrh-7fpw: [email protected] (npm) is affected by GHSA-23hp-3jrh-7fpw; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| critical | osv/GHSA-7gfh-x38p-prh3: [email protected] (npm) is affected by GHSA-7gfh-x38p-prh3; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| critical | osv/GHSA-2464-fhr4-w9xw: [email protected] (npm) is affected by GHSA-2464-fhr4-w9xw; also in pnpm-lock.yaml |
package-lock.json |
| critical | osv/GHSA-2xp9-vwfh-vxw4: [email protected] (npm) is affected by GHSA-2xp9-vwfh-vxw4; also in pnpm-lock.yaml |
package-lock.json |
| critical | osv/GHSA-9qr9-h5gf-34mp: [email protected] (npm) is affected by GHSA-9qr9-h5gf-34mp; also in pnpm-lock.yaml |
package-lock.json |
| critical | osv/GHSA-p293-qw3h-jr36: [email protected] (npm) is affected by GHSA-p293-qw3h-jr36; also in pnpm-lock.yaml |
package-lock.json |
| critical | osv/GHSA-w7jw-789q-3m8p: [email protected] (npm) is affected by GHSA-w7jw-789q-3m8p; also in pnpm-lock.yaml |
package-lock.json |
| critical | osv/GHSA-23hp-3jrh-7fpw: [email protected] (npm) is affected by GHSA-23hp-3jrh-7fpw; also in pnpm-lock.yaml |
package-lock.json |
| high | opengrep/dockerfile.security.missing-user: By not specifying a USER, a program in the container may run as 'root'. This is a security hazard. If an attacker can control a process running as root, they may have control over the container. Ensure that the last USER in a Dockerfile is a USER other than 'root'. [confidence medium] |
functions/aws/Dockerfile:20 |
| high | opengrep/javascript.lang.security.detect-child-process: Detected calls to child_process from a function argument command. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly sanitized or sandboxed. [confidence low] |
scripts/deploy-gh-pages.js:19 |
| high | opengrep/javascript.lang.security.detect-child-process: Detected calls to child_process from a function argument command. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly sanitized or sandboxed. [confidence low] |
scripts/deploy-gh-pages.js:35 |
| high | opengrep/javascript.lang.security.detect-child-process: Detected calls to child_process from a function argument command. This could lead to a command injection if the input is user controllable. Try to avoid calls to child_process, and if it is needed ensure user input is correctly sanitized or sandboxed. [confidence low] |
scripts/deploy.js:19 |
| high | osv/GHSA-36hh-x5p5-jgc8: @hapi/[email protected] (npm) is affected by GHSA-36hh-x5p5-jgc8; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| high | osv/GHSA-8494-f6mr-cjpv: @hapi/[email protected] (npm) is affected by GHSA-8494-f6mr-cjpv; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| high | osv/GHSA-jg4p-7fhp-p32p: @hapi/[email protected] (npm) is affected by GHSA-jg4p-7fhp-p32p; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| high | osv/GHSA-7q85-xj36-vmfc: [email protected] (npm) is affected by GHSA-7q85-xj36-vmfc; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| high | osv/GHSA-8238-w5pm-2374: [email protected] (npm) is affected by GHSA-8238-w5pm-2374; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| high | osv/GHSA-j5f4-cc29-5x44: [email protected] (npm) is affected by GHSA-j5f4-cc29-5x44; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
| high | osv/GHSA-rcw4-f5rp-g42v: [email protected] (npm) is affected by GHSA-rcw4-f5rp-g42v; also in pnpm-lock.yaml |
functions/aws/package-lock.json |
Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.
Repository profile
- Source lines: 15,333; test lines: 0
| Language | Lines |
|---|---|
| TypeScript | 11,448 |
| JavaScript | 3,851 |
| Shell | 34 |