Versioned security assessment

Report ID: SA-73FDADA3

7/5/2026, 7:13:44 AM

bark-notify security assessment v7

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
bark-notify
Version
v7
Maintainer
caopulan
Source
github.com/caopulan/Notification-Skill/tree/main/bark-notify
Coverage
2 Files scanned · 202 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

Medium

2 confirmed security findings require attention.

Installation context

Historical evidence

This report may not describe the currently installable artifact. Open the current Skill page for install guidance.

Open current Skill page

This report does not block or authorize the manifest or ZIP.

The skill intentionally sends Bark push notifications, so outbound network use and selected environment access are expected. I confirmed real risks around sending task metadata, reading the Bark key, executing the helper command, and dry-run output that can reveal the token. Most high filesystem and path traversal alerts are false positives from documentation placeholders and standard Codex paths.

Report position

Historical report

Open audit history before using this report to install.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

2 Files scanned · 202 Lines analyzed

9 items shown for review

Limitations

This report does not claim runtime or sandbox execution and does not prove the absence of side effects.

Evidence chain

Follow the evidence from source binding to the install contract. Available evidence supports verification; it is not a safety guarantee.

  1. Source

    Binding unavailable

  2. Artifact

    Identity incomplete

  3. Audit

    Complete

  4. Install contract

    Open manifest to verify

    Open manifest

Capabilities observed

Observed means this report recorded supporting evidence. Not recorded does not prove that a capability is absent.

Contains scripts

May execute code included with the Skill.

Not recorded by this audit

Network access

May connect to external services.

Observed in 3 evidence locations

Filesystem access

May read or write local files.

Observed in 5 evidence locations

Env variables

May read values from the process environment.

Observed in 3 evidence locations

External commands

May invoke commands or programs outside the Skill.

Observed in 9 evidence locations

Capability review items (7)
Medium
SKILL.md:45-51
Ruby/shell backtick execution
```bash
The markdown block instructs the agent to run python3 against the bundled helper script. This external command is expected, but generated arguments require careful quoting.
Low
scripts/send_bark_notification.py:88
Hardcoded URL
base_url = os.environ.get("CODEX_BARK_BASE_URL", "https://api.day.app")
The helper defaults to https://api.day.app and later posts task notification data to that endpoint. This is expected for Bark, but it is intentional outbound network behavior.
Low
scripts/send_bark_notification.py:86
Python environment access
machine_name = os.environ.get("CODEX_MACHINE_NAME")
The machine name is read from the environment and included in the notification body sent externally. It is not a secret, but it can identify the user device.
Low
scripts/send_bark_notification.py:87
Python environment access
bark_key = os.environ.get("CODEX_BARK_KEY")
CODEX_BARK_KEY is a Bark credential used in the request URL. Reading it is required, but mishandling can disclose a notification token.
Low
scripts/send_bark_notification.py:88
Python environment access
base_url = os.environ.get("CODEX_BARK_BASE_URL", "https://api.day.app")
CODEX_BARK_BASE_URL controls the outbound notification destination. This is legitimate configuration, but it can redirect posted task data if set incorrectly.
Low
SKILL.md:19
Hardcoded URL
export CODEX_BARK_KEY="" # https://api.day.app/<CODEX_BARK_KEY>/
The documentation shows the Bark API URL used with the notification key. It reflects the skill's intended external service, which users should understand before enabling.
Low
SKILL.md:20
Hardcoded URL
export CODEX_BARK_BASE_URL="https://api.day.app"
The setup example configures https://api.day.app as the notification endpoint. This is expected, but confirms the skill depends on an external network service.

Risk findings

Confirmed security concerns are separated from items that still need review.

Confirmed security concerns (2)

RISK-001 Medium
scripts/send_bark_notification.py:118-122
Dry-run Output Can Disclose Bark Key
The helper builds the request URL with CODEX_BARK_KEY and prints that full URL during dry-run mode. Logs or copied output can expose the notification token.
Line 118 embeds the Bark key in the URL, and line 122 prints that URL during dry-run. This is direct credential exposure to local output.
RISK-002 Medium
scripts/send_bark_notification.py:109-119scripts/send_bark_notification.py:127-130
Task Metadata Is Sent To External Push Service
The notification body includes device, project, status, and summary fields before posting to Bark. Sensitive project details can leave the local environment if summaries are too broad.
The code constructs a payload from task metadata and sends it with urllib. This is intended behavior, but the privacy risk is clear from the data fields.

Remediation

Suggested fixes recorded by this audit. Applying them is the maintainer’s responsibility.

  1. FIX-001
    Medium
    Dry-run output can expose the Bark key.
    Mask the Bark key when printing dry-run URLs, or print only the destination host.
  2. FIX-002
    Medium
    Notification payloads can include sensitive task details.
    Redact secrets and keep summaries minimal before sending notifications to Bark.
  3. FIX-003
    Medium
    The documented shell command accepts generated text arguments.
    Document safe argument quoting, or provide a wrapper that passes arguments without shell interpolation.
  4. FIX-004
    Low
    The helper allows a configurable Bark base URL.
    Validate the base URL scheme and document that only trusted Bark endpoints should be used.

Expert evidence

Immutable subject identity, scanner metadata, dismissed matches, and source-level evidence.

Artifact subject

Marketplace commit
Unavailable
Content hash
Unavailable
Tree hash
Unavailable
Skill path
Unavailable
Audit payload hash
Unavailable

Analysis metadata

Audit model: codex

Analysis state: Complete

Scope is limited to the recorded files, lines, methods, and evidence. No runtime or sandbox execution is claimed.

Verify and export

JSON report CITATION.cff SARIF 2.1.0 Signed installation manifest

The manifest and lockfile bind install artifacts to cryptographic hashes. This integrity claim is separate from the security assessment.

Audit attestation: not_attestable