TencentBlueKing / TencentBlueKing/bk-cli
agent 安全与执行治理
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5
- Forks
- 3
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 1
Description
- action 标注 risk: read/write/high
- 高风险命令默认建议 --dry-run 或需要 --yes
- 文件输入路径校验
- 错误 envelope 扩展 type/subtype/param/hint
- 后续再考虑 sidecar 或插件化 credential/transport
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the command/action execution entry points, file-input validation, and error-envelope handling. Define how risk labels, dry-run or confirmation requirements, and path checks should apply across commands, then document the expected structured error fields and test the resulting behavior. Sidecar and plugin-based credentials or transport are explicitly deferred.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100