flutter/packages

A collection of useful packages maintained by the Flutter team

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 23 minutes ago
Added to GitGenius on September 12th, 2026
Created on August 1st, 2017
Open Issues & Pull Requests: 232 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 3,929
Total Stargazers: 5,305 (+0)
Total Subscribers: 116 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Flutter Packages is a collection of first-party packages maintained by the Flutter team that extend the capabilities of the Flutter framework.

The repository addresses the need for officially supported, well-maintained packages that solve common development problems in Flutter applications. Rather than requiring developers to search for third-party solutions, the Flutter team provides a curated set of packages covering essential functionality. These packages are developed and maintained directly by the core Flutter team, ensuring they follow framework best practices and remain compatible with Flutter's evolution.

Developers should adopt these packages when building Flutter applications that require functionality the core framework does not provide. The packages are particularly suitable for projects that prioritize stability and long-term maintenance, since they receive direct support from the Flutter team. The collection is available both in this repository and on pub.dev, making them accessible through standard package management workflows. These are the official first-party packages; developers building their own packages for the Flutter ecosystem should publish independently to pub.dev rather than contributing to this repository.

The project maintains a clear separation between issue tracking and development: issues and feature requests are filed in the main Flutter repository and labeled "package" rather than in this repository itself. The contribution process is structured to direct external package developers toward the general package development documentation rather than this repository, which is reserved for the core team's own packages. Pull requests for changes to existing packages in the repository follow a dedicated contribution guide, indicating an established review process for modifications to the maintained collection.