Versioned security assessment

Report ID: SA-03AB77C5

7/6/2026, 5:15:37 PM

figma security assessment v2

Skill Security Certification Report

Audit History
Audit model: codex Historical report
Skill name
figma
Version
v2
Maintainer
heygen-com
Source
github.com/heygen-com/hyperframes/tree/main/skills/figma/
Coverage
1 Files scanned · 120 Lines analyzed
Policy version
Unavailable

Highest confirmed finding severity

High

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.

Most static command findings are Markdown inline examples rather than executable code. Confirmed risks are the intended HyperFrames CLI and npx workflows. The report also flags project .env token guidance; no prompt injection or malicious exfiltration intent was found.

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 · 120 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.

Observed in 1 evidence location

Network access

May connect to external services.

Not recorded by this audit

Filesystem access

May read or write local files.

Not recorded by this audit

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

Capability review items (4)
Medium
SKILL.md:51-53
Ruby/shell backtick execution
```bash
The fenced block at lines 51-53 instructs running the HyperFrames asset CLI with a user-provided Figma reference. That external command performs network and filesystem operations.
Medium
SKILL.md:59-61
Ruby/shell backtick execution
```bash
The fenced block at lines 59-61 instructs running the HyperFrames tokens CLI against a Figma file key. It uses project credentials and writes imported token artifacts.
Medium
SKILL.md:69-71
Ruby/shell backtick execution
```bash
The fenced block at lines 69-71 instructs running the HyperFrames component CLI with a user-provided Figma reference. That command can fetch remote design data and write component files.
Medium
SKILL.md:86-99
Ruby/shell backtick execution
5. Run `npx hyperframes lint && npx hyperframes validate` before calling it done.
Line 86 instructs running npx hyperframes lint and npx hyperframes validate. Package-managed commands can execute local project or dependency code.

Risk findings

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

Confirmed security concerns (2)

RISK-001 High
SKILL.md:22
Environment file access
**Preflight — before the first CLI call, check a token exists**: shell env (`[ -n "$FIGMA_TOKEN" ]`)
The skill directs the agent to check for a Figma token in shell environment or a project .env file. Even an existence check can lead agents toward secret-bearing files, so this should remain flagged.
RISK-002 High
SKILL.md:26
Environment file access
3. `export FIGMA_TOKEN="figd_..."` — and suggest persisting it (shell profile or project `.env`) so
The skill suggests persisting FIGMA_TOKEN in a shell profile or project .env file. Project .env storage can expose a Figma personal access token if committed or shared.

Remediation

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

  1. FIX-001
    High
    The skill suggests persisting FIGMA_TOKEN in a shell profile or project .env file.
    Recommend secure local secret storage, add .env to ignore rules, and avoid storing tokens in shared project files.
  2. FIX-002
    Medium
    The skill directs agents to run HyperFrames CLI commands against user-provided Figma references.
    Require explicit user confirmation before running commands, validate Figma references, and run only in trusted projects.
  3. FIX-003
    Medium
    The validation step uses npx, which may execute project or package code.
    Prefer a pinned local HyperFrames dependency and tell users before running package-managed commands.

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