Skills brewpage-publish-safe
๐Ÿ“ฆ

brewpage-publish-safe

Content revision r2 High Risk ๐ŸŒ Network access๐Ÿ“ Filesystem accessโš™๏ธ External commands๐Ÿ”‘ Env variables

Publish and Update Content on BrewPage

Publishing a file or site also means tracking who can update it. BrewPage Publish Safe sends approved content and keeps ownership records for later updates.

Supports: Claude Codex Code(CC)
Maintain this Skill? Claim it โš ๏ธ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "brewpage-publish-safe" from https://skillstore.io/skills/kochetkov-ma-brewpage-publish-safe.md and its manifest at https://skillstore.io/api/skills/kochetkov-ma-brewpage-publish-safe/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "brewpage-publish-safe". Publish an approved Markdown draft without public listing.

Expected outcome:

  • Publication confirmed. The BrewPage reader link is ready to share.
  • Anonymous owner proof was saved in private workspace state.

Using "brewpage-publish-safe". Publish a site ZIP with entries requiring approval.

Expected outcome:

  • No upload was made. The archive manifest lists the files, selected entry, and flagged names.
  • Approve the exact archive digest before continuing.

Using "brewpage-publish-safe". Update a reader link without matching owner proof.

Expected outcome:

  • The target could not be matched to saved owner proof. No update or new publication was sent.

Security Audit

High Risk
v2 โ€ข 11/20/2026 Open versioned report

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.

9
Files scanned
2,061
Lines analyzed
29
Review items
0
False positives ignored

Confirmed security concerns (3)

High
Unreviewed ZIP metadata is transmitted
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.
Medium
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.
Medium
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.

High
Python subprocess.run
result = subprocess.run(['git', '-C', root] + arguments, stdout=subprocess.PIPE, stderr=subprocess.P
The Git check uses fixed arguments and no shell, but executable lookup still relies on inherited PATH rather than a verified binary.
High
Process spawn
const child = spawn(bin, argv, { cwd: options.cwd, env: options.env, stdio: ['pipe', 'ignore', 'igno
The caller uses fixed tool names and argument arrays without a shell. The child still resolves its executable through a PATH without ownership checks.
High
Synchronous spawn
const r = spawnSync('unzip', ['-tq', zipPath], { env: archiveEnv, encoding: 'utf8', maxBuffer: LIST_
The fixed unzip integrity check is bounded and uses no shell. The unzip executable is still resolved by name through PATH.
High
Synchronous spawn
const copied = spawnSync('python3', ['-I', '-S', '-c', FILE_SNAPSHOT, source, args.out, String(info.
The snapshot uses fixed isolated Python source and separate arguments. The executable is still resolved by name through PATH.
Medium
Shell command substitution
output=$(bp_curl -s -A "$BP_UA" -X "$method" "$url" "$@" -w $'\nBP_HTTP_STATUS:%{http_code}') || ret
This call sends selected content and can attach live credentials. The URL guard limits it to the official service.
Medium
Shell command substitution
metadata=$(BP_OWNER_HEADER_FILE="$proof" BP_HEADER_FILE='' bp_request GET "https://brewpage.app/api/
The owner-check sends reusable owner proof to the first-party API. This is expected, but it crosses the local credential boundary.
Medium
Shell command substitution
selected=$(bp_history select "$intent" "$target" "$BP_OWNER_HEADER_FILE") || return 1
The history call can select an existing live token on create without an explicit owner target. Only the endpoint is captured from stdout.
Medium
Shell command substitution
token=$(printf '%s' "$response" | jq -er '.ownerToken | if . == null then "" else strings | select(t
This extracts a live owner token from the API response into shell memory. The fixed jq filter checks its format and does not evaluate it.
Medium
Shell command substitution
receipt=$(printf '%s' "$response" | jq -c --rawfile proof "${BP_OWNER_HEADER_FILE:-/dev/null}" --arg
The command packages a reusable owner token and management details for local persistence. These remain sensitive even within private storage.
Medium
Shell command substitution
runtime_dir=$(builtin cd "$runtime_dir" 2>/dev/null && builtin pwd -P) || continue
The runner keeps absolute PATH directories outside the workspace without verifying their owner or write permissions.
Medium
Shell command substitution
metadata=$(bp_history recover-target "$proof") || die 'no readable protected recovery receipt'
The recovery helper extracts a live token from a private receipt into an owner-only header. The captured stdout contains only target metadata.
Medium
Shell command substitution
password_identity=$(bp_python "$HERE/inputs.py" password "$pwfile" "$BP_HEADER_FILE") || exit 1
The password helper reads a selected plaintext password into a private request header. Command output contains only file identity.
Medium
Shell command substitution
response=$(bp_request "$method" "$endpoint" -H "Content-Type: application/json" --data-binary @"$BP_
This sends the selected page and optional state to BrewPage, with configured credentials when present. It is the intended external write.
Medium
Shell command substitution
response=$(bp_request "$method" "$endpoint" -H "Content-Type: application/json" --data-binary @"$con
This sends the selected JSON to BrewPage, with configured credentials when present. It is the intended external write.
Medium
Shell command substitution
response=$(bp_request "$method" "$endpoint" -F "$(form_file file "$content")") || die "$unknown"
The multipart request transfers the chosen file to BrewPage. Quoting the form value does not remove the disclosure risk.
Medium
Shell command substitution
metadata=$(bp_request GET "$endpoint") || die "cannot verify existing site entry; no replacement sen
The GET fetches current site entry metadata from the exact owner endpoint using reusable owner proof.
Medium
Shell command substitution
response=$(bp_request "$method" "$endpoint" -F "$(form_file archive "$CHECKED_PATH")" ${state:+--for
The runner uploads the complete ZIP and optional state to BrewPage. Unreviewed ZIP metadata can be transferred along with inspected content.
Medium
Python file write/append
with os.fdopen(fd, 'wb') as output:
This write helper persists reusable owner tokens and private management data as plaintext protected by local file permissions.
Medium
Python file write/append
with os.fdopen(fd, 'w', encoding='ascii') as header:
The code materializes reusable owner proof as a plaintext request header. Exclusive creation and mode 0600 limit access.
Medium
Python os file operations
os.unlink(PENDING, dir_fd=directory)
This unlinks the pending create after matching the local operation ID. Its caller can clear it on an HTTP rejection without independent outcome proof.
Medium
Python file write/append
with os.fdopen(fd, 'wb') as header:
The code writes the selected plaintext password to a temporary owner-only request header. It is not an unrelated secret read.
Medium
Python shutil operations
shutil.copyfileobj(incoming, outgoing)
The file snapshot copies ordinary input before enforcing its later review limit. An oversized input can consume temporary storage.
Low
HTTP client library
bp_request() {
This wrapper dispatches publication requests and attaches owner or password headers from local files. The destination is restricted to BrewPage.
Low
Hardcoded URL
metadata=$(BP_OWNER_HEADER_FILE="$proof" BP_HEADER_FILE='' bp_request GET "https://brewpage.app/api/
The fixed BrewPage owner-check destination receives reusable owner proof. This is an authorized integration path, not an unrelated destination.
Low
Python environment access
environment = {'PATH': os.environ['PATH'], 'LC_ALL': 'C', 'GIT_CONFIG_NOSYSTEM': '1', 'GIT_CONFIG_GL
The Git subprocess environment is minimized, but it still trusts inherited PATH for executable resolution.
Low
Environment variable access (dot notation)
const dirs = (process.env.PATH || '').split(delimiter).filter(Boolean);
The helper checks availability using PATH without requiring installation directories to be trusted by ownership or permissions.
Low
Environment variable access (dot notation)
const archiveEnv = { PATH: process.env.PATH, LC_ALL: 'C', TZ: 'UTC' };
The restricted child environment still inherits PATH. Archive subprocesses use it to locate their executables.
Low
Environment variable object
const dirs = (process.env.PATH || '').split(delimiter).filter(Boolean);
The helper checks availability using PATH without requiring installation directories to be trusted by ownership or permissions.
Low
Environment variable object
const archiveEnv = { PATH: process.env.PATH, LC_ALL: 'C', TZ: 'UTC' };
The restricted child environment still inherits PATH. Archive subprocesses use it to locate their executables.

Risk Factors

๐ŸŒ Network access (21)
๐Ÿ“ Filesystem access (50)
โš™๏ธ External commands (50)
๐Ÿ”‘ Env variables (10)
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/kochetkov-ma-brewpage-publish-safe/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/kochetkov-ma-brewpage-publish-safe/security.svg)](https://skillstore.io/skills/kochetkov-ma-brewpage-publish-safe?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/kochetkov-ma-brewpage-publish-safe?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/kochetkov-ma-brewpage-publish-safe/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/kochetkov-ma-brewpage-publish-safe.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

kochetkov-ma. (2026). brewpage-publish-safe security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/kochetkov-ma-brewpage-publish-safe/audits/2

BibTeX citation

@techreport{kochetkov-ma-kochetkov-ma-brewpage-publish-safe-2026, author = {kochetkov-ma}, title = {brewpage-publish-safe security audit report (audit version 2)}, institution = {Skillstore}, year = {2026}, number = {2}, url = {https://skillstore.io/skills/kochetkov-ma-brewpage-publish-safe/audits/2}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "brewpage-publish-safe security audit report (audit version 2)" version: "unspecified" type: report authors: - name: "kochetkov-ma" date-released: "2026-11-20" url: "https://skillstore.io/skills/kochetkov-ma-brewpage-publish-safe/audits/2" identifiers: - type: other value: "skillstore:kochetkov-ma-brewpage-publish-safe:audit:2" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium
59
Architecture
85
Maintainability
87
Content
65
Community
83
Spec Compliance

What You Can Build

Share a review draft

Publish a reviewed Markdown draft without requesting public listing. Share only the reader link with reviewers.

Publish a static site build

Package a dedicated build directory and review its files and entry point before approving an upload.

Replace a published status page

Use the original workspace and exact saved reader link to update the page without creating a replacement.

Try These Prompts

Inspect a local file
Probe the selected draft locally and report its file type and size. Do not contact BrewPage or publish anything.
Publish a reviewed draft
Publish the reviewed Markdown draft to BrewPage under the specified non-public namespace for seven days. Use fresh anonymous ownership and no password.
Update the same reader link
In the original workspace, update the exact saved reader link with my approved replacement. Keep the existing access settings and expiration. Do not create another publication.
Review a static site release
Review the dedicated site build and its entry file without uploading. Check all selected content and archive metadata. Ask me to approve the final archive before uploading.

Best Practices

  • Review the exact files, page state, and archive metadata before authorizing an external write.
  • Choose fresh anonymous ownership or expressly approve reuse. Keep owner tokens, management links, and passwords out of prompts and transcripts.
  • Use the original workspace and exact saved reader link for updates. Resolve uncertain creates before authorizing another one.

Avoid

  • Do not publish an entire workspace when only a build output is intended.
  • Do not treat a link-only publication as private. Anyone with the link can view it unless it is password protected.
  • Do not approve a changed archive with an old review digest or turn a failed update into a new publication.

Frequently Asked Questions

What inputs can I publish?
You can publish HTML, Markdown, JSON, a single file, or a static site from a directory or supported ZIP.
Does a reader link make the content private?
No. Anyone with a link-only URL can view it unless a password protects it. Choose the public namespace only when you intend public listing.
Where are owner credentials stored?
The runner keeps them in owner-only application state for the operating system account and resolved workspace. It reports the reader link, not the token.
Can I update a page from another workspace?
Use the original workspace, the same operating system account, and the exact saved reader URL. This edition does not search other workspaces for proof.
Does archive confirmation prove there are no secrets?
No. It binds approval to an archive digest. Encoded values, unsupported formats, and unreviewed metadata still need independent review.
What should I do if a create has an unknown outcome?
Check the pending operation and recover a protected receipt if available. Otherwise verify the outcome through BrewPage before recording it or authorizing another create.

Developer Details

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Ref

d0711bf661230a71e66e40843f2ab3bb938327ae

Maintenance freshness

11/20/2026

Usage

0 downloads ยท 0 views

File structure

๐Ÿ“„ LICENSE

๐Ÿ“„ README.md

๐Ÿ“ scripts/

๐Ÿ“„ brewpage-lib.sh

๐Ÿ“„ brewpage-run.sh

๐Ÿ“„ history.py

๐Ÿ“„ inputs.py

๐Ÿ“„ publish.mjs

๐Ÿ“„ SKILL.md

๐Ÿ“„ VERSION

More from kochetkov-ma

View all
View all