← Back to scan
File as GitHub Issue repo: Uranid/mnem

Push this scan report to Uranid/mnem

Click 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.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

LLM Prompt Injection — User Input in AI Prompt

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
CRIT DKC007 Compose service contains a literal secret environment value benchmarks/harness/compose.yml:61
CRIT DKC007 Compose service contains a literal secret environment value benchmarks/harness/compose.yml:55
CRIT DKC007 Compose service contains a literal secret environment value benchmarks/harness/compose.yml:49
CRIT DKC007 Compose service contains a literal secret environment value benchmarks/harness/compose.yml:43
HIGH SEC016 [SEC016] LLM Prompt Injection — User Input in AI Prompt: User-supplied text is interpolat… crates/mnem-cli/src/commands/retrieve.rs:745
HIGH SUPC001 Supply chain — curl | bash anti-pattern scripts/install.sh:5
HIGH SUPC001 Supply chain — curl | bash anti-pattern scripts/dev-setup.sh:36
HIGH SEC020 [SEC020] Secret Printed to Logs: Debug or diagnostic code appears to print a credential-b… crates/mnem-py/examples/quickstart.py:56
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. npm-packages/mnem-cli/scripts/postinsta…:76
MED SEC012 [SEC012] ZipSlip — Archive Path Traversal: Archive extraction without path validation all… py-packages/mnem-cli/mnem_cli/__init__.…:84
MED DKR003 Compose service `ollama` image uses the latest tag docker-compose.yml:41
MED DKR007 Docker build context has no .dockerignore .dockerignore
MED AIC003 Duplicated implementation block across source files crates/mnem-core/src/objects/sparse_set…:54
MED AIC003 Duplicated implementation block across source files crates/mnem-core/src/objects/operation.…:37
MED AIC003 Duplicated implementation block across source files crates/mnem-core/src/index/vector.rs:127
MED AIC003 Duplicated implementation block across source files crates/mnem-core/benches/retrieve.rs:11
MED AIC003 Duplicated implementation block across source files crates/mnem-cli/src/commands/tag.rs:59
MED AIC003 Duplicated implementation block across source files crates/mnem-cli/src/commands/reindex.rs:158
MED AIC003 Duplicated implementation block across source files crates/mnem-cli/src/commands/push.rs:22
MED AIC003 Duplicated implementation block across source files crates/mnem-cli/src/commands/import.rs:77
MED AIC003 Duplicated implementation block across source files crates/mnem-bench/src/score/membench.rs:125
MED AIC003 Duplicated implementation block across source files crates/mnem-bench/src/score/membench.rs:119
MED AIC003 Duplicated implementation block across source files crates/mnem-bench/src/score/longmemeval…:16
MED AIC003 Duplicated implementation block across source files crates/mnem-bench/src/score/locomo.rs:145
MED LOG001 PII printed to stdout/stderr crates/mnem-py/examples/quickstart.py:57
MED LOG001 PII printed to stdout/stderr crates/mnem-py/examples/quickstart.py:56
MED SUPC002 Supply chain — npm install without lockfile crates/mnem-py/python/pymnem/langchain.…:9
MED SUPC002 Supply chain — npm install without lockfile crates/mnem-py/python/pymnem/crewai.py:8
MED SUPC002 Supply chain — npm install without lockfile crates/mnem-py/python/pymnem/__init__.py:11
MED SUPC002 Supply chain — npm install without lockfile crates/mnem-py/examples/quickstart.py:15
MED CRYP001 Crypto — plaintext HTTP for sensitive endpoint crates/mnem-ingest/src/extract.rs:505
MED CRYP001 Crypto — plaintext HTTP for sensitive endpoint crates/mnem-ingest/src/extract.rs:497
MED CRYP001 Crypto — plaintext HTTP for sensitive endpoint crates/mnem-embed-providers/src/ollama.…:135
MED CRYP001 Crypto — plaintext HTTP for sensitive endpoint crates/mnem-http/src/main.rs:128
MED CRYP001 Crypto — plaintext HTTP for sensitive endpoint crates/mnem-core/src/sparse.rs:222
MED CRYP001 Crypto — plaintext HTTP for sensitive endpoint crates/mnem-core/src/sparse.rs:217
MED AGT015 Remote install command pipes network code directly to a shell scripts/install.sh:5
MED CRYP001 Crypto — plaintext HTTP for sensitive endpoint crates/mnem-http/examples/smoke_client.…:63
MED CRYP001 Crypto — plaintext HTTP for sensitive endpoint crates/mnem-rerank-providers/tests/http…:45
LOW DKC010 Compose service lacks no-new-privileges hardening docker-compose.yml:41
LOW DKC010 Compose service lacks no-new-privileges hardening docker-compose.yml:19
LOW DKC010 Compose service lacks no-new-privileges hardening benchmarks/harness/compose.yml:61
LOW DKC010 Compose service lacks no-new-privileges hardening benchmarks/harness/compose.yml:55
LOW DKC010 Compose service lacks no-new-privileges hardening benchmarks/harness/compose.yml:49
LOW DKC010 Compose service lacks no-new-privileges hardening benchmarks/harness/compose.yml:43
LOW AIC002 Source file name looks like an AI patch artifact crates/mnem-bench/src/score/hybrid_v4.rs:1
LOW DKC006 Compose service does not declare a runtime user docker-compose.yml:41
Reset to top 5 47 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `Uranid/mnem`

**Score: 75/100 (B)**  ·  49 findings  ·  scanned 2026-05-14 22:54 UTC  ·  112,732 LOC

| Severity | Count |
|---|---|
| CRITICAL | 4 |
| HIGH | 4 |
| MEDIUM | 31 |
| LOW | 8 |

📊 [Full filterable report](https://repobility.com/scan/fba39ac8-1e1f-42dc-8c6d-39269bb4d3be/)  ·  ![scorecard](https://repobility.com/scan/fba39ac8-1e1f-42dc-8c6d-39269bb4d3be/report.png?v=1778799262-s2)

### Top findings

1. **CRITICAL** `DKC007` — Compose service contains a literal secret environment value
   `benchmarks/harness/compose.yml:61`
2. **CRITICAL** `DKC007` — Compose service contains a literal secret environment value
   `benchmarks/harness/compose.yml:55`
3. **CRITICAL** `DKC007` — Compose service contains a literal secret environment value
   `benchmarks/harness/compose.yml:49`
4. **CRITICAL** `DKC007` — Compose service contains a literal secret environment value
   `benchmarks/harness/compose.yml:43`
5. **HIGH** `SEC016` — LLM Prompt Injection — User Input in AI Prompt
   `crates/mnem-cli/src/commands/retrieve.rs:745`

---

**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/fba39ac8-1e1f-42dc-8c6d-39269bb4d3be/_
Already filed
This repo publishes a SECURITY.md policy and the scan contains 2 Critical/High security finding(s). Public issue filing would violate coordinated disclosure. Submit privately via the project's security reporting channel.
Megaproject â high spam risk
Could not determine 'Uranid/mnem' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
Already filed
16/49 findings (33%) on this scan are already flagged as test-file, won't-fix, or suppressed. The scan is too noisy to file as a single issue. Curate down to specific actionable findings, or address the FP source first.
I read the warnings â override Cancel

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.