📦

監査履歴

personwise-customer-education - 1 監査

2026年8月5日 18:37

Most static findings are false positives caused by secure installer checks and Markdown formatting. Shell substitutions use quoted validation inputs, while descriptor entropy comes from Base64 metadata and a Minisign signature. Native installation, service-provided update commands, and document uploads still create meaningful third-party trust and execution risks.

6
スキャンされたファイル
649
解析済み行数
6
レビュー項目
0
誤検知を無視

確認済みのセキュリティ上の懸念 (3)

中
Native CLI installation expands the trust boundary
When the CLI is missing, the workflow installs a downloaded native PersonWise executable. Fixed hashes reduce tampering risk, but third-party native code still executes locally.
The workflow explicitly directs the agent to run bundled bootstrap scripts that install the required native executable.
中
Service-provided update commands can be executed
The workflow runs an update command returned by PersonWise after user approval. It does not require parsing the response against a fixed executable and argument allowlist.
The text explicitly says to quote and run the returned action command. User approval mitigates risk, but command validation is not specified.
中
Selected customer materials are uploaded to PersonWise
The workflow treats user-selected documents as authorized and uploads them to PersonWise. Sensitive content can cross a third-party boundary without destination-specific confirmation.
The source add command and surrounding instructions directly describe uploading selected local documents to the service.
監査者: codex