-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JS-359 Create rule S6418 (hardcoded-secrets
): Hard-coded secrets are security-sensitive (broken)
#4920
Conversation
hardcoded-secrets
): secrets should not be hardcodedhardcoded-secrets
): Hard-coded secrets are security-sensitive
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great overall, but there are a few things to address.
...lugin/javascript-checks/src/main/java/org/sonar/javascript/checks/HardcodedSecretsCheck.java
Outdated
Show resolved
Hide resolved
...n/javascript-checks/src/main/resources/org/sonar/l10n/javascript/rules/javascript/S6418.html
Show resolved
Hide resolved
.../javascript-checks/src/test/java/org/sonar/javascript/checks/HardcodedPasswordCheckTest.java
Show resolved
Hide resolved
Co-authored-by: Yassin Kammoun <52890329+yassin-kammoun-sonarsource@users.noreply.github.com>
…t because I find no way to use hyphens in the Java check
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job!
Quality Gate passedIssues Measures |
hardcoded-secrets
): Hard-coded secrets are security-sensitivehardcoded-secrets
): Hard-coded secrets are security-sensitive (broken)
Based on the sonar-python S6418 rule.
RSPEC PR
JS-359
Other ticket tackling S2068