DataDog/datadog-api-client-python
DataDog/datadog-api-client-pythonClick the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.
This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.
Weak Crypto
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `DataDog/datadog-api-client-python` **Score: 94/100 (A-)** · 17 findings · scanned 2026-06-05 14:22 UTC · 17,959 LOC | Severity | Count | |---|---| | CRITICAL | 3 | | HIGH | 5 | | MEDIUM | 7 | | LOW | 0 | 📊 [Full filterable report](https://repobility.com/scan/efffaa4d-098b-4955-a5e8-f06a3af25d85/) ·  ### Top findings 1. **CRITICAL** `MINED116` — Workflow uses `secrets.DD_CLIENT_APP_KEY` on a `pull_request` trigger `.github/workflows/reusable-integration-test.yml:124` · ✓ Repobility 2. **CRITICAL** `MINED116` — Workflow uses `secrets.DD_CLIENT_API_KEY` on a `pull_request` trigger `.github/workflows/reusable-integration-test.yml:123` · ✓ Repobility 3. **CRITICAL** `MINED116` — Workflow uses `secrets.DD_API_KEY` on a `pull_request` trigger `.github/workflows/reusable-integration-test.yml:77` · ✓ Repobility 4. **HIGH** `MINED108` — `self.double_emphasis` used but never assigned in __init__ `.generator/src/generator/formatter.py:165` · ✓ Repobility 5. **HIGH** `MINED004` — Weak Crypto `examples/v1/synthetics/CreateSyntheticsAPITest_1987645492.py:104` · CWE-327 · ✓ Repobility --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/efffaa4d-098b-4955-a5e8-f06a3af25d85/_
The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.
For real security findings on big repos: use the project's SECURITY.md or
private advisory flow instead of a public issue.