microsoft/flint-chart

πŸͺ„ Flint is a visualization language that lets AI agents reliably create expressive, good-looking charts from simple, human-editable chart specs.

View on GitHub β†—Jump to charts ↓Open shareable report β†’

Summary Information

Updated 56 minutes ago
Added to GitGenius on September 16th, 2026
Created on May 13th, 2026
Open Issues & Pull Requests: 32 (+0)
GitHub issues: Enabled
Number of forks: 236
Total Stargazers: 4,254 (+0)
Total Subscribers: 12 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 34.7 hours
Mean response time: 2.1 days
90th percentile: 4.6 days
Tracked items: 13

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 14
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 44 days
Stale 30+ days: 12
Stale 90+ days: 0

Recent activity

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

Top labels

No label distribution available yet.

Detailed Description

Flint is a visualization language that lets AI agents reliably create expressive, good-looking charts from simple, human-editable chart specs.

Flint addresses the challenge of generating charts through AI systems, which often produce inconsistent or poorly formatted output when using traditional charting libraries. The tool works by defining a declarative specification language that AI agents can learn and apply reliably. Rather than requiring agents to write imperative charting code, Flint provides a human-readable format that captures chart intent in a way that both machines and people can understand and edit. This approach reduces the friction between what an AI system generates and what actually renders as a usable visualization.

Flint suits projects where AI systems need to produce charts programmatically, particularly in applications that combine language models with data visualization. It is especially valuable when chart specifications need to be inspected, modified, or debugged by humans after generation. The tool's emphasis on human-editable specs makes it useful in workflows where the output of an AI system serves as an intermediate artifact rather than a final product. Teams building AI agents that work with data should consider Flint if they find that existing charting libraries create a gap between what the agent intends and what actually displays.

The project maintains active development with regular commits across its codebase. Pull requests receive timely review and integration. The maintainers respond to issues and incorporate external contributions. Documentation is kept current alongside code changes. The project demonstrates sustained attention to both new features and the maintenance of existing functionality.