buildpacks/lifecycle

Reference implementation of the Cloud Native Buildpacks lifecycle

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

buildpacks/lifecycle has 200+ stars and 100+ forks on GitHub, is written in Go, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on October 15th, 2026
Created on April 12th, 2018
Open Issues & Pull Requests: 139 (+0)
GitHub issues: Enabled
Number of forks: 127
Total Stargazers: 215 (+0)
Total Subscribers: 17 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 days
Mean response time: 22.8 days
90th percentile: 92.6 days
Tracked items: 56

Maintainer activity

1 person 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

Roughly one issue in two opened in the past year never receives a reply. 88% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 49% of issues opened in the past year have been closed. Three people close 98% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 40
New in 7 days: 2
Closed in 7 days: 0
Avg open age: 321 days
Stale 30+ days: 35
Stale 90+ days: 26

Recent activity

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

Top labels

  • type/bug (62)
  • status/triage (54)
  • cve (27)
  • status/ready (9)
  • type/enhancement (7)
  • type/chore (4)
  • status/discussion-needed (3)
  • status/awaiting-response (2)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Lifecycle is a reference implementation of the Cloud Native Buildpacks specification that orchestrates the build and execution phases for container image creation.

The tool solves the problem of standardizing how applications are transformed into container images by implementing the buildpacks lifecycle specification. It breaks the build process into distinct phases: the analyzer reads metadata from previous images, the detector selects appropriate buildpacks, the restorer retrieves cached layers, the builder executes buildpack logic, and the exporter produces the final image. These phases can be run individually or combined through a single creator command. For runtime, the launcher invokes the chosen process type. The tool also provides a rebaser for updating base layers in existing images without rebuilding.

Adoption suits organizations building container platforms or CI/CD systems that need a standards-compliant buildpacks implementation. The tool is designed for platform builders rather than end users, as it provides the core execution engine that platforms integrate. Teams implementing the Cloud Native Buildpacks specification will find this the authoritative reference implementation to build against.

The project maintains broad API compatibility across multiple platform and buildpack API versions. Development follows a structured contribution process with dedicated documentation for contributors, development workflows, and release procedures.