-
Notifications
You must be signed in to change notification settings - Fork 0
Known Issues
onfire7777 edited this page Jun 29, 2026
·
1 revision
These notes were captured during the Goal 1–3 consolidation so that future cleanup doesn't re-introduce removed bloat or mistake intentional structure for redundancy.
Source: docs/KNOWN_ISSUES.md
Some per-skill vendoring is deliberate self-containment, verified during the refactor. Git stores identical blobs once, so the on-disk repetition is not a storage cost:
| What | Scope | Why it's intentional |
|---|---|---|
canvas-fonts |
vendored per skill (~4 skills × 54 files) | Keeps each canvas/design skill runnable standalone, without a shared font dependency. |
| OOXML / XSD schemas | vendored per skill (~5 skills × 39 files) | Keeps document-generation skills self-contained. |
Warning
Don't "deduplicate" these. They are preserved on purpose; removing them breaks the skills' standalone runnability.
-
infrastructure/mcp-bridges/bridge_context_mode.ps1previously launched Node via the full pathC:\Program Files\nodejs\node.exe, which could space-split the-Commandargument undermcp-proxy. Fixed (2026-06-17): the invocation now uses the 8.3 short pathC:\PROGRA~1\nodejs\node.exe.
skills/onefilellm/references/ pins onefilellm's upstream dependency set.
Resolved 2026-06-17:
| Package | Bump | Advisory |
|---|---|---|
yt-dlp |
2026.3.17 → 2026.6.9 |
GHSA-f7j3-774f-rfhj (cookie leak) |
bleach |
6.3.0 → 6.4.0 |
GHSA-8rfp-98v4-mmr6 (URI sanitization) + GHSA-g75f-g53v-794x (linkify CPU exhaustion, ==6.3.0 only) |
Accepted risk (no upstream fix available):
-
nltk==3.9.4— GHSA-p4gq-832x-fm9v (URL-encoded path traversal innltk.data.load()), severity High.3.9.4is the latest release; no patched version exists. onefilellm uses NLTK only for stopword removal via the hardcodedstopwordscorpus name — it never passes untrusted input tonltk.data.load(), so the vulnerable path is not reachable in this usage. The Dependabot alert was dismissed as tolerable risk; it will be bumped as soon as upstream ships a fix.
- Security — reporting and secret handling
- Testing & CI — the gates that protect against regressions
- Skills Corpus — why some vendoring is intentional
Getting started
Concepts
Reference
Project
- Roadmap & Phases
- Node → Go Migration
- Performance & Benchmarks
- Testing & CI
- Contributing
- Security
- Known Issues
Help