Problem
Security scanning is already performed at install time, but rules are hard-coded, reports are ephemeral, and users cannot tune severity or view historical scan results.
Goals
- Move rule definitions to a configurable JSON/YAML file in user data.
- Support severity levels and per-source overrides.
- Persist scan reports in SQLite with timestamp.
- UI: show "Safe / Warning / Dangerous" status per skill; click to view detailed report.
- Hard-block installation if critical rules trigger.
Acceptance Criteria
问题
安装时已经执行了安全扫描,但规则是硬编码的,报告是临时的,用户也无法调整严重级别或查看历史扫描结果。
目标
- 将规则定义移到用户数据目录下的可配置 JSON/YAML 文件。
- 支持严重级别和按来源覆盖规则。
- 将扫描报告按时间戳持久化到 SQLite。
- UI:每个 skill 展示 "Safe / Warning / Dangerous" 状态,可点击查看详细报告。
- 触发 critical 规则时强制阻止安装。
验收标准
Problem
Security scanning is already performed at install time, but rules are hard-coded, reports are ephemeral, and users cannot tune severity or view historical scan results.
Goals
Acceptance Criteria
问题
安装时已经执行了安全扫描,但规则是硬编码的,报告是临时的,用户也无法调整严重级别或查看历史扫描结果。
目标
验收标准