Verified history
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean GitHub Packages has never changed. Undated values are kept in the current baseline below instead of being presented as history.
Current monitored baseline
HyperObserve currently monitors 2 scoped observations for GitHub Packages. The baseline covers included package storage, included monthly transfer. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| included package storageFree organizations also receive 500 MB included storage. | Free: 500 MB; Pro/Team: 2 GB; Enterprise Cloud: 50 GB | Account plan | GitHubAug 22, 2026 |
| included monthly transferPackage transfer resets monthly and some GitHub Actions downloads are treated differently. | Free: 1 GB; Pro/Team: 10 GB; Enterprise Cloud: 100 GB | Account plan | GitHubAug 22, 2026 |
Tracked constraints and impact
Package storage and monthly transfer included with each GitHub plan. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.
GitHub Packages Storage Limits by Plan
GitHub Packages Storage Limits by Plan, verified against GitHub Packages's official documentation with scope, implementation impact, caveats, and a direct check.
GitHub Packages Data Transfer Limits
GitHub Packages Data Transfer Limits, verified against GitHub Packages's official documentation with scope, implementation impact, caveats, and a direct check.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.
Official sources monitored
These first-party documents support the current GitHub Packages baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
GitHub Packages storage and monthly transfer allowances