Skill
product-launch-video
Turn a product or marketing URL, pasted script, or brief into a product launch / promo video — SaaS promos, feature reveals, product demos, app and company launches. Use when the user wants to market, launch, promote, or reveal a product; the default for any commercial URL. Site tours / showcases of a website route here too — the brief carries the show-it-as-is intent. Unclear → /hyperframes.
○ declared by the publisher, as-isSafety
Safety · gate= b46ebed · assessed 3d ago
F46 severity-bearing · 1 informational
Graded from 46 severity-bearing findings on this release.
A gate; it passes or fails, never weighed against price or quality.
Reliability & Quality
B
Reliability & Quality= b46ebed · assessed 3d ago
B0 findings
Graded from 0 severity-bearing findings on this release.
Findings with severity, graded on the same letter scale as safety.
Cost
n/a
Cost= b46ebed · assessed 3d ago
n/anot assessed
Not assessed; no producer has emitted into this category. An absence, not a zero.
Declared external service dependencies. Never a monetary figure.
not assessed
Popularity
6286
Popularity · not a figure= b46ebed · assessed 3d ago
6286Forks
Read off the linked repository, not off this record. It carries no verdict and enters no grade.
Context read off the linked repository. It enters no ranking and no grade.
Performance tested for◌ not assessed
no controlled task evaluation on this release
Vettd Note
No Vettd note yet for this asset.
Best for
Not for
Re-assessed 3d ago · 6 of 7 categories assessed
Record lookup
◌ Vettd does not install assets; this record describes a copy you obtain yourself.
Custody chainSource ↗○ linked, not verified by Vettd
heygen-com ◐heygen-com/hyperframes ○version = b46ebed ◐ sha256:9148…96d0 ◐ signature △ not assessedApache-2.0 ○record 927aca14-21af-49ca-add3-9eba313a611c · live
Evidence · 6 of 7 categories · 72 signals · 45 soft spots
Where the record is weakest: 45 soft spots
Ranked worst first.
1Shell execution without sandboxingCriticalSafety · critical · VTD-0018
Detected in scripts/assemble-index.mjs:54 — `import { spawnSync } from "node:child_process";`
2Shell execution without sandboxingCriticalSafety · critical · VTD-0018
Detected in scripts/assemble-index.test.mjs:5 — `import { spawnSync } from "node:child_process";`
3Shell execution without sandboxingCriticalSafety · critical · VTD-0018
Detected in scripts/audio.mjs:23 — `import { spawnSync } from "node:child_process";`
Ranked 4–45: Shell execution without sandboxing, Shell execution without sandboxing, Shell execution without sandboxing, Shell execution without sandboxing, Shell execution without sandboxing, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, INJECTION ATTACK detected by YARA, Node.js child_process module usage for shell command execution, INJECTION ATTACK detected by YARA, Node.js child_process module usage for shell command execution, INJECTION ATTACK detected by YARA, Node.js child_process module usage for shell command execution, INJECTION ATTACK detected by YARA, Node.js child_process module usage for shell command execution, INJECTION ATTACK detected by YARA, Node.js child_process module usage for shell command execution, INJECTION ATTACK detected by YARA, Node.js child_process module usage for shell command execution, INJECTION ATTACK detected by YARA, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution, Node.js child_process module usage for shell command execution
The soft spots and their evidence are identical when you are signed in.sign in
Safety● gradedFmost recent 3d ago50 signals · 45 soft spots
how it was established50 signals · 2 sources · scan
show
Shell execution without sandboxingflaggedsoft spot 1Detected in scripts/assemble-index.mjs:54 — `import { spawnSync } from "node:child_process";`vettd · scan · 3dCritical
Shell execution without sandboxingflaggedsoft spot 2Detected in scripts/assemble-index.test.mjs:5 — `import { spawnSync } from "node:child_process";`vettd · scan · 3dCritical
Shell execution without sandboxingflaggedsoft spot 3Detected in scripts/audio.mjs:23 — `import { spawnSync } from "node:child_process";`vettd · scan · 3dCritical
Shell execution without sandboxingflaggedsoft spot 4Detected in scripts/audio.test.mjs:5 — `import { spawnSync } from "node:child_process";`vettd · scan · 3dCritical
Shell execution without sandboxingflaggedsoft spot 5Detected in scripts/build-frame-colors.test.mjs:2 — `import { spawnSync } from "node:child_process";`vettd · scan · 3dCritical
Shell execution without sandboxingflaggedsoft spot 6Detected in scripts/build-frame-subsets.test.mjs:2 — `import { execFileSync } from "node:child_process";`vettd · scan · 3dCritical
Shell execution without sandboxingflaggedsoft spot 7Detected in scripts/media-contract.test.mjs:7 — `import { spawnSync } from "node:child_process";`vettd · scan · 3dCritical
Shell execution without sandboxingflaggedsoft spot 8Detected in scripts/transitions.test.mjs:2 — `import { spawnSync } from "node:child_process";`vettd · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 9scripts/assemble-index.mjs:54 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 10scripts/assemble-index.mjs:84 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 11scripts/assemble-index.mjs:100 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 12scripts/assemble-index.test.mjs:5 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 13scripts/assemble-index.test.mjs:10 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 14scripts/assemble-index.test.mjs:11 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 15scripts/assemble-index.test.mjs:32 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 16scripts/assemble-index.test.mjs:94 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 17scripts/assemble-index.test.mjs:120 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 18scripts/audio.mjs:23 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 19scripts/audio.mjs:86 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 20scripts/audio.test.mjs:5 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 21scripts/audio.test.mjs:24 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 22scripts/audio.test.mjs:96 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 23scripts/audio.test.mjs:192 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 24scripts/audio.test.mjs:325 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 25scripts/audio.test.mjs:349 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 26scripts/build-frame-colors.test.mjs:2 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 27scripts/build-frame-colors.test.mjs:35 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 28scripts/build-frame-subsets.test.mjs:2 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 29scripts/media-contract.test.mjs:7 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
INJECTION ATTACK detected by YARAflaggedsoft spot 30scripts/media-contract.test.mjs:29 — Script injection patterns: onerror="alert(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 31scripts/media-contract.test.mjs:32 — Pattern detected: spawnSync(cisco · scan · 3dCritical
INJECTION ATTACK detected by YARAflaggedsoft spot 32scripts/media-contract.test.mjs:70 — Script injection patterns: onerror="alert(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 33scripts/media-contract.test.mjs:73 — Pattern detected: spawnSync(cisco · scan · 3dCritical
INJECTION ATTACK detected by YARAflaggedsoft spot 34scripts/media-contract.test.mjs:102 — Script injection patterns: <htmlcisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 35scripts/media-contract.test.mjs:105 — Pattern detected: spawnSync(cisco · scan · 3dCritical
INJECTION ATTACK detected by YARAflaggedsoft spot 36scripts/media-contract.test.mjs:125 — Script injection patterns: <htmlcisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 37scripts/media-contract.test.mjs:128 — Pattern detected: spawnSync(cisco · scan · 3dCritical
INJECTION ATTACK detected by YARAflaggedsoft spot 38scripts/media-contract.test.mjs:148 — Script injection patterns: <htmlcisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 39scripts/media-contract.test.mjs:151 — Pattern detected: spawnSync(cisco · scan · 3dCritical
INJECTION ATTACK detected by YARAflaggedsoft spot 40scripts/media-contract.test.mjs:171 — Script injection patterns: <htmlcisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 41scripts/media-contract.test.mjs:173 — Pattern detected: spawnSync(cisco · scan · 3dCritical
INJECTION ATTACK detected by YARAflaggedsoft spot 42scripts/media-contract.test.mjs:191 — Script injection patterns: <htmlcisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 43scripts/media-contract.test.mjs:193 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 44scripts/transitions.test.mjs:2 — Pattern detected: from "node:child_process"cisco · scan · 3dCritical
Node.js child_process module usage for shell command executionflaggedsoft spot 45scripts/transitions.test.mjs:36 — Pattern detected: spawnSync(cisco · scan · 3dCritical
Script contacts a destination the documentation never mentionsflaggedscripts/captions.mjs:483 — Script contacts or configures 'cdn.jsdelivr.net' but the skill documentation never visibly mentions it. Undocumented network destinations can indicate behaviour the manifest and description do not disclose.cisco · scan · 3dLow
Skill does not specify a licenseflaggedSKILL.md — Skill manifest does not include a 'license' field. Specifying a license helps users understand usage terms.cisco · scan · 3dInfo
behavioral scan passednothing foundNo prompt-injection or jailbreak signals were detected.vettd · scan · 3dnothing found
External URL scan passednothing foundNo external URLs were found in scanned skill text.vettd · scan · 3dnothing found
Name validation passednothing foundThe declared skill name follows the supported naming rules.vettd · scan · 3dnothing found
Reliability & Quality● gradedBmost recent 3d ago7 signals
how it was established7 signals · vettd · scan
show
Unresolvable internal referencesflaggedUnresolvable internal path(s): audio/references/tts.md, audio/scripts/heygen-tts.mjs, references/intent-interview.md, references/setup-providers.md, scripts/carve.mjs, scripts/prefs.mjs, scripts/recipe.mjsvettd · scan · 3dMedium
Checklist patternreadvettd · scan · 3dabsent
Description usage contextreadvettd · scan · 3dpresent
Examplesreadvettd · scan · 3dpresent
Gotchas sectionreadvettd · scan · 3dabsent
Step-by-step workflowreadvettd · scan · 3dabsent
Validation loopreadvettd · scan · 3dpresent
Performance● measured1 measuredmost recent 3d ago2 signals
how it was establishedtiktoken/cl100k_base/skill-md-body · 2 signals · vettd · scan
show
Progressive disclosurereadvettd · scan · 3dpresent
Static context tokensmeasuredvettd · scan · 3d7777
Cost◌ not assessednot assessed0 signals
how it was establishednot assessed; no producer has emitted into this category
Not assessed; no producer has emitted into cost for this asset. That is different from a check that ran and found nothing, which the record would carry as a row of its own.
Compatibility◌ unjudgednot judgedmost recent 3d ago4 signals
how it was established4 signals · vettd · scan
show
CLI helpreadvettd · scan · 3dpresent
Declared environment assumptionsreadvettd · scan · 3d
Declared skill namereadvettd · scan · 3dproduct-launch-video
Structured outputreadvettd · scan · 3dpresent
Popularity◇ context onlynot judgedmost recent today5 signals
how it was establishedgithub-repo-object · 5 signals · github-api · research
show
Forksmeasuredgithub-api · research · today6286
Days since last commitmeasuredgithub-api · research · today0 days
Open issuesmeasuredgithub-api · research · today395
Starsmeasuredgithub-api · research · today69352
Watchersmeasuredgithub-api · research · today181
Characteristics◇ context onlynot judgedmost recent today4 signals
how it was establishedbundle-extension-share · 4 signals · 2 sources · research/scan
show
Declared licensereadvettd · scan · 3d
Primary bundle languageobservedvettd · scan · 3d · conf highJavaScript
Repository linkreadvettd · scan · 3dabsent
Archivedreadgithub-api · research · todayfalse
Coverage6 of 7 categories assessed · shown
Safety
✓ assessed
behavioral scan passed · External URL scan passed · Name validation passed
Reliability & Quality
✓ assessed
7 signals recorded
Performance
✓ assessed
2 signals recorded
Cost
△ not assessed
no producer has emitted for this category
Compatibility
✓ assessed
4 signals recorded
Popularity
✓ assessed
5 signals recorded
Characteristics
✓ assessed
4 signals recorded
Freshness & re-evaluation
assessed3d ago · Cisco AI Defense · Vettd core● current
source stateThe source matches what was scanned. No changes detected.Up to date
re-check policyre-checked against the upstream source on the scheduler's cadencenext check in 11h
re-run whena new release ships, the upstream source changes, or the scanner ruleset is revisedauto-scheduled
Limitations & open conflicts
limitationCost is not assessed: behaviour there is unmeasured, not clean△ gap
conflictno two sources report the same quantity on this record
Verify: does this record describe your copy?
What record 927aca14-21af-49ca-add3-9eba313a611c covers
scannerv11● current
validityassessed 3d ago · Up to date
this record was taken at digest sha256:9148e9bb921d… compare it against the digest your own scan prints
Reproduce: re-run the evidence yourself
runs the same scanners against your own copy; the published record is never overwritten
How this record comparesagainst other published records · full comparison →
Signal kinds
▲ finding: something to act on, carries a severity● measurement: a reproducible quantityƒ estimate: inferred from a sample▪ fact: read directly off the artifact◆ classification: assigned from a taxonomy◌ nothing found: a producer looked and emitted no object◇ context only: described, never graded
Custody marks◐ computed by vettd○ declared by the publisher, as-is△ not assessed: nothing looked