lewish/asciiflow

ASCIIFlow

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 19 minutes ago
Added to GitGenius on September 11th, 2026
Created on January 5th, 2014
Open Issues & Pull Requests: 33 (+0)
GitHub issues: Enabled
Number of forks: 421
Total Stargazers: 5,914 (+0)
Total Subscribers: 52 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 210.8 days
Mean response time: 487.7 days
90th percentile: 1539.6 days
Tracked items: 61

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 96% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 2% of issues opened in the past year have been closed. Three people close 98% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 24
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 1,270 days
Stale 30+ days: 21
Stale 90+ days: 15

Recent activity

Opened in 7 days: 2
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (32)
  • bug (18)
  • duplicate (6)
  • question (3)

Most active issues this week

Detailed Description

ASCIIFlow is a web-based ASCII diagram drawing tool that runs entirely in the browser.

The tool addresses the need to create ASCII art diagrams programmatically and interactively without server-side processing. It provides a client-side application where users can draw ASCII diagrams through a graphical interface, then export the resulting text-based diagrams for use in documentation, code comments, or anywhere ASCII art is needed.

ASCIIFlow suits developers and technical writers who need to create flowcharts, architecture diagrams, or other visual representations in ASCII format for inclusion in plain-text documents, version control systems, or terminals. The tool is particularly valuable for those working in environments where rich graphics are impractical or where ASCII diagrams integrate naturally with existing workflows. Since it runs entirely client-side, there are no server dependencies or privacy concerns about diagram content.

The project receives steady real-world usage from outside adopters who report issues and request features. However, response times to issues and pull requests are slow, often taking weeks or longer for initial engagement. Work in the issue tracker centers on enhancements, bug fixes, and user questions, reflecting an active user base bringing feature requests and problem reports rather than the core team driving the development agenda.