Enterprise DNAEnterprise DNA

Skills

ai-figure

by hustcc

🧑‍🎨 Clean SVG flowchart renderer — define nodes & edges, get beautiful diagrams. Works in browser and Node.js.

Our verdict

Not reviewed yet

We have not reviewed ai-figure yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About ai-figure

A TypeScript library that renders clean SVG flowcharts from defined nodes and edges. It operates in both browser and Node.js environments, producing diagrams as SVG output.

Best for

Developers needing a simple, dependency-free SVG flow diagram generator in TypeScript projects.

Use cases

  • Generate flowcharts from structured data in web applications
  • Create diagrams in server-side Node.js scripts for reports or documentation
  • Render node-edge graphs as scalable vector graphics for presentations

Notes

30 stars on GitHub. Last updated 2026-06-11. Licensed MIT.

Pros

  • Lightweight design focused on clean SVG output
  • Cross-platform compatibility with browser and Node.js
  • Simple API for defining nodes and edges

Cons

  • Low star count suggests limited community adoption
  • Feature set is likely minimal, lacking advanced layout algorithms
  • No indication of interactive editing capabilities

Key facts

What we have checked

Days since the last commit
156
Checked GitHub
GitHub forks
1
Checked GitHub
GitHub stars
30
Checked GitHub
Open issues
1
Checked GitHub
Releases in the last 90 days
0
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

Stars and usage

How ai-figure is growing

GitHub stars

30 to 30

stars. 1 Nov 2026 to 14 Nov 2026, 3 readings.

Source: GitHub. Checked .

Health and security

Is ai-figure looked after, and what do its setup files show

Health score

31 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity18.7 of 30Last push 156 days ago
Releases0 of 150 releases in 90 days
Issue repliesNot countedThe latest check has no issue response reading (fewer than 3 measured issues, or issues switched off)
Maintainer0 of 15Owned by a single user
Official sourceNot countedMCP servers only

Security check static checks

40 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-skill-static-v1 main@cbe46853d60f. What it checks

  • Critical Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are used (affects next 16.2.4, pinned in site/package.json).
  • Critical Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used (affects next 16.2.4, pinned in site/package.json).
  • Critical Next.js: Unauthenticated Remote Code Execution in `use cache` functions returning typed arrays (affects next 16.2.4, pinned in site/package.json).
  • Critical Next.js: Unauthenticated Remote Code Execution on windows-hosted servers (affects next 16.2.4, pinned in site/package.json).
  • Critical Next.js: Remote Code Execution in next/og ImageResponse (affects next 16.2.4, pinned in site/package.json).
  • High Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes (affects next 16.2.4, pinned in site/package.json).
  • High Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up (affects next 16.2.4, pinned in site/package.json).
  • High Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n (affects next 16.2.4, pinned in site/package.json).
  • High Next.js has a Middleware / Proxy bypass through dynamic route parameter injection (affects next 16.2.4, pinned in site/package.json).
  • High Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale (affects next 16.2.4, pinned in site/package.json).
  • High Next.js: Server-Side Request Forgery in Server Actions on custom servers (affects next 16.2.4, pinned in site/package.json).
  • High Next.js Vulnerable to Denial of Service with Server Components (affects next 16.2.4, pinned in site/package.json).
  • High Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades (affects next 16.2.4, pinned in site/package.json).
  • High Next.js has Server-Side Request Forgery in Image Optimization (affects next 16.2.4, pinned in site/package.json).
  • High Next.js: Denial of Service in App Router using Server Actions (affects next 16.2.4, pinned in site/package.json).
  • High Next.js vulnerable to Denial of Service via connection exhaustion in applications using Cache Components (affects next 16.2.4, pinned in site/package.json).
  • High Next.js: Denial of Service in App Router using Server Actions (affects next 16.2.4, pinned in site/package.json).
  • High Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname (affects next 16.2.4, pinned in site/package.json).
  • Medium Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences (affects next 16.2.4, pinned in site/package.json).
  • Medium Next.js: Unbounded Server Action payload in Edge runtime (affects next 16.2.4, pinned in site/package.json).
  • Medium Next.js has cache poisoning of SSG and ISR pages in self-hosted applications (affects next 16.2.4, pinned in site/package.json).
  • Medium Next.js: Cache confusion of response bodies for requests with bodies (affects next 16.2.4, pinned in site/package.json).
  • Medium Next.js: Unauthenticated disclosure of internal Server Function endpoints (affects next 16.2.4, pinned in site/package.json).
  • Medium Next.js has information disclosure in App Router metadata image routes via dynamicParams bypass (affects next 16.2.4, pinned in site/package.json).
  • Medium Next.js vulnerable to cross-site scripting in App Router applications using CSP nonces (affects next 16.2.4, pinned in site/package.json).
  • Medium Next.js has cross-site scripting in beforeInteractive scripts with untrusted input (affects next 16.2.4, pinned in site/package.json).
  • Medium Next.js has a Denial of Service in the Image Optimization API (affects next 16.2.4, pinned in site/package.json).
  • Medium Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service (affects next 16.2.4, pinned in site/package.json).
  • Medium Next.js: Denial of Service in the Image Optimization API using SVGs (affects next 16.2.4, pinned in site/package.json).
  • Medium Next.js vulnerable to cache poisoning in React Server Component responses (affects next 16.2.4, pinned in site/package.json).
  • Low Next.js has information disclosure in development server's Model Context Protocol endpoint (affects next 16.2.4, pinned in site/package.json).
  • Low Next.js's Middleware / Proxy redirects can be cache-poisoned (affects next 16.2.4, pinned in site/package.json).
  • Low Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting (affects next 16.2.4, pinned in site/package.json).
  • Note 4 of 7 packages are not pinned to one version, so only the malicious packages list was checked for them, not version advisories.

Alternatives

Alternatives to ai-figure

RecordTypeHow we knowChecked
blueprint-figureThis is an alternative to itSkillMatched from the listing text
Diagram DesignThis is an alternative to itSkillMatched from the listing text

Compare

Compare ai-figure side by side

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

  1. Security finding

    Source: osv.dev

  2. Security finding

    Source: osv.dev

  3. Security finding

    Source: osv.dev

  4. Security finding

    Source: osv.dev

  5. Security finding

    Source: osv.dev

  6. Security finding

    Source: osv.dev

  7. Security finding

    Source: osv.dev

  8. Security finding

    Source: osv.dev

  9. Security finding

    Source: osv.dev

  10. Security finding

    Source: osv.dev

  11. Security finding

    Source: osv.dev

  12. Security finding

    Source: osv.dev

  13. Security finding

    Source: osv.dev

  14. Security finding

    Source: osv.dev

  15. Security finding

    Source: osv.dev

  16. Security finding

    Source: osv.dev

  17. Security finding

    Source: osv.dev

  18. Security finding

    Source: osv.dev

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.