> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/jp/developer-tools/commander/commander-16.11.6.md).

# コマンダー 16.11.6

GitHubでリリースを確認: <https://github.com/Keeper-Security/Commander/releases/tag/v16.11.6>

## 向上点とバグ修正

* `security-audit-report`\
  セキュリティデータのサイズが予期しない場合に復号に失敗し、その結果サマリースコアの計算が不正確になる不具合を修正。
* `breachwatch report`\
  サマリースコアが更新された状態で表示されるように改善。
* `security-audit sync`\
  確認プロンプトなしで同期を実行するオプション (非対話モード) と、同期時にセキュリティ監査レポートを表示しないオプションを追加。
* 各種エンタープライズレポートコマンド (例: `user-report`、`enterprise-info --roles)`\
  SCIMによって割り当てられたロールが表示されない不具合を修正。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.keeper.io/release-notes/jp/developer-tools/commander/commander-16.11.6.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.