Added check for debug true in Django

[pkalyankumar1010]

DEBUG = True cannot be used in production in django framework.
When DEBUG = True is enabled in Django, the framework provides detailed error messages, stack traces, and sensitive information about your application. While useful for development, this setting is dangerous in production because:

❌ Risks of DEBUG = True in Production

• Sensitive Data Exposure

  • Django displays full error traces and environment variables, which might include database credentials, API keys, or secret tokens.

• Security Vulnerabilities

  • Debug mode allows detailed error pages that could help attackers find weaknesses in your application.
  • It can expose internal file paths and configuration details.

• Performance Issues

  • Debug mode can slow down your app by enabling extra logging and debugging tools that aren't needed in production.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Comments	Updated (UTC)
globstar	⬜️ Ignored (Inspect)	Visit Preview		Feb 27, 2025 1:27pm

[MashyBasker]

Typo in include field name

[sourya-deepsource]

This will not work on the analysis runtime given the way the test runner is implemented. Since we look for an individual file rule-name.test.extension, settings.py will never match the pattern. Here is the related issue: #159.

[sourya-deepsource]

Even the first DEBUG, in line no. 2, should not raise an issue, since it is overwritten in line no. 4. You'd have to implement the checker in Go in order to check for the last DEBUG. You might also want to look for DEBUG statements inside conditional blocks.