Platane/snk

🟩⬜ Generates a snake game from a github user contributions graph and output a screen capture as animated svg or gif

View on GitHub ↗Jump to charts ↓Open shareable report →

Summary Information

Updated 38 minutes ago
Added to GitGenius on September 11th, 2026
Created on July 15th, 2020
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 2,306
Total Stargazers: 6,083 (+0)
Total Subscribers: 17 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.2 days
Mean response time: 18.0 days
90th percentile: 80.8 days
Tracked items: 29

How this project is maintained

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

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 108 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

No label distribution available yet.

Detailed Description

snk is a GitHub Actions tool that generates an animated snake game visualization from a user's GitHub contribution graph.

The tool solves the problem of creating engaging profile README content by transforming contribution data into a playable snake game animation. It fetches a GitHub user's contribution graph and generates a snake path that consumes the contribution cells in sequence, producing output as either an animated SVG or GIF. Colors can be customized, and the tool supports dark mode through GitHub's native image theme syntax.

The project suits developers who want to add dynamic, personalized content to their GitHub profile README. It works best as an automated workflow that regenerates the visualization daily via GitHub Actions, keeping the animation fresh with new contribution data. An interactive demo is available on the project's homepage for testing before integration.

The project does not accept pull requests, with the maintainer preferring to discuss any API or implementation changes through issues first. Issue reporting and fixes are welcomed, but the contribution model is intentionally restrictive around core changes.