Scoring System

Core Features
3 min read

Scoring System

Every ThinkReview analysis includes four metrics scored from 0 to 100. These scores provide a high-level health check for your code changes.

MetricWhat it measures
OverallA holistic assessment of the code's health and readiness.
Code QualityClarity, maintainability, and structural integrity.
SecurityIdentification of potential vulnerabilities and risks.
Best PracticesAdherence to language idioms and industry standards.
## How Scores are Calculated

Our AI analyzes your code based on standard software engineering principles, but you can also influence the focus of the review through your settings.

Security Score


The Security score is highly sensitive to potential risks:
  • Starting Point: Every review starts at 100.

  • Deductions: We deduct 15 points for every unique security issue identified (e.g., SQL injection, exposed secrets, insecure logic).

  • Criticality: A security score below 70 should be considered a "Blocker" for merging.

    • Scoring Calibration


    In your account settings, you can select specific Security Checks and Best Practice Guidelines. When these are selected, the system:
  • Injects specific instructions into the AI's review prompt.

  • Prioritizes those concerns during analysis.

  • Applies stricter scoring penalties if those specific rules are violated.

    • Understanding the Ranges

  • 85 - 100 (Excellent): The code is solid and adheres to best practices. Ready for merge.

  • 70 - 84 (Good): Minor improvements are suggested. Merging is usually safe but review the feedback.

  • 50 - 69 (Needs Work): Contains noticeable issues that should be addressed before the PR is approved.

  • 0 - 49 (Critical): Significant security risks or poor code quality detected. Action is required immediately.

Pro Tips for Better Scores

  • Fix Security First: A single security vulnerability can tank your overall score. Address these findings immediately.

  • Read the Feedback: Scores are just indicators. The real value is in the Suggestions and Best Practices lists provided with the review.

  • Calibrate: Use the settings portal to tell ThinkReview what your team cares about most. This makes the scores more relevant to your specific project.

  • Iterate: After fixing issues, use the Refresh button or push a new commit to see your scores improve.

    • TL;DR: Scores (0-100) help you quickly judge code health. Security issues carry heavy penalties (-15 pts each). You can calibrate what the AI looks for in your settings to get more accurate scores.