pirapira/raiden-services

scanned 2026-08-09 · git 49d0d12

2 of 6 checks flagged a security issue

🔴 Needs attention

Only 3 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secrets7Vulnerable dependencies10Known OSS vulnerabilities—Risky code patterns✓Malicious dependencies—Project health—

Security checks

Leaked secrets — Gitleaksⓘ 7 found

API keys, passwords or tokens committed into the repo.

Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

tests/pathfinding/test_blockchain_integration.py:43

A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

tests/pathfinding/test_cli.py:25

A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

tests/pathfinding/test_cli.py:45

A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

tests/monitoring/monitoring_service/test_cli.py:17

A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

tests/pathfinding/test_blockchain_integration.py:41

A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

tests/pathfinding/fixtures/network_service.py:315

A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.
Worth fixing generic-api-key Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

tests/pathfinding/fixtures/network_service.py:339

A credential (key, password or token) appears in your code. Fix: Remove it, rotate the key, and load it from an environment variable instead.

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 10 found · 1 serious

Packages you depend on that have known security holes (CVEs).

Serious CVE-2023-41419 python-gevent: privilege escalation via a crafted script to the WSGIServer component

requirements.txt

A package you depend on has a known security hole (CVE-2023-41419). Fix: Update that package to its patched version.
Worth fixing GHSA-3qwc-47jf-5rf7 eth-abi is vulnerable to recursive DoS

requirements.txt

A package you depend on has a known security hole (GHSA-3qwc-47jf-5rf7). Fix: Update that package to its patched version.
Worth fixing GHSA-rqr8-pxh7-cq3g Ethereum ABI decoder DoS when parsing ZST

requirements.txt

A package you depend on has a known security hole (GHSA-rqr8-pxh7-cq3g). Fix: Update that package to its patched version.
Worth fixing CVE-2022-1930 Regular expression denial of service in eth-account

requirements.txt

A package you depend on has a known security hole (CVE-2022-1930). Fix: Update that package to its patched version.
Worth fixing CVE-2023-30861 flask: Possible disclosure of permanent session cookie due to missing Vary: Cookie header

requirements.txt

A package you depend on has a known security hole (CVE-2023-30861). Fix: Update that package to its patched version.
Worth fixing CVE-2023-32681 python-requests: Unintended leak of Proxy-Authorization header

requirements.txt

A package you depend on has a known security hole (CVE-2023-32681). Fix: Update that package to its patched version.
Worth fixing CVE-2024-35195 requests: subsequent requests to the same host ignore cert verification

requirements.txt

A package you depend on has a known security hole (CVE-2024-35195). Fix: Update that package to its patched version.
Worth fixing CVE-2024-47081 requests: Requests vulnerable to .netrc credentials leak via malicious URLs

requirements.txt

A package you depend on has a known security hole (CVE-2024-47081). Fix: Update that package to its patched version.
Worth fixing CVE-2026-25645 requests: Requests: Security bypass due to predictable temporary file creation

requirements.txt

A package you depend on has a known security hole (CVE-2026-25645). Fix: Update that package to its patched version.
Minor CVE-2026-27205 flask: Flask: Information disclosure via improper caching of session data

requirements.txt

A package you depend on has a known security hole (CVE-2026-27205). Fix: Update that package to its patched version.

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ timed out

Your dependencies cross-checked against the OSV vulnerability database.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via OSV-Scanner v1.9.2 · Apache-2.0

error: timeout after 400s

Risky code patterns — Semgrepⓘ none found ✓

Code that can be exploited: injection, hardcoded credentials and similar.

Nothing found by this check. ✓

via Semgrep v1.147.0 · LGPL-2.1

Malicious dependencies — Guarddogⓘ timed out

Packages that look intentionally malicious: typosquats, sneaky install scripts.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via Guarddog v2.10.0 · Apache-2.0

error: pypi:timeout

Project health

A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.

Project health — OpenSSF Scorecardⓘ didn’t run

Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via OpenSSF Scorecard · Apache-2.0

About these results. Six open-source checks ran in parallel; every finding is tagged with the tool that produced it. The verdict follows a published rule. False positives and false negatives are normal — a clean scan does not mean the code is secure, and a red verdict does not mean the project is compromised.