fix : replace SELECT * with explicit columns in data-export

[tmdeveloper007]

fix : replace SELECT * with explicit columns in data-export

[vercel]

@TESTPERSONAL is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

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

[Priyanshu-byte-coder]

Security issue: The explicit column list for user_github_accounts includes access_token:

.select("id, user_id, github_id, github_login, access_token, created_at")

This exports the plaintext OAuth token in the user data export. Remove access_token from the select list. Only include non-sensitive fields.

[Priyanshu-byte-coder]

Security issue blocks this merge:

user_github_accounts select still exposes access_token
Line: .select("id, user_id, github_id, github_login, access_token, created_at")

This was the vulnerability this PR (and our earlier fix in commit 435d85f) was meant to address. The current main branch already has this corrected to:

.select("id, user_id, github_id, github_login, created_at")

Please remove access_token from that select. The rest of the explicit column changes (goals, metric_snapshots, streak_freezes, streak_milestones, local_coding_sessions) are all correct.

Also please rebase on main first — the current data-export/route.ts has already been partially updated.

[vercel]

Deployment failed with the following error:

The provided GitHub repository does not contain the requested branch or commit reference. Please ensure the repository is not empty.

[tmdeveloper007]

This pull request is fully up-to-date with the latest upstream merges, all review items are addressed, local tests are passing cleanly, and it is fully ready to be merged! 🚀