Metrics to compare against
List of metrics:
- License
- GitHub popularity: Number of followers/forks/bugs/commits/recent activity
- Rendering engines: WebGL/SVG/Canvas/etc.
- Platforms: NodeJS, Browsers
- Performance: Graph size vs FPS
- Supported layout algorithms
- Library size
What else?
Here some more ideas:
- Feature richness, flexibility
- Styling options (can you easily style it to match your websites layout)
- Ease of use, learning curve, required skills
- Dynamic/static rendering (static drawing or a dynamic graph where you can move/zoom around)
- Supported data formats (JSON, DOT, ...)
- Editable or view-only (dynamic/static data)
- Platforms: NodeJS, Browser, Mobile devices (Extension to your no. 4)
Very nice! One more: Memory usage comparison.
(1) Perhaps under platforms, you may also want to include supported package managers and require() environments -- e.g. CommonJS, AMD.
(2) Measurements of memory and FPS seem like a nice idea, but in practice those measurements won't be useful unless you provide jsperfs. A manual measurement is not practical to keep uptodate.
(3) Points like "ease of use" are subjective and qualitative so perhaps best belong in a text review section outside of a table of metrics. "Easy", "medium", and "hard" probably aren't very useful in a comparison matrix.
Added information about average "issue closed" time. Check it out: http://anvaka.github.io/graph-drawing-libraries/#/all
This information is based on https://github.com/hstove/issue_stats