-
Notifications
You must be signed in to change notification settings - Fork 5
test #1669
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
test #1669
Conversation
run-unit-tests-and-coverage: Run #2570
🎉 All tests passed!Github Test Reporter by CTRF 💚 |
|
|
||
| try { | ||
| const summaryData = require('../../coverage/coverage-summary.json'); | ||
| console.log('total: ', summaryData.total.lines.total, 'covered', summaryData.total.lines.total); |
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.
🚫 [Bearer] <javascript_lang_logger_leak> reported by reviewdog 🐶
Leakage of information in logger message
Description
Information leakage through logger messages can compromise sensitive data. This vulnerability arises when dynamic data or variables, which may contain sensitive information, are included in log messages.
Remediations
- Do not include sensitive data directly in logger messages. This can lead to the exposure of such data in log files, which might be accessible to unauthorized individuals.
logger.info(`Results: ${data}`) // unsafe
- Do use logging levels appropriately to control the verbosity of log output and minimize the risk of leaking sensitive information in production environments.
|
Coverage: 0.9034749034749034 |
No description provided.