Dart static code analysis

Filtered: 17 rules found

cwe

Impact

Clean code attribute

Exposing native code through JavaScript interfaces is security-sensitive
Security Hotspot
Pubspec urls should be secure
Vulnerability
Enabling JavaScript support for WebViews is security-sensitive
Security Hotspot
Cipher algorithms should be robust
Vulnerability
Encryption algorithms should be used with secure mode and padding scheme
Vulnerability
Using clear-text protocols is security-sensitive
Security Hotspot
Accessing Android external storage is security-sensitive
Security Hotspot
Server certificates should be verified during SSL/TLS connections
Vulnerability
Using weak hashing algorithms is security-sensitive
Security Hotspot
Exceptions should not be ignored
Code Smell
Using pseudorandom number generators (PRNGs) is security-sensitive
Security Hotspot
Code annotated as deprecated should not be used
Code Smell
Unused assignments should be removed
Code Smell
"==" operator and "hashCode()" should be overridden in pairs
Bug
Jump statements should not occur in "finally" blocks
Bug
Track uses of "TODO" tags
Code Smell
Track uses of "FIXME" tags
Code Smell

Track uses of "FIXME" tags

intentionality - complete

maintainability

Code Smell

FIXME tags are commonly used to mark places where a bug is suspected, but which the developer wants to deal with later.

Sometimes the developer will not have the time or will simply forget to get back to that tag.

This rule is meant to track those tags and to ensure that they do not go unnoticed.

// FIXME denominator value might be 0
int divide(int numerator, int denominator) {
  return numerator / denominator;
}

Available In: