Skip to content

test: validate QWED Security v1.1 scanner across all engines - #214

Closed
Rahul Dass (rahuldass19) wants to merge 9 commits into
mainfrom
test/qwed-security-v11
Closed

test: validate QWED Security v1.1 scanner across all engines#214
Rahul Dass (rahuldass19) wants to merge 9 commits into
mainfrom
test/qwed-security-v11

test: re-check runtime secret regex

840b0fb
Select commit
Loading
Failed to load commit list.
GitHub Advanced Security / QWED Security failed Jul 27, 2026 in 5s

5 new alerts including 1 error

New alerts in code changed by this pull request

  • 1 error
  • 4 warnings

See annotations below for details.

View all branch alerts.

Annotations

Check failure on line 3 in src/qwed_new/runtime_secret_demo.py

See this annotation in the file changed.

Code scanning / QWED Security

Hardcoded credential-like material detected. Error

Hardcoded credential-like material detected. Context=RUNTIME_CODE. Decision: Executable runtime path contains a dangerous pattern.

Check warning on line 3 in examples/qwed_security_test.py

See this annotation in the file changed.

Code scanning / QWED Security

Hardcoded credential-like material detected. Warning

Hardcoded credential-like material detected. Context=DEMO_CODE. Decision: Credential-like pattern in demo code with non-production value.

Check warning on line 13 in examples/qwed_security_test.py

See this annotation in the file changed.

Code scanning / QWED Security

Dangerous eval() call can execute untrusted code. Warning

Dangerous eval() call can execute untrusted code. Context=DEMO_CODE. Decision: Pattern detected in demo/example code; surfaced as advisory.

Check warning on line 13 in examples/qwed_security_test.py

See this annotation in the file changed.

Code scanning / QWED Security

DYNAMIC_EXECUTION_BOUNDARY violation: eval enables arbitrary code execution. Warning

DYNAMIC_EXECUTION_BOUNDARY violation: eval enables arbitrary code execution. Context=DEMO_CODE. Decision: Pattern detected in demo/example code; surfaced as advisory.

Check warning on line 13 in examples/qwed_security_test.py

See this annotation in the file changed.

Code scanning / QWED Security

TAINT_FLOW_BOUNDARY violation: Tainted data from input reaches eval -- Remote code execution. Flow: input -> expression Warning

TAINT_FLOW_BOUNDARY violation: Tainted data from input reaches eval -- Remote code execution. Flow: input -> expression Context=DEMO_CODE. Decision: Pattern detected in demo/example code; surfaced as advisory.