Versioned security assessment

Report ID: SA-0BBB6514

6/30/2026, 8:15:24 AM

ckm-design-system security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
ckm-design-system
Version
v2
Maintainer
nextlevelbuilder
Coverage
26 Files scanned · 4,805 Lines analyzed
Policy version
Unavailable

Confirmed finding summary

No confirmed security findings

The completed audit recorded no confirmed security findings. This is not proof that the Skill has no side effects.

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 static analyzer produced many high-severity hits, but most repeated weak-crypto, C2, reconnaissance, and backtick findings are false positives from Markdown, CSV design data, CSS token names, and template literals. No malicious intent or prompt-injection attempt was found, but the skill includes local scripts that can read broad directories and write caller-selected output paths, so it should publish with clear usage warnings.

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

26 Files scanned · 4,805 Lines analyzed

4 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.

Observed in 2 evidence locations

Network access

May connect to external services.

Observed in 2 evidence locations

Filesystem access

May read or write local files.

Observed in 4 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 1 evidence location

Capability review items (4)
Medium
Unconstrained CLI Output Paths
The slide and token generators write to caller-provided output paths. This is legitimate local tooling, but unsafe if an AI agent passes untrusted paths or runs in a sensitive workspace.
The file writes are direct and depend on CLI-provided output values. The behavior appears intended for local generation, so the risk depends on how arguments are controlled.
Medium
Broad User-Selected Filesystem Reads
The validation tools recursively scan a user-selected directory and read matching source files. This can inspect more project data than intended if invoked with a broad path.
The scripts read local files from caller-controlled paths, but the purpose is visible token validation. I did not find evidence that file contents are sent to a remote service.
Low
Curated External Resource References
The skill references public Pexels image URLs and generated HTML can load public font resources. These are not credential exfiltration, but users should review external resources before publication.
The URLs are public design resources used for slides and fonts. I did not find code that uploads local data to those URLs.
Low
Subprocess Wrapper Delegates to Local Validator
The legacy slide validator calls a local Python validator through subprocess.run with an argument list. The pattern is executable behavior, but it does not use a shell string.
The command is built as an argv array using sys.executable and a local script path. This significantly reduces command injection risk compared with shell execution.

Risk findings

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

No confirmed security findings were recorded for this completed audit.

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.

Static false positives ignored (1)
Low
Static Crypto and C2 Hits Are Design-Token False Positives
The repeated weak-crypto and C2 findings align with CSS token names, Markdown code fences, radius names such as md, colors, shadows, and design-token examples, not cryptographic code or command-and-control behavior.
The cited sections are design-token reference values and JSON token data. I did not find cryptographic functions, malware networking, or C2 logic in those contexts.

Verify and export

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

Audit attestation: not_attestable