emcie-co/parlant
emcie-co/parlantClick 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.
No Repobility access matrix policy found
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `emcie-co/parlant` **Score: 73/100 (A-)** · 27 findings · scanned 2026-05-16 09:47 UTC · 138,641 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 2 | | MEDIUM | 21 | | LOW | 2 | 📊 [Full filterable report](https://repobility.com/scan/00d57213-51b2-4fdb-9000-c77d21e631e2/) ·  ### Top findings 1. **HIGH** `DKR006` — Dockerfile pipes a remote script into a shell `.devcontainer/Dockerfile:39` 2. **HIGH** `SEC004` — SQL Injection Risk `src/parlant/adapters/db/snowflake_db.py:427` · A03:2021 Injection 3. **MEDIUM** `ERR001` — Silent Exception Swallowing `src/parlant/adapters/nlp/azure_service.py:592` 4. **MEDIUM** `ERR001` — Silent Exception Swallowing `src/parlant/adapters/vector_db/qdrant.py:350` 5. **MEDIUM** `AUC001` — No Repobility access matrix policy found CWE-285 · WSTG-AUTHZ --- **Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately. --- _Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/00d57213-51b2-4fdb-9000-c77d21e631e2/_
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.