fix: Remove excessive console logging in server.ts

[saidai-bhuvanesh]

Issue #2: Excessive Console Logging in Production

Severity: MEDIUM

Category: Security / Code Quality

File Location

server.ts - Lines 425, 429, 502, 607, 618, 635, 676, 680, 692, 750, 753, 762, 802, and more

Problem Description

Multiple console.log statements throughout the server.ts file can leak sensitive information in production environments. These logs may expose:

• Request/response data
• File processing details
• User information
• Internal system details

Evidence

console.log("Firebase admin initialized from FIREBASE_SERVICE_ACCOUNT");
console.log(`${new Date().toISOString()} - ${req.method} ${req.url}`);
console.log("=== PDF INGESTION START ===");

Security Impact

• Information disclosure in production logs
• May expose sensitive user data
• Violates OWASP security logging guidelines
• Makes debugging harder in production

Root Cause

Debug logging statements left in production code without proper log levels or environment checks.

Recommended Fix

1. Remove all console.log statements in production code
2. Implement proper logging with levels (error, warn, info, debug)
3. Use environment checks to control logging:

const LOG_LEVEL = process.env.LOG_LEVEL || "error";
if (LOG_LEVEL === "debug") console.log("debug info");

Testing

1. Verify no sensitive data in production logs
2. Ensure important errors still logged
3. Check all endpoints for excessive logging

Estimated Effort: Medium (2-3 hours)

Confidence: 100%

Summary

• Added a gaxios override to require uuid 11.1.1 or newer.
• Updated gaxios, file-type, and nodemailer.
• Added uuid as a development dependency.
• Addressed vulnerabilities reported by npm audit.

[github-actions]

Thank you for your contribution!

To keep reviews manageable and maintain repository quality, contributors may have a maximum of 3 open Issues and 3 open Pull Requests at any given time.

Please wait until one of your existing submissions is reviewed or closed before opening additional ones.

If you believe this was closed by mistake, feel free to contact the maintainers.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 3772a484-be2e-4677-8937-64326668143e

📥 Commits

Reviewing files that changed from the base of the PR and between 32c4e5c and 733ecaf.

⛔ Files ignored due to path filters (1)

• backend/package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• backend/package.json

---

📝 Walkthrough

Walkthrough

The backend package manifest adds gaxios and uuid, upgrades file-type and nodemailer, and enforces uuid version 11.1.1 or newer for gaxios.

Changes

Backend dependency alignment

Layer / File(s)	Summary
Dependency manifest updates backend/package.json	The manifest adds gaxios and uuid, upgrades file-type and nodemailer, and adds an npm override for gaxios to use uuid 11.1.1 or newer.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

• Canopus-Labs/PrepPilot#1352: Contains the same dependency and gaxios override changes.
• Canopus-Labs/PrepPilot#1354: Applies the same dependency and override changes in backend/package.json.

Suggested reviewers: karanunique

✨ Finishing Touches 💡 1

⚔️ Resolve merge conflicts 💡

• Resolve merge conflict in branch fix/excessive-console-logging

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}