Versioned security assessment

Report ID: SA-88A205C7

7/8/2026, 3:39:58 PM

project-to-obsidian security assessment v4

Skill Security Certification Report

Audit History
Audit model: codex Latest published report
Skill name
project-to-obsidian
Version
v1.4.0
Maintainer
Claude Code
Source
github.com/ZhanlinCui/Ultimate-Agent-Skills-Collection/tree/main/project-to-obsidian
Coverage
7 Files scanned · 1,074 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

High

2 confirmed security findings require attention.

Installation context

Check the current Skill page

This page summarizes report evidence only. The Skill page provides the canonical install advisory.

Open current Skill page

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

Most static alerts are false positives caused by Markdown code fences, slash-command examples, Obsidian links, Mermaid diagrams, and normal Claude skill installation instructions. I confirmed the .env and configuration scanning guidance because it can expose credentials when generated notes capture environment values. No prompt injection or covert exfiltration language was found.

Report position

Latest published report

Latest refers to the report sequence, not to artifact currentness.

Audit attestation

Not attestable

The required immutable binding is incomplete.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

7 Files scanned · 1,074 Lines analyzed

3 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

    Commit and path bound

  2. Artifact

    Content and tree hashes bound

  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.

Not recorded by this audit

Filesystem access

May read or write local files.

Observed in 2 evidence locations

Env variables

May read values from the process environment.

Not recorded by this audit

External commands

May invoke commands or programs outside the Skill.

Observed in 65 evidence locations

Capability review items (1)
High
SKILL.md:197
Hidden file access
- **/.env*, **/config.* # 配置文件
The workflow explicitly includes **/.env* in project scans. Hidden environment files often contain credentials, and generated notes may expose those values.

Risk findings

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

Confirmed security concerns (2)

RISK-001 High
SKILL.md:197
Environment file access
- **/.env*, **/config.* # 配置文件
The scan pattern targets environment files and config files that commonly store secrets. The skill also generates configuration documentation, creating a credible disclosure risk.
RISK-002 High
SKILL.md:193-198SKILL.md:243-246
Potential Secret Disclosure in Generated Documentation
The workflow scans .env and config files, then extracts environment variables and configuration into generated Obsidian documentation. Without redaction, notes can expose credentials or private endpoints.
The file scan pattern and later extraction requirements are explicit. I did not find redaction rules that prevent secret values from being written to notes.

Remediation

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

  1. FIX-001
    High
    Default scan pattern includes environment files.
    Remove **/.env* from default scans, or require explicit confirmation before reading secret-bearing files.
  2. FIX-002
    High
    Generated configuration notes may disclose secret values.
    Document variable names only and redact tokens, passwords, keys, connection strings, and private URLs before writing notes.
  3. FIX-003
    Low
    Project scanning mentions shell-based ls/find usage.
    Prefer Glob and read-only file APIs, or use hardcoded safe commands without interpolating user paths.

Expert evidence

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

Artifact subject

Marketplace commit
88a205c7f635a966e31156313b590d59007c5caa
Content hash
441b654649c1374a0fddfc5cdbe536d9e8e6b5858d04e836f1ebb99cddf66482
Tree hash
b181e04cad19e809216ed6583f3fc1eb7ca7883465018c3d1445ed67908aa0f0
Skill path
skills/zhanlincui/project-to-obsidian
Audit payload hash
620909feab62b87c42154d86e39d1672

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 Source

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

Audit attestation: not_attestable