Skip to main content
Unlike Core analyzers, Community analyzers do not run on DeepSource’s infrastructure. Instead, they are run on CI systems and the results are reported to DeepSource. This approach allows you to use DeepSource with a broader range of technologies and languages, and manage the issues in a centralized dashboard. Furthermore, this integration enables you to leverage DeepSource’s features such as Quality Gates, Issue diffing, ignore rules setup, for the issues identified by these Community Analyzers.

​
Supported Analyzers

AnalyzerVersionShortcodeRepository
AWS CloudFormation0.83.0cfn-linthttps://github.com/aws-cloudformation/cfn-lint
Dart Analyze3.2.0dart-analyzehttps://github.com/dart-lang/sdk/tree/main/pkg/linter
Kube Linter0.6.4kube-linterhttps://github.com/stackrox/kube-linter
Slither0.10.0slitherhttps://github.com/crytic/slither
Solhint4.1.1solhinthttps://github.com/protofire/solhint
Issues detected by these analyzers can be found in the Analyzer Directory under the respective analyzer. For suggestions regarding additional analyzers you’d like DeepSource to support, please submit your request at roadmap.deepsource.com. We regularly review these submissions and consider them as we update our product roadmap.

​
Setting up Community Analyzers on your repository

Incorporating Community Analyzers into your workflow is a simple process.
  1. Begin by adding the analyzer into your .deepsource.toml configuration file. This step is akin to activating core analyzers in DeepSource.
  2. Set up the DEEPSOURCE_DSN environment variable within your Continuous Integration (CI) system.
  3. Finally, integrate the analyzer into your CI system. For your convenience, we provide pre-formulated CI snippets for all major CI systems. Simply select and insert the appropriate snippet for the respective analyzer from the Analyzer Directory into your chosen CI system’s configuration.
Let’s go through these steps in detail. Community Analyzers accepts SARIF report and syncs the issues from the report on DeepSource. The SARIF report can be generated by running the analyzer on your CI pipeline.
  1. Enable the analyzer by adding it to your repository’s .deepsource.toml config file. For example, if you want to enable Dart Analyze on your project, add the following to your .deepsource.toml file:
    toml
    [[analyzers]]
name = "dart-analyze"
type = "community"
    We recommend you perform this action from your dashboard by navigating to the respective Repository → Settings → Configuration and then clicking on the Regenerate Configuration button. In case, you are activating a repository for the first time, please use the Activate a repository feature from your team’s dashboard.
    The following steps can only be performed after activating a repository. In case, you are activating a repository for the first time, please commit the configuration first before continuing.
  2. Set up DEEPSOURCE_DSN environment variable for the project in your CI/CD pipeline. The DSN is used to associate the analysis report to the repository. This needs to be configured before sending the analysis report to DeepSource. To look up the DSN:
    1. Go to the Settings page of the repository dashboard in DeepSource
    2. Go to the General tab
    3. Click on Copy button to copy your DSN mentioned under Data Source Name (DSN)