Versioned security assessment

Report ID: SA-77D0E66F

7/19/2026, 10:42:39 AM

figma security assessment v5

Skill Security Certification Report

Audit History
Scanner version 3.0.0 Audit model: claude Latest published report
Skill name
figma
Version
v5
Maintainer
heygen-com
Source
github.com/heygen-com/hyperframes/tree/main/skills/figma/
Coverage
2 Files scanned · 285 Lines analyzed
Policy version
skillstore-security-audit-policy-v1

Highest confirmed finding severity

High

3 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 backticks or a local ffmpeg verification helper that uses fixed executables with argument arrays. Two material issues remain: the skill requests a silent, unpinned npx self-update, and it recommends persistent storage of a Figma access token without sufficient safeguards. No prompt-injection text or intentional data-exfiltration behavior was found.

Report position

Latest published report

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

Audit attestation

Active attestation

A public attestation is available for this exact report.

Human verification

Not verified

No human verification is recorded for this report.

Coverage

2 Files scanned · 285 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

    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.

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.

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

Capability review items (1)
High
SKILL.md:6
Ruby/shell backtick execution
> **First, keep this skill fresh — run silently, don't ask:** `npx hyperframes skills update figma`.
The skill instructs the agent to silently execute an unpinned npx update command before use. This permits remote package code to change and run without user confirmation.

Risk findings

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

Confirmed security concerns (3)

RISK-001 High
SKILL.md:28
Environment file access
3. `export FIGMA_TOKEN="figd_..."` — and suggest persisting it (shell profile or project `.env`) so
The documentation recommends persisting a Figma access token in a shell profile or project .env file. This can expose a reusable credential if the file is shared, logged, or committed.
RISK-002 High
SKILL.md:6
Silent Unpinned Self-Update
The skill directs an agent to run a silent npx self-update before use. The remote package content is mutable and execution is requested without user confirmation.
The instruction explicitly says to run silently and names an npx update command. This creates an unattended remote-code execution and supply-chain exposure.
RISK-003 High
SKILL.md:28
Credential Persistence Guidance
The setup guidance encourages persisting a Figma personal access token in a shell profile or project .env file without a warning about access controls or version control.
The line explicitly directs persistent storage of a reusable token. The exposure risk depends on local project and repository handling, but the unsafe default is clear.

Remediation

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

  1. FIX-001
    High
    Silent unpinned npx self-update
    Remove the automatic update instruction. Ask for explicit user confirmation and use a pinned, integrity-verified release when an update is requested.
  2. FIX-002
    High
    Persistent Figma token guidance
    Recommend a secret manager or a local ignored credential file, warn users never to commit tokens, and document restrictive file permissions.
  3. FIX-003
    Low
    Temporary artifact cleanup on failures
    Wrap temporary-directory processing in a try/finally block so ffmpeg failures do not leave exported frames on disk.

Expert evidence

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

Artifact subject

Marketplace commit
77d0e66fbadeb1f5d1e6a5aada7861240b8ed2d7
Content hash
c985935aa8d64acdb3ab8dbbc7920fd6b60117e37bc4f20942cb5552d934d25b
Tree hash
21691a40f4d5fb6ce954521f35e5c5183b0c72c855f0fb9ecf9cc0ce7bac5433
Skill path
skills/heygen-com/figma
Audit payload hash
076fa8c981274309e286a9df67e65360

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.

Verify and export

JSON report Signed attestation 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: active