July 2019 (version 1.27.0)

1.27.0 Update


Welcome to the new DeepScan updates.

While DeepScan focuses on the capability of analysis beyond lint, many users still want to use also ESLint because of its custom-defined rule sets and plugins. To date, we have been hard at work helping organizations using ESLint manage the results of both tools.

We are very happy to announce the integration of ESLint with DeepScan in this update!

Please kindly go ahead with the highlights for the latest release.

Release Summary

This version includes a number of updates that we hope you've found some of them helpful.
The key highlights are:

ESLint Integration

While DeepScan is focusing on the capability beyond lint, many users still want to use ESLint for checking code styles and by its useful plugins.

Now you can analyze your projects with both DeepScan and ESLint and see the results altogether from our dashboard.

By default, this feature is disabled. To enable it, please check on the Enable ESLint option in the project settings and re-analyze.

Then, you can see the issues detected by both tools and filter those by specific analysis engine.

ESLint Issues

As of identical issues detected by both, you can merge those issues according to your preferences (preferring either DeepScan, ESLint, or both).

For further information, please see our Guide for Using ESLint.

Key Statistics in the Team Dashboard

We got a fresh new Key Statistics to make it easier to understand the team's quality status.

Now, you can see the following statistics in the Team Dashboard:

  • Top Risky Projects: 5 highest projects with multiple issues of high or medium impact
  • Top Violated Rules: 5 highest rules that occur most frequently throughout all team projects
  • Top LoC Projects: 5 highest projects with many lines of code

You can use these statistics to determine projects or issues which can be focused on with higher priority.

Team Dashboard: Key Statistics

New Rules

We have enhanced our React rules with the function components and Hooks.

Check the new rules!

Improved Rules


  • Analyze the return value of React useMemo and useCallback Hooks
  • Better recognition of setState() calls inside React class component
  • Change some NON_REFERENCE_LHS alarms to SYNTAX_ERROR alarms
  • Do not detect REACT_USELESS_PROP_TYPES alarms when the component does not have valid render() function

Bug Fixes

  • A false alarm for REACT_USELESS_PROP_TYPES may occur when the prop is directly used as JSX tag name
  • Analyzer abnormally terminates when && operator is used at _.isUndefined() argument
  • TypeScript this parameter is not properly distinguished from normal parameters