canonical/snapcraft

Package, distribute, and update any app for Linux and IoT.

Owned by Canonical

View on GitHub ↗Jump to charts ↓

canonical/snapcraft has 1k+ stars and 550+ forks on GitHub, is written in Python, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 10 minutes ago
Added to GitGenius on October 12th, 2026
Created on October 29th, 2015
Open Issues & Pull Requests: 229 (+0)
GitHub issues: Enabled
Number of forks: 562
Total Stargazers: 1,289 (+0)
Total Subscribers: 36 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.2 days
Mean response time: 79.3 days
90th percentile: 340.3 days
Tracked items: 502

Maintainer activity

19 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 11% of issues opened in the past year have never received a reply. 70% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "Status: Needs information" is answered fastest, typically in about 20 hours, while "Type: Cleanup" waits about 2 weeks. 57% of tracked open issues have had no activity in three months. 63% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 192
New in 7 days: 4
Closed in 7 days: 3
Avg open age: 522 days
Stale 30+ days: 156
Stale 90+ days: 147

Recent activity

Opened in 7 days: 3
Closed in 7 days: 3
Comments in 7 days: 2
Events in 7 days: 4

Top labels

  • Status: Triaged (271)
  • Type: Enhancement (127)
  • Type: Bug (77)
  • Type: Documentation (54)
  • good first issue (26)
  • Status: Needs information (16)
  • Type: Cleanup (12)
  • Type: Question (12)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Snapcraft is a packaging and distribution tool that enables developers to build, publish, and maintain applications for Linux and IoT devices through the snap format.

The tool addresses the fragmentation problem in Linux application distribution, where different distributions use incompatible package managers and formats. Snapcraft solves this by allowing developers to package their applications once and deploy them across any Linux distribution and IoT platform. It handles the creation of snap packages, which are self-contained bundles that include the application and its dependencies, and provides mechanisms for automatic updates and version management across diverse target systems.

Snapcraft suits projects targeting broad Linux adoption or IoT deployments where maintaining separate packages for different distributions becomes burdensome. It works well for applications that need consistent behavior across Ubuntu, Fedora, Debian, and other distributions, as well as for IoT scenarios where update management and confinement are important. The tool is particularly valuable for teams wanting to reduce packaging overhead while ensuring their applications reach users on any Linux system without distribution-specific modifications.

The project maintains active development with regular updates to core functionality and tooling. The codebase shows ongoing refinement of the build system and snap creation workflows. The maintainers actively address issues and incorporate feedback from the packaging community. Development focuses on improving the developer experience around snap creation and distribution, with attention to both the command-line interface and underlying build infrastructure. The project demonstrates sustained investment in keeping pace with evolving Linux packaging needs and IoT requirements.