Most static alerts are documentation, validation, or fixed local operations. Confirmed exposure includes first-party transfers, reusable plaintext owner proof, and executable lookup through unverified PATH directories. Review also found incomplete ZIP metadata checks and implicit owner reuse; no evidence of author prompt injection or undisclosed external destinations was found.
The secret check reads member names and file contents, not all ZIP metadata. The runner uploads supplied archives without removing unreviewed comments and extra fields.
The parser accepts comments and does not inspect arbitrary extra-field values for secrets. The multipart upload sends the complete archive.
New publications can silently reuse existing ownership
A create without an owner target can select the sole saved workspace token. The publish instructions do not require affirmative approval for that authority reuse.
Selection considers all retained rows when the target is empty. One distinct saved token is written to the request header unless anonymous mode was chosen.
Create recovery is not tied to a server operation identifier
The request fingerprint is local, and reconciliation trusts an operator attestation. Most HTTP client errors also clear pending state without a verified no-write outcome.
The local fingerprint is recorded before dispatch, but no server idempotency key is sent. Incorrect reconciliation or ambiguous rejection could permit an unintended duplicate.
Capability review items (29)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Most alerts match documented BrewPage requests, private state operations, fixed utility calls, or literal text. No evidence of deliberate credential exfiltration or reviewer-directed prompt injection was found. Residual risks include non-isolated Python startup, inherited environment settings, and incomplete validation of publication inputs and results.
Some publish-time helpers start Python without isolated mode. Local module lookup and interpreter startup can execute code outside the installed skill before content validation completes.
The HTML, UTF-8, and digest helpers omit the interpreter flags used for history and snapshot operations. The runner does not establish a trusted working directory.
Skipped filenames can enter the review transcript without escaping. The runner also derives the entry point from printed text instead of a separate structured field.
Names with line breaks can enter the skipped list, which the formatter prints verbatim. The shell later reads an entry value from that same manifest output.
Credential Filtering Does Not Inspect File Contents
The skill relies on names, file metadata, and known path identities to screen uploads. An approved file can still contain exposed secrets, including inside nested archives.
The code checks reserved names and selected file identities, not arbitrary payload content. The runner sends selected content to BrewPage after those checks.
Password Source Validation Is Not Bound to the Read
The runner checks the selected password file and later reopens its path. A local replacement can change the password or place unintended data in the publication header.
The copy uses the path again without retaining the validated descriptor. The later check validates password syntax, not the identity of the source file.
The receipt checks the official write endpoint but can display an arbitrary HTTPS reader host as confirmed. That can mislead users about where a publication is hosted.
The reader identity check applies only to the main BrewPage hostname. The runner displays the validated string without requesting it or checking another host binding.
Capability review items (2)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
result = subprocess.run(['git', '-C', root] + arguments, stdout=subprocess.PIPE, stderr=subprocess.P
The Git safety check inherits repository-discovery overrides from the caller. These can invalidate the check that credential state is outside a Git working tree.
ZIP utilities inherit the caller environment after only ZIP option defaults are removed. This unnecessarily exposes unrelated environment values to child processes.