Skip to content

chore: enable DeepSource javascript analyzer - #3503

Open
Priyanshu-byte-coder wants to merge 2 commits into
mainfrom
chore/deepsource-config
Open

chore: enable DeepSource javascript analyzer#3503
Priyanshu-byte-coder wants to merge 2 commits into
mainfrom
chore/deepsource-config

Conversation

@Priyanshu-byte-coder

Copy link
Copy Markdown
Owner

DeepSource was activated on this repo but no .deepsource.toml existed, so only the secrets analyzer ran. Both analysis runs reported FAILURE and the 35 findings surfaced were all in docs, test fixtures and playwright configs.

Enables the javascript analyzer with the react plugin and typescript dialect so DeepSource actually analyses src/.

Claude-Session: https://claude.ai/code/session_012ML3xbVUA9NjDJzAB71qVc

Summary

Closes #


Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 💥 Breaking change (fix or feature that changes existing behavior)
  • 📝 Documentation update
  • ♻️ Refactor / code cleanup (no functional change)
  • ⚡ Performance improvement
  • 🔒 Security fix
  • 🧪 Tests only

What Changed


How to Test

Expected result:


Screenshots / Recordings

Before After

Checklist

  • Linked the related issue above
  • Self-reviewed my own diff
  • No unnecessary console.log, debug code, or commented-out blocks
  • npm run lint passes locally
  • No TypeScript errors (npm run type-check)
  • Added or updated tests where applicable
  • Updated documentation / comments if behavior changed

Accessibility (UI changes only)

  • Keyboard navigation works correctly
  • Color contrast meets WCAG AA standard
  • ARIA labels / roles added where needed
  • Tested on mobile / responsive layout

Additional Context

DeepSource was activated on this repo but no .deepsource.toml existed, so
only the secrets analyzer ran. Both analysis runs reported FAILURE and the
35 findings surfaced were all in docs, test fixtures and playwright configs.

Enables the javascript analyzer with the react plugin and typescript dialect
so DeepSource actually analyses src/.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012ML3xbVUA9NjDJzAB71qVc
@deepsource-io

deepsource-io Bot commented Aug 19, 2026

Copy link
Copy Markdown

DeepSource Code Review

We reviewed changes in c10c207...048362a on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Security  

Reliability  

Complexity  

Hygiene  

Code Review Summary

Analyzer Status Updated (UTC) Details
Secrets Aug 21, 2026 8:10a.m. Review ↗

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

@github-actions github-actions Bot added the gssoc26 GSSoC 2026 contribution label Aug 19, 2026
@github-actions

Copy link
Copy Markdown

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

  • level:beginner — 20 pts
  • level:intermediate — 35 pts
  • level:advanced — 55 pts
  • level:critical — 80 pts

Quality (optional):

  • quality:clean — ×1.2 multiplier
  • quality:exceptional — ×1.5 multiplier

Validation (required to score):

  • gssoc:approved — counts for points
  • gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus

The SonarCloud scanner writes .scannerwork/ (.sonar_lock, report-task.txt) into
the repo root on a local run. It was untracked but not ignored, so a `git add -A`
would sweep scanner scratch into a commit.

Sits next to the existing .jscpd-report/ entry, which covers the same class of
local analysis output.
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

gssoc26 GSSoC 2026 contribution

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant