Versioned security assessment

Report ID: SA-C5DA72CF

7/8/2026, 3:58:59 AM

bark-notify security assessment v8

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
bark-notify
Version
v8
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 notifications to a configured endpoint and reads environment variables for that workflow. Most static Markdown, placeholder, and hidden-path matches are false positives, but task metadata egress and dry-run token exposure remain real risks.

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

6 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 (4)
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 the external Bark API endpoint and posts notification content there. This is expected for the skill, but it is real outbound network behavior.
Low
scripts/send_bark_notification.py:86
Python environment access
machine_name = os.environ.get("CODEX_MACHINE_NAME")
The script reads CODEX_MACHINE_NAME and includes it in the notification body. This can disclose a device label to the configured Bark endpoint.
Low
scripts/send_bark_notification.py:87
Python environment access
bark_key = os.environ.get("CODEX_BARK_KEY")
The script reads CODEX_BARK_KEY, which is an authentication token for the Bark service. Handling this secret is necessary but security-sensitive.
Low
scripts/send_bark_notification.py:88
Python environment access
base_url = os.environ.get("CODEX_BARK_BASE_URL", "https://api.day.app")
The script reads CODEX_BARK_BASE_URL to select the notification endpoint. This is expected configuration, but it controls where task metadata is sent.

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:109-119SKILL.md:41
External Notification Content Exposure
The script builds a notification body with device, project, status, and summary values, then sends it to the configured Bark service. This expected behavior can expose workspace metadata if summaries include sensitive details.
The payload construction and POST target are explicit in the helper script. The documentation warns to avoid secrets, so the risk is real but partly acknowledged.
RISK-002 Medium
scripts/send_bark_notification.py:118-122
Dry Run Can Reveal Bark Key
The script embeds the Bark key in the request URL and prints that URL during dry-run mode. Captured terminal output could disclose the notification token.
The code directly builds the URL with bark_key and prints it when dry-run is enabled. This is a clear token exposure path in logs or shared transcripts.

Remediation

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

  1. FIX-001
    Medium
    Notification content can expose workspace metadata.
    Add stronger guidance to omit secrets, user data, ticket details, private repository names, and sensitive summaries before sending alerts.
  2. FIX-002
    Medium
    Dry-run output prints the full Bark URL with the key.
    Mask CODEX_BARK_KEY in dry-run output and any future debug logging.
  3. FIX-003
    Low
    The Bark key may be stored in shell startup files.
    Recommend a secret manager or session-scoped environment variable when possible.
  4. FIX-004
    Low
    Custom Bark base URLs can receive all notification content.
    Document that CODEX_BARK_BASE_URL should use a trusted HTTPS endpoint only.

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