> 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/keeperpam/commander-sdk/keeper-commander-sdks/sdk-command-reference/reporting-commands/password-report-command.md).
# Password Report Command
### Password Report Command
Displays information about shared records, limited to those shared by the caller with other users and excluding records shared with the caller by others..
DotNet CLI
**Command:** Coming Soon
DotNet SDK
**Function:** Coming Soon
Power Commander
**Command:** `Get-KeeperPasswordReport`
**Parameters**
| Flag | Purpose | Default |
| ---------- | -------------------------------------------------------- | -------------- |
| `-Policy` | Complexity policy as `Length,Lower,Upper,Digits,Special` | `"12,2,2,2,0"` |
| `-Folder` | Limit to a specific folder path or UID | All records |
| `-Length` | Minimum password length filter | From policy |
| `-Lower` | Minimum lowercase characters filter | From policy |
| `-Upper` | Minimum uppercase characters filter | From policy |
| `-Digits` | Minimum digits filter | From policy |
| `-Special` | Minimum special characters filter | From policy |
**Examples:**
{% code expandable="true" %}
```
PS > Get-KeeperPasswordReport -Policy "16,3,3,3,1"
Password Length: 16
Lowercase characters: 3
Uppercase characters: 3
Digits: 3
Special characters: 1
Record UID Title Description Length Lower Upper Digits Special
---------- ----- ----------- ------ ----- ----- ------ -------
aA3jupAlFe8d7Z5KFWyfeQ 1rec_5iEQPHha user256@test.local 12 1 7 4 0
HtQDE742egmS7lllKC2lWA 1rec_U7FtywiP user275@test.local 12 4 5 3 0
IrcqEStZGsEIzI8VoHgTTw 1rec_FNRJanY1 user853@test.local 12 6 3 3 0
oBmXCuUPzrIZRXuMMGEuvQ 1rec_S6XMmej2 user303@test.local 12 6 4 2 0
```
{% endcode %}
Python CLI
**Command:** `passsword-report`
**Parameters:**
folder: folder path or UID
**Flags:**
--format format of output {table, csv, json}.\ --output path to resulting output file (ignored for "table" format).\ -v, --verbose display verbose information.\ --policy password complexity policy. Length,Lower,Upper,Digits,Special. Default is 12,2,2,2,0.\ -l, --length minimum password length.\ -u, --upper minimum uppercase characters.\ --lower minimum lowercase characters.\ -d, --digits minimum digits.\ -s, --special minimum special characters.
**Example:**
```powershell
My Vault> password-report --policy 12,2,2,2,0
Password Length: 12
Lowercase characters: 2
Uppercase characters: 2
Digits: 2
# Record UID Title Description Length Lower Upper Digits Special
--- ------------ ------- ------------- -------- ------- ------- -------- ---------
```
Python SDK
**Function:** Coming Soon
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.keeper.io/keeperpam/commander-sdk/keeper-commander-sdks/sdk-command-reference/reporting-commands/password-report-command.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.