Evaluation report
Warningsfigma-developer-mcp · mcp24713d8· 3 months ago
Every check MetaHub ran on this artifact, grouped by area. Static checks run on the source at publish time; behavioral checks run the artifact in a sandbox and judge what it actually does.
Structural
5 passedRepository is reachable
https://github.com/GLips/Figma-Context-MCP @ 24713d8 — ★ 15,168 · TypeScript · MIT · last push 2 days ago
Manifest detected
kind=mcp slug=figma-developer-mcp · source=package.json
Slug is URL-safe
"figma-developer-mcp" matches /^[a-z0-9][a-z0-9-]{0,62}$/
Slug is unique within kind
No collision found for mcp/figma-developer-mcp
Version is semver
0.13.2
Documentation
5 passedDescription quality
16 words · 97 chars — "Give your coding agent access to your Figma data. Implement designs in any frame…"
README is present and substantial
4,182 chars · 5 sections · 2 code blocks
Tags / topics declared
5 total — figma, mcp, typescript, ai, cursor
README has usage / example sections
found: Getting Started
Homepage / docs URL declared
https://www.framelink.ai
Safety
2 passed1 warningDependencies: known vulnerabilitieswarn
3 high/critical advisories — [email protected] (HIGH: GHSA-hm92-r4w5-c3mj) · [email protected] (HIGH: GHSA-vmh5-mc38-953g) (+1)
Update the affected packages, then re-publish. (`npm audit` shows the same data locally.)
LICENSE file at repo root
LICENSE
No sensitive files in the repo
scanned for .env, credentials.json, *.pem, .ssh/, AWS / GCP configs — none found
Kind-specific
5 passedMCP: launch path
bin: figma-developer-mcp · scripts.start
MCP: @modelcontextprotocol/sdk in dependencies
pinned at "1.29.0"
MCP: SDK version pinned
pinned at "1.29.0"
MCP: ESM package
"type": "module"
MCP: server surface
0 tools
Maintenance
3 passedRecent activity
last push 2 days ago
Tests detected
1 test directory · 18 test files
CI configuration detected
GitHub Actions (2 workflows)
Behavioral
This artifact hasn't produced behavioral results yet: the evaluation sandbox couldn't run it (it may need credentials we don't provide, or a build our environment doesn't support). That's a limitation of our environment, not a verdict on the artifact.