svgdotjs/svg.js

The lightweight library for manipulating and animating SVG

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 18 minutes ago
Added to GitGenius on September 5th, 2026
Created on December 15th, 2012
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 1,078
Total Stargazers: 11,821 (+0)
Total Subscribers: 266 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.8 hours
Mean response time: 16.5 days
90th percentile: 64.4 days
Tracked items: 24

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 9% of issues opened in the past year have been closed. Three people close 83% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

  • wontfix (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

SVG.js is a lightweight library for manipulating and animating SVG graphics in JavaScript without external dependencies.

The library addresses the complexity of working with SVG through the DOM by providing a fluent API that simplifies common operations like creating shapes, modifying attributes, and applying animations. Rather than requiring developers to write verbose SVG markup or complex DOM manipulation code, SVG.js wraps these tasks in chainable methods that read naturally and reduce boilerplate.

Developers should choose this tool when building interactive graphics, data visualizations, or animations that need to run in browsers without adding significant bundle weight. It suits projects where SVG manipulation is a core feature but a full graphics framework would be overkill. The library is available through npm, yarn, and multiple CDN options, making it flexible for different project setups.

The project maintains steady activity with regular commits addressing bug fixes and feature enhancements. Development follows a structured approach with pull requests reviewed before merging, and the maintainers respond to issues with technical guidance. The codebase receives ongoing refinement rather than major architectural shifts, suggesting a mature tool focused on stability and incremental improvement.