buildingjoshbetter/TrueMemory
buildingjoshbetter/TrueMemoryClick 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.
Silent Exception Swallowing
Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.
## Code-quality scan: `buildingjoshbetter/TrueMemory` **Score: 86/100 (B+)** · 27 findings · scanned 2026-05-15 06:14 UTC · 36,839 LOC | Severity | Count | |---|---| | CRITICAL | 0 | | HIGH | 4 | | MEDIUM | 18 | | LOW | 0 | 📊 [Full filterable report](https://repobility.com/scan/493756b5-9d72-4a48-88a4-dd14a9704063/) ·  ### Top findings 1. **HIGH** `SEC004` — SQL Injection Risk `truememory/storage.py:342` · A03:2021 Injection 2. **HIGH** `SEC016` — LLM Prompt Injection — User Input in AI Prompt `truememory/engine.py:1972` 3. **HIGH** `SEC004` — SQL Injection Risk `truememory/temporal.py:553` · A03:2021 Injection 4. **HIGH** `AGT002` — LLM memory extraction can be prompt-injected into storing fake facts `truememory/ingest/models.py:391` 5. **MEDIUM** `ERR001` — Silent Exception Swallowing `truememory/telemetry.py:84` --- **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/493756b5-9d72-4a48-88a4-dd14a9704063/_
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.