Ericsson/PlantUML-Interactive-Editor

A graphical editor for PlantUML diagrams

Owned by Ericsson

View on GitHub ↗Jump to charts ↓

Ericsson/PlantUML-Interactive-Editor has 70+ stars and 10+ forks on GitHub, is written in Python, and was last pushed on Oct 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 minutes ago
Added to GitGenius on October 10th, 2026
Created on September 24th, 2024
Open Issues & Pull Requests: 41 (+0)
GitHub issues: Enabled
Number of forks: 12
Total Stargazers: 74 (+0)
Total Subscribers: 4 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.2 days
Mean response time: 35.0 days
90th percentile: 82.9 days
Tracked items: 120

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in four opened in the past year never receives a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 67% of issues opened in the past year have been closed, leaving a working backlog. Three people close 100% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 40
New in 7 days: 0
Closed in 7 days: 11
Avg open age: 128 days
Stale 30+ days: 1
Stale 90+ days: 0

Recent activity

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

Top labels

  • enhancement (14)
  • extension (5)
  • bug (4)
  • dependencies (2)
  • documentation (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

PlantUML Interactive Editor is a graphical editor for PlantUML diagrams that enables real-time editing and visualization of diagram code.

The tool addresses the friction of working with PlantUML by offering dual editing modes: you can modify diagrams through direct graphical interaction with elements or by editing the underlying PlantUML code, switching between whichever approach suits the moment. As you type or interact, the diagram updates instantly, letting you see the results of your changes without manual compilation steps. The editor supports activity and sequence diagrams with features like right-click context menus for element operations, double-click editing of text, pan and zoom controls, and bidirectional highlighting that connects code lines to their corresponding diagram elements.

The tool is most suitable for teams and individuals already committed to PlantUML who want a smoother authoring experience than text-only editors provide. It works best for those who value the ability to switch fluidly between code and graphical editing depending on the task at hand. The interactive element manipulation appeals to users who prefer visual design workflows, while the code editor remains available for those who want precise control or need to work with PlantUML features not yet exposed in the graphical interface. A detailed feature list documenting supported and unsupported capabilities is provided to help assess coverage for your specific diagram types.

Development activity shows consistent engagement with the codebase through regular commits addressing both features and maintenance. The project maintains automated test coverage for both Python and JavaScript components, with tooling in place to measure and track coverage metrics. Documentation is actively maintained alongside code changes, including a dedicated features file that tracks implementation status. The presence of a development setup using a package manager and clear testing procedures indicates an organized approach to code quality and contributor onboarding.