Identified Risks
This table shows all the identified risks for this repository.
Filename | Message | Scanner |
|---|---|---|
Dockerfile | Ensure that HEALTHCHECK instructions have been added to container images | iac |
leaks-baseline.json | Base64 High Entropy String | iac |
leaks-baseline.json | Base64 High Entropy String | iac |
.github/workflows/devguard-scanner.yaml | Ensure top-level permissions are not set to write-all | iac |
leaks-baseline.json | generic-api-key has detected secret for file leaks-baseline.json at commit bfebd20d65fae35103346f93b78e273bbc8d290e. | secret-scanning |
leaks-baseline.json | generic-api-key has detected secret for file leaks-baseline.json at commit bfebd20d65fae35103346f93b78e273bbc8d290e. | secret-scanning |
leaks-baseline.json | generic-api-key has detected secret for file leaks-baseline.json at commit bfebd20d65fae35103346f93b78e273bbc8d290e. | secret-scanning |
leaks-baseline.json | generic-api-key has detected secret for file leaks-baseline.json at commit 0b6d3d075c8002f30f62e2d1b020df40d26fd26d. | secret-scanning |
leaks-baseline.json | generic-api-key has detected secret for file leaks-baseline.json at commit 0b6d3d075c8002f30f62e2d1b020df40d26fd26d. | secret-scanning |
leaks-baseline.json | generic-api-key has detected secret for file leaks-baseline.json at commit 0b6d3d075c8002f30f62e2d1b020df40d26fd26d. | secret-scanning |
README.md | generic-api-key has detected secret for file README.md at commit 31d68f10860c6023c74a8abed76a0ee777e33293. | secret-scanning |
README.md | generic-api-key has detected secret for file README.md at commit 31d68f10860c6023c74a8abed76a0ee777e33293. | secret-scanning |
README.md | generic-api-key has detected secret for file README.md at commit 9ad5299c96380a18e52dd8d8f08f4b1d890b7258. | secret-scanning |
/github/workspace/src/components/common/CopyCode.tsx | RegExp() called with a `props` function argument, this might allow an attacker to cause a Regular Expression Denial-of-Service (ReDoS) within your application as RegExP blocks the main thread. For this reason, it is recommended to use hardcoded regexes instead. If your regex is run on user-controlled input, consider performing input validation or use a regex checking/sanitization library such as https://www.npmjs.com/package/recheck to verify that the regex does not appear vulnerable to ReDoS. | sast |
Showing 1 of 1 pages (14 items)