Repository navigation
v0.44.0: fixes from audits 46 to 50
Install: npm install umlimator@0.44.0, or "umlimator": "github:zintaen/umlimator#v0.44.0".
Audits 46 to 50 confirmed 103 findings: 1 high, 33 medium and 69 low. 98 are fixed in seven pull requests (#519, #520 and #521 for audit 46, then one per round: #535, #538, #540 and #543), each code fix with a test that fails without it; audit 50 finding 12 (the gallery's wording about the bike share) went with the bike share in #544. Audit 49 findings 13 to 16 (one medium, three low) are still open: the lane that fixed them was left out when #540 combined that round (Known gaps).
This release holds 24 pull requests since 0.43.0, #518 to #545 (#529 to #531 and #533 were combined into #535): besides the fixes, the map-repo pin (#518), describe() on map views (#525), map line weights (#536), the examples and the docs site's Examples page (#522 to #528, #532, #534, #537, #542, #544), the repository's community files (#539), the README's links (#541) and the CI gate (#545). bench/expected.json changes only because the bench's models changed (the bike share, then bench/models/i59.json in #544): no audit fix moves a hashed layout, the order-states and sales-classes examples are as 0.43.0 left them, and the stress views' crossing pins are unchanged.
The changes a host sees without editing anything: every map line is drawn at weight 1's width at rest, and a weight of 2 or 3 shows only on hover, selection and keyboard focus, with the line's what (or "weight 2 of 3") in its title and accessible name (#536, #543); describe(), paths() and reach() read a version-2 map view's own lines with their labels, steps and latency (#525); an edited line's dot is drawn off its label (#538); validate() warns on more (present-values, stereotype-text, comment-link in more views, a change mark not written in lower case) and no longer calls an interface realization from a component or a port an error (#535, #538, #540, #543); diff() says and marks edited, moved and re-owned members and writes a new diffMarks field on the typed views it lays out (#535, #540, #543); more editing gestures are refused where validate() would call the result an error (#521, #538, #543); the MCP tour tool refuses a tour the page cannot ride (#535, #538); and the bike share and the other retired example files are gone from examples/ (#527, #544), so a link to examples/bike-share.json, examples/bookshop.json or examples/bookshop.html, or to the Bookshop Atlas's api or checkout view, now breaks. What changes for callers:
- Core and layout. A map line's weight shows only on hover, selection and keyboard focus (#536): at rest every line has weight 1's width and arrowhead; a line of weight 2 or 3 grows to its weight's width with its heavier arrowhead when the pointer is on it or on a card at either end, when it or a card at either end is selected, and when its line key has keyboard focus, and its title and accessible name add its
what(all thewhats of the edges it stands for, joined by " / "), else "weight 2 of 3" or "weight 3 of 3". Weight 1 lines say nothing new, and mindmap branches and typed lines are unchanged.describe(),paths()andreach()read a version-2 map view's own lines with their labels, steps and latency (#525): a view with nodiagram, ordiagram: "map", is walked as a map, where it was walked by model line, sodescribe()now says a line's label and step. At rest the flow line is trimmed for the weight 1 arrowhead, and a weighted line draws a second flow line (flowline fl-hv) for its heavy arrowhead that shows in the same states (#543, audit 50 finding 2). An edited line's dot is drawn on the longest stretch of the line clear of its label: in a sweep of the examples with every other line also marked edited, 46 of 84 dots sat under a label before and none do now (audit 48 finding 21; #538).svgOf()draws a map view whose container names itself, or another in a cycle, as its parent, where it overflowed the stack (#538). A map line or cardchangethat is not text draws unmarked, asvalidate()and the typed views already read it (#519).lib/umlimator.d.tsand the schema now describe a map line'schangeas main draws it (added,new,removed,changed,modified, drawn with nostyleneeded) and say it is written in lower case (#519, #535; audit 46 findings 6 and 24, audit 47 finding 4). - diff(), the diff page and stills.
diff()says and marks edited members: a member in both models whose own fields or owner changed is marked changed and said by name ("renames charge to inlet in Battery"), and a retyped part's lost ports are drawn removed beside its new ones (audit 47 finding 1; #535, #543). A member moved to another owner is said once ("moves X out of A into B", no more "changes A (members)") and drawn back removed at its old place, under a fresh id<id>~moved(#540). An added or removed part, port or lane is marked, and a removed one is drawn back (#520). A new public field,view.diffMarks(marksby shape id andgonelines; inlib/umlimator.d.tsand the schema), carries what a typed view draws that is no element or line of its own: the old C4 implied line or SysML containment line of a re-owned element is drawn back removed (audit 47 findings 0 and 14; #535), a deleted container's implied line comes back removed (#543), and a shape drawn from what it reads (a C4 instance or implied line, an IDEF1X entity, an information flow, a class or package name qualified through an owner, an object, a parametric constraint property, a port typed by an interface block) is marked changed only when its drawing changes (#520, #535, #538, #540, #543). A C4 implied line that is new in the picture is marked added; one drawn before stays changed (audit 50 finding 0; #543). Relationshipsdiff()brings back removed no longer join an implied line (#538). On a communication view the message rows carry their marks (audit 46 finding 9, high; #520) and number the live messages as the new model does (#538). An interaction overview's inline interaction marks its messages, lifelines and fragments, and is marked changed when its sequence view changes through its own lines (#520, #538, #540). An added or removed dashed typed line keeps its dash, and a solid one stays solid, so a removed call message draws solid rose (#520, #535). Timing constraints are marked and a removed one is drawn back (#540); a deleted BPMN group is drawn removed (#540); an IDEF1X entity whose only identifying relationship was removed is drawn independent (#535); a removed mindmap topic's branch is no longer drawn solid in its branch colour (#520).diff().viewsleaves out a view listed only through what it refers to or reads when its picture is the same before and after (#535), and lists again a C4 container view whose cards move when a context relationship to its subject is added or removed (audit 48 finding 0, a round 47 regression; #538), and lists a view whose card opens a retitled view when a map card shares that view's id (audit 48 finding 3; #538). The summary names a BPMN lane by its label (#535) and a removed extend's extension point by its name (#538). - validate() and rules. New warnings:
present-values, a port side or interfacepresentvalue the view ignores (component and composite views, #535; internal block and parametric views, #538);stereotype-text, a stereotype stored with its marks such as«entity», on any element (#535; the Stereotypes field now strips one pair);comment-linkon the state machine and use case views (#521), judged on the lines they draw (#535), and on the activity (#535) and information flow views (#543); and "write it in lower case" for a change mark in another letter case, which still draws (#535).realization-targetaccepts a class, component, port, enumeration or data type realizing an interface (#540), so a component or port that realizes one is no longer an error. The warning on a sequence fragment operator that is not text now says so, and how it is drawn (#521). Validating a C4 deployment model is no longer quadratic (#519). - Page, keyboard and accessibility. A line's weight is explained in its title and accessible name, and its key's keyboard focus shows it (#536). A communication row's "Message N of M" counts live rows only (#538). The diff page's change words follow the marks above.
- UML structural. A stereotype or metaclass dragged out of its profile is refused in every view, a type's own
moveTohook included (#521, #535). An interface realization from a component or a port is drawn and checked as the component view always did (#540). Composite structure: the ports on an added part are marked, the ports on a removed part are drawn removed (#520), and F2 or a member row on a part, port, role or collaboration use is linear in its spaces (64,000 spaces: 17 s before, under 250 ms now; #543). - UML behavioural. A comment link between two elements that are not comments is refused in the use case, state machine and interaction overview views (#521). The state machine and interaction overview connect refuse a line that
validate()calls an error (into an initial node, out of a final state, onto a region; #538), and the use case connect refuses an include, extend or generalization from an actor and an association between two use cases (#543); a new state machine or overview line's id istransition1or<from>-<to>, where the canvas used to pick it (#538); a new unguarded line out of an interaction overview decision that has one exit withoutelsegets the guardelse(#538). Timing F2 is linear in its spaces, and a change's or message's text over 4,096 characters is refused (#543). A removed message in another letter case is not numbered (#543). - ER. A comment link between two tables is refused (#521). On the diff page an IDEF1X entity is marked when a relationship it reads changes how it draws, and only then (#520, #535).
- Flowchart. A comment link between two nodes that are not comments is refused (#521).
- DFD. A comment link between two elements that are not comments is refused (#521).
- Information flow.
comment-linkwarns on a link with no comment at either end (#543). A flow conveying a renamed item is marked on the diff page (#520). - C4. All six C4 views refuse a comment link between two elements that are not comments, and
c4.dynamicadds one drawn towards a comment from the comment (#521). The diff page marks a container instance drawn from a changed container (#520) and draws implied lines as the diff bullet says. An implied line standing for planned relationships is no longer drawn and keyed as changed (#520). - SysML. The block definition view adds a comment link drawn from a block to a comment from the comment (#538). The internal block and parametric views warn
present-values(#538). On the diff page an internal block port whose interface block's flow directions flip is marked changed (#540), and a retyped part's lost port is drawn removed (#543). - BPMN. Delete on a lane says how many flow nodes are now in no lane of its pool ("N flow nodes now in no lane of P: drag them into a lane"; #538), counting only those the view shows (#543). Lanes added to or removed from a pool are marked on the diff page (#520).
- Mindmap. A removed topic's branch on the diff page is no longer drawn solid (#520), and the Mermaid mindmap reader reads a shape's text over line breaks as Mermaid does (#540).
- Cloud. Shift+Delete on a group counts what it held as
apply()deletes it: a view's own group is counted and a model service lifted out is not (#521, #535); the deployment and state machine remove hooks follow the same rule (#535). - Readers and writers. Every Mermaid reader reads a character SVG or XML cannot hold, written raw or as an entity code in the diagram's text, as U+FFFD and says so, whether written as an entity code (#535) or raw (C0 controls other than tab, line feed and carriage return, U+FFFE, U+FFFF, lone surrogates; raw U+000B and U+000C included), and so do the Structurizr, DBML and BPMN XML readers (#538);
umlimator.py importdoes the same for entity codes (#538) and raw characters (#540), and keeps compose and Kubernetes keys apart that differ only in such a character (key-2; #543). A quoted or bracketed text runs over line breaks as Mermaid reads it in the mindmap, requirement, class, state (#540) and ER readers (#543), and the requirement writer writes a value holding a line feed in quotes across lines (#543). Mermaid class: a body missing its}is closed at the nextclassornamespaceline and reported (#535, #538), the writer leaves out a member holding{or}and a default whose~would read back as a generic, with a%% not written:line (#538). Mermaid requirement: entity codes are decoded and reported, and the writer writes a#that would read as a code as#35;(#538). BPMN XML: a collaboration's and a lane set's name and documentation are reported (#521), a process in no pool reports the id it will be written with (#521), and with no diagram interchange the view takes a free id afterprocess(#538). - CLI, MCP, the diff Action and the map-repo skill. The MCP
tourtool refuses a tour of fewer than two cards ("needs two cards or more"), or two cards in turn with no line between them on the view (#535), and says "no view shows all these cards" when no view does (#538); a tour with a gap, which the page used to ride skipping it, is refused as a whole. The repository no longer tracks a symlink to an absolute path, and a test guards that (#535). CI's gate job skips the duplicate full run on a push to main whose version is already tagged; a push whose version is not tagged yet runs every check, then the release (#545). The map-repo skill runs v0.43.0 since #518 (REF, SHA = "0.43.0-c04bd48", ...); 0.44.0 ships with that pin, and it moves to v0.44.0 in a follow-up once the tag exists, as it did after 0.43.0. - Security. The readers' U+FFFD replacement (above) keeps imported text from making a still malformed XML, apart from JSON escapes in a requirement hint or a front-matter title (Known gaps). Two F2 parsers lost their quadratic regular expressions (#543). The CLA workflow runs on
pull_request_target, pinned to a commit, and never checks out pull request code;SECURITY.mdsays how to report (#539). - Performance. Validating a C4 deployment model with 1,000 nodes in four views took 2.8 s and now takes 6 ms (#519). Composite F2 on 64,000 spaces: 17 s before, under 250 ms now, and timing F2 is linear in its spaces too (#543). The Mermaid mindmap reader stays linear on an unclosed shape (80,000 lines of
a[xora["xin about 100 ms; #540). The requirement, class, state (#540) and ER (#543) readers find each string's closing line in one pass ahead.diff()lays out more to judge what it marks: measured on the bike share model as it was then (nowtests/fixtures/integration.json), a C4 rename took about 120 ms instead of 30 ms, and relabelling every element about 210 ms instead of 20 ms (#535). - Docs and examples. The docs site's top nav is Guide, API and Examples (#534). The Examples page is a docs page (
docs/examples.md), with Diagrams (the map and the 28 types), Atlas and In an app; each type has its own page (docs/gallery/<type>.md) framing the page the site build renders fromexamples/types/<type>.json, andexamples/index.htmlredirects there keeping its#fragment(#537). Each diagram type opens on one full example showing every element and line kind it draws, with an alternative view only for a choice that cannot share the picture, and the Atlas holds two whole businesses: the new Umlimator Atlas (examples/umlimator-atlas.json; #534) and the Bookshop Atlas, rebuilt at the same path (examples/bookshop-atlas.json, retired in #527 and written again in #542): its root view is nowoverview, and itsapiandcheckoutviews are gone. Retired fromexamples/(#527, #544):bike-share.json,bookshop.jsonand.html,clinic.dsland.json,weather.json,assistant.json,states.json,ebike-atlas.json, theapiandoverviewstills,stills/.stills.jsonand theride-endandmatchtraces; tests readtests/fixtures/integration.json(the bike share as a moped share) and the benchbench/models/, andtests/showcase.test.mjsonly smoke-checks the examples. The README's links and pictures are absolute, so the npm page this release publishes does not break when a file moves (#541). The repository hasCONTRIBUTING.md,CODE_OF_CONDUCT.md,SECURITY.md,SUPPORT.md, issue forms and a pull request template, an individual CLA (CLA.md), a trademark policy (TRADEMARKS.md) and funding links (.github/FUNDING.yml,package.jsonfunding, a README badge and the site's footer; #539). Corrections: the 0.43.0 section was corrected in place where it was wrong when written (the C4 palette, the comment link and stereotype gaps, and what the 0.43.0 d.ts and schema say; #519, #521, #535); the CLI guide's PDF heading names a view the Umlimator Atlas has (#538). - Known gaps. The 0.43.0 list still holds apart from the items its corrected text already gives as closed (the comment link and stereotype refusals, #519 to #521); this release closes none of its other items by name, and they were not re-checked item by item. Audit 49 findings 13 to 16, checked on main:
docs/guide/cli.md'sstills ... --views overview,apiandcheck page.html --views 'pic-*'name views the Umlimator Atlas does not have, so both stop with exit 1; a weighted line'swhatgoes into its title and accessible name as raw Markdown;lib/umlimator.d.tsand the schema still say a weight is drawn as the line's width;examples/README.mdandexamples/monorepo.pystill say a heavier line. Still open from the 0.43.0 list, checked again on main:validate()says nothing of a hand-written comment link between two elements that are not comments in the ER, flowchart, DFD, C4 and SysML requirement views; a timing view'stimeline.changescarry no mark, a removed entry is not drawn back on the diff page, and the summary says only "(timeline)". New from rounds 46 to 50, each checked on main with a small script: a stereotype already stored with its marks draws doubled (««entity»»), whichstereotype-textwarns of; a card's title and accessible name keep a Markdown link in itswhatas written; the Mermaid requirement reader keeps a JSON escape such as\u001bin a%% text:hint as a raw control character, and every Mermaid reader keeps one in a double-quoted front-mattertitleas a raw control character, with no report; and in compose, adepends_onthat names the renamed second of two keys points at the first service. The lane notes report further gaps that were not re-checked for this release: on the diff page a reply to a removed call still names the call's old number,describe()counts removed messages, and an inline lifeline stem is not faded for a removed lifeline (round 48); a member moved to the top level, with no new owner, is not said or drawn back, the moved ghost's id<id>~movedshows as a shape id, and the summary can read "moves amount out of Money into Money" (round 49);diffMarks{marks:{line:'none'}}is left on a viewdiff().viewsdoes not list (round 50); and the Mermaid writers write characters XML cannot hold raw (round 47). - Size:
lib/umlimator.js, what a map host loads, is 264.7 kB (264,692 B) withgzip -9(812,423 B raw), 60.46% over 0.16.0's 164,954 B and up 8,013 B from 0.43.0, which this gzip measures at 256,679 B (786,054 B raw; the 0.43.0 note printed 256,692 B).lib/umlimator-all.jsis 787.6 kB (787,630 B; 2,496,112 B raw), up 24,750 B from 762,880 B as this gzip measures it (2,421,838 B raw; the 0.43.0 note printed 762,897 B). The npm package is 1,111.5 kB (npm pack --dry-run; 1,077.3 kB at 0.43.0). There is no core size cap until 1.0.0 (the maintainer's decision of 15 Nov 2026): sizes are reported each release and a budget is set at 1.0.0.