Ability to create configuration policy templates for certain settings (Quality Gates, Ignore Rules, Reporting) and allow users to apply them to the subset of repositories. This intends to allow teams to manage multiple DeepSource configurations in buckets without repeating the effort and also have a single place to audit their current configuration.

This is a known issue that the search on file names doesn't work as expected from the Issues tab. Only searching by the issue's shortcode seems to work. We're looking into how we can improve this.

A new repository metric that tracks the lines of code in the repository.

Currently, users have to deactivate and activate analysis from the repository's settings. Enable users to re-run full analysis without disrupting the flow.

A new repository metric to track the code's cyclomatic complexity.

We're working on the analysis for 3rd-party packages in a repository to report the licenses used and alert if a harmful license is found.

Scanning of 3rd-party packages used in a repository to highlight potentially vulnerable packages.

A new repository metric to track code duplications in the repository.

We're exploring ways to support Software Bill of Materials(SBOM) reporting to help our users better understand the open-source and 3rd party components they use in their codebase.

We're enhancing DeepSource's Secrets Analyzer to provide users with a more comprehensive and reliable solution for identifying and securing sensitive data.

We're working on building capabilities for our users to extend DeepSource and better suit their needs regarding managing their code health. With Macros, users can create their Analyzers on DeepSource with custom issues.

To enhance the security of the users' data, we are working on implementing IP whitelisting in DeepSource for Enterprise Cloud users. With this feature, admins will be able to restrict access to the platform by allowing only specific IP addresses to connect. This will prevent unauthorized access from unknown sources and give users more control over who can access their code.

We are exploring ways to report areas of a codebase with high churn that lack sufficient test coverage. This will help users identify and prioritize areas of their codebase that require more thorough testing, thereby improving code quality and reducing potential issues.

Currently, code coverage is only reported for programming languages supported by DeepSource. We're working on expanding code coverage support to include all programming languages.

Access audit logs from our GraphQL API.

Trigger DeepSource on a branch you're working on or Autofix issues directly from IntelliJ IDEA.