A simple web-based tool for Spriting and Pixel art.
Topics
Jump into the topic listings this repository belongs to.
Measured history
Weekly GitHub totals with 30, 90, and 180 day views.
Jun 14, 2026
Current0
Previous1
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
144 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Jun 14, 2026
Current0
Previous0
Weekly total
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
144 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Jun 14, 2026
Current0
Previous0
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
144 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Jun 14, 2026
Current0
Previous0
Weekly total
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
144 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Jun 14, 2026
Current0
Previous0
Weekly total
GitHub API observation. Historical values render only when the source provides a real observation for that day.
144 observed daily rows. Missing days are not fabricated.
| Date | Value |
|---|
Jun 7, 2026
Current0.00
Previous0.00
Daily ratio — a gap means nothing was opened that day
How this works: each day's value is issues closed that day ÷ issues opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more issues than arrived that day.
GitHub Search issue totals queried for exact UTC days; rolling values are sums of proven daily counts.
7 observed daily rows. Missing days are not fabricated.
Per-day formula: issues closed that day ÷ issues opened that day; blank when nothing was opened (a gap, not a zero).
| Date | Issues opened | Issues closed | Stored score |
|---|
May 28, 2026
Current0.00
Previous0.00
Daily ratio — a gap means nothing was opened that day
How this works: each day's value is pull requests closed that day ÷ pull requests opened that day. Days when nothing was opened render as gaps — never a rolling average or a made-up zero. Values above 1 mean the project closed more pull requests than arrived that day.
GitHub Search pull-request totals queried for exact UTC days; rolling values are sums of proven daily counts.
16 observed daily rows. Missing days are not fabricated.
Per-day formula: pull requests closed that day ÷ pull requests opened that day; blank when nothing was opened (a gap, not a zero).
| Date | PRs opened | PRs closed | Stored score |
|---|
Join the conversation
Share what you know about piskel — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Explain what worked, what broke down, and what another team should know before adopting piskel.
Project Q&A
Browse implementation threads tied directly to piskelapp/piskel. Each question links through to the full answer page.
Be the first to ask how teams run piskel in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses piskel — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post