Unused imports cause risks in code

Production RiskSoftware ResiliencyCode Reliability

Unused imports cause risks in code

This code insight counts one violation each time a import is nerver used.

Why you should care

Usually, when this issue is encountered, it means that you began implementing a module but did not finish it. Other times, you might have refactored a module, but you forgot to remove the import statement. Treat this issue as a warning and review the module in question.

Business Impacts

Production Risk

CAST recommendations




About CAST and Highlight’s Code Insights

Over the last 25 years, CAST has leveraged unique knowledge on software quality measurement by analyzing thousands of applications and billions of lines of code. Based on this experience and community standards on programming best practices, Highlight implements hundreds of code insights across 15+ technologies to calculate health factors of a software.

See featuresHow it works