lmzhen/dsh-evolution--packages-evolution-threat ↗★ 1
@deepseek-ai/dsh-evolution-threat
Write-time threat guard for evolution tools
AI 분석
提供写入时的安全扫描与威胁防护,适合需要保障演化工具运行安全的开发者。
설치
검증된 bundle이 없거나 호환성 검사에 실패했습니다. 먼저 저장소 설명을 읽어 주세요. 전체 README 읽기 ↗
@deepseek-ai/dsh-evolution-threat
Write-time threat guard for evolution tools
Model Experience
Indirect model surface
What the model sees
@deepseek-ai/dsh-evolution-threat registers no direct prompt or tool schema itself. Model-visible effects are owned by the packages that consume this service.
Token effect
Zero direct token effect from this package; consumers add any model-visible tokens.
KV Cache effect
Independent of request-prefix construction. This package does not alter the assembled prompt or tool list.
Config
-
maxScanChars(default 65536): the scan window size in normalized characters. Legal range is>= 4097— a smaller window cannot guarantee full-coverage scanning (the overlap floor isPATTERN_OVERLAP + 1in evolution-core), so the schema rejects it at load and the assembly clamp falls back to the default. The whole text is always scanned in overlapping windows; this value is not a total cap. -
threatExemptLabels(default[]): pattern labels the deployment knows to be benign. P2-4 (v14) closed the store-vs-guard asymmetry for the STORE gates (SkillLibrary/MemoryStoreoptions) — but the exemption surface is per config site: this guard row, the tool-skill-manage row, the evolution-commands row (its own SkillLibrary for the command write paths), and the memory store options each carry their OWN list and must be set separately. A label exempted only on the store side still blocks here. (v17 audit: the evolution-commands site was missing from this enumeration.)
Known Limitations and Deferred Work
- No known durable consumer gaps at this time. Runtime contracts are covered by package and boundary tests.