Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add benchmark ci + optimize the validate records fk flow #925
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
base: master
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
Add benchmark ci + optimize the validate records fk flow #925
Changes from all commits
aac1b0aafb95fb1d7d3442b55fd01cde35af2885df3902461585b2cc00e3e97fcae9ac07e2f0b81f2fd012962c1de5aab5add32ff8ab56b6e5a3b98File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Check failure on line 44 in .github/workflows/scripts/collect-benchmarks.mts
[Bearer] .github/workflows/scripts/collect-benchmarks.mts#L44 <javascript_lang_logger_leak>(https://docs.bearer.com/reference/rules/javascript_lang_logger_leak)
Raw output
message:"\n# Leakage of information in logger message\n## Description\n\nInformation 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.\n\n## Remediations\n\n- **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.\n ```javascript\n logger.info(`Results: ${data}`) // unsafe\n ```\n- **Do** use logging levels appropriately to control the verbosity of log output and minimize the risk of leaking sensitive information in production environments." location:{path:".github/workflows/scripts/collect-benchmarks.mts" range:{start:{line:44 column:3} end:{line:44 column:62}}} severity:ERROR source:{name:"Bearer" url:"https://docs.bearer.com/"} code:{value:"javascript_lang_logger_leak" url:"https://docs.bearer.com/reference/rules/javascript_lang_logger_leak"}Check failure on line 45 in .github/workflows/scripts/collect-benchmarks.mts
[Bearer] .github/workflows/scripts/collect-benchmarks.mts#L45 <javascript_lang_logger_leak>(https://docs.bearer.com/reference/rules/javascript_lang_logger_leak)
Raw output
message:"\n# Leakage of information in logger message\n## Description\n\nInformation 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.\n\n## Remediations\n\n- **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.\n ```javascript\n logger.info(`Results: ${data}`) // unsafe\n ```\n- **Do** use logging levels appropriately to control the verbosity of log output and minimize the risk of leaking sensitive information in production environments." location:{path:".github/workflows/scripts/collect-benchmarks.mts" range:{start:{line:45 column:3} end:{line:45 column:31}}} severity:ERROR source:{name:"Bearer" url:"https://docs.bearer.com/"} code:{value:"javascript_lang_logger_leak" url:"https://docs.bearer.com/reference/rules/javascript_lang_logger_leak"}Check failure on line 87 in .github/workflows/scripts/collect-benchmarks.mts
[Bearer] .github/workflows/scripts/collect-benchmarks.mts#L87 <javascript_lang_logger_leak>(https://docs.bearer.com/reference/rules/javascript_lang_logger_leak)
Raw output
message:"\n# Leakage of information in logger message\n## Description\n\nInformation 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.\n\n## Remediations\n\n- **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.\n ```javascript\n logger.info(`Results: ${data}`) // unsafe\n ```\n- **Do** use logging levels appropriately to control the verbosity of log output and minimize the risk of leaking sensitive information in production environments." location:{path:".github/workflows/scripts/collect-benchmarks.mts" range:{start:{line:87 column:5} end:{line:87 column:82}}} severity:ERROR source:{name:"Bearer" url:"https://docs.bearer.com/"} code:{value:"javascript_lang_logger_leak" url:"https://docs.bearer.com/reference/rules/javascript_lang_logger_leak"}This file was deleted.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.