Versioned security assessment

Report ID: SA-94BEDE9C

5/5/2026, 8:55:24 AM

seedance-v2 security assessment v1

Skill Security Certification Report

Audit History
Audit model: claude Historical report
Skill name
seedance-v2
Version
v1
Maintainer
agentspace-so
Coverage
1 Files scanned · 182 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.

All static findings are false positives. The skill is a video generation documentation file with CLI command examples in markdown code blocks. The external_commands alerts flag markdown code fences (```bash) rather than actual shell execution. Hardcoded URLs are legitimate documentation links. Path traversal patterns are placeholder paths in examples. Token storage uses standard secure CLI practices with mode 0600 permissions. No malicious patterns confirmed.

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

1 Files scanned · 182 Lines analyzed

1 item 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 1 evidence location

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 4 evidence locations

Capability review items (1)
Medium
Token file storage at ~/.config/runcomfy/token.json
The skill documents storing API tokens in ~/.config/runcomfy/token.json. This is a standard CLI tool pattern and the documentation explicitly mentions using mode 0600 (owner-only) permissions. For CI environments, the skill recommends using RUNCOMFY_TOKEN environment variable instead.
Standard secure CLI practice with documented permission requirements. Token storage is explicitly documented with security controls.

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: claude

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 (5)
High
False Positive: Ruby/shell backtick pattern in markdown code blocks
The static scanner flags backtick patterns in markdown code fences as 'Ruby/shell backtick execution'. These are documentation code examples showing CLI commands like `runcomfy run bytedance/seedance-v2/pro`. No shell execution occurs - these are markdown syntax for inline code and fenced code blocks. Verified at lines 24-26, 70-74, 78-87, 91-100, and throughout the document.
Code fences (```bash) and inline backticks in markdown are documentation syntax, not shell backtick execution. The content describes CLI usage examples with hardcoded commands, not dynamic code generation.
High
False Positive: Path traversal in documentation placeholders
The static scanner flags `<absolute/path>` as path traversal. These are documentation placeholders showing users where to specify their output directory. They are not actual path traversal exploits - the skill documentation is teaching users how to use CLI arguments properly.
The placeholder <absolute/path> is standard documentation syntax teaching users CLI argument usage. No user input is processed into file paths without validation.
High
False Positive: Weak cryptographic algorithm on 'seed' keyword
The static scanner flags 'seed' as a weak cryptographic algorithm indicator. In this context, 'seed' refers to a video generation reproducibility parameter (line 64 in the schema table), not cryptography. This is a completely different semantic context.
The word 'seed' appears in a video generation context (schema field for reproducibility), not cryptographic usage. No actual cryptographic operations are performed in this documentation file.
Medium
Hardcoded URLs are legitimate documentation links
Static scanner flagged hardcoded URLs at lines 14, 20, 169, and 173. These are legitimate documentation links to runcomfy.com, docs.runcomfy.com, and model-api.runcomfy.net. No malicious URLs detected.
All flagged URLs point to runcomfy.com and associated domains - the legitimate service provider for this skill. No suspicious external endpoints detected.
Low
False Positive: System reconnaissance patterns
The static scanner flagged lines 42 and 112 as 'system reconnaissance'. Line 42 is a routing condition ('If the user said Seedance...') and line 112 documents reference media specs. These are not reconnaissance patterns - they are legitimate skill routing logic and documentation.
No system information gathering detected. Line 42 is prompt routing logic, line 112 is documentation about reference media specifications.

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