buildpacks/spec

Specification for Cloud Native Buildpacks

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

buildpacks/spec has 250+ stars and 70+ forks on GitHub, is written in Shell, and was last pushed on Dec 19, 2025. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Type:Documentation / SpecificationCategory(s):Containers & RuntimesDocumentation ToolsCloud Native & Infrastructure
Added to GitGenius on October 15th, 2026
Created on August 26th, 2018
Open Issues & Pull Requests: 32 (+0)
GitHub issues: Enabled
Number of forks: 72
Total Stargazers: 272 (+0)
Total Subscribers: 14 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 days
Mean response time: 21.5 days
90th percentile: 101.2 days
Tracked items: 7

Maintainer activity

2 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.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • api/buildpack (2)
  • api/platform (1)
  • enhancement (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Cloud Native Buildpacks Specification is a formal specification that defines the interactions between platforms, lifecycles, buildpacks, and applications for transforming source code into OCI images and enabling automated testing.

The specification addresses the need for a standardized contract governing how buildpacks—software that transforms application source code into runnable artifacts—interact with lifecycles that orchestrate them and platforms that expose buildpack functionality to end users. It establishes precise requirements using RFC 2119 key words to ensure compliance, with explicit handling of operating system differences between Linux and Windows stacks, including path notation conventions and shell requirements.

Organizations building container platforms, buildpack implementations, or tools that integrate with Cloud Native Buildpacks should adopt this specification as the authoritative reference. It suits projects that need to ensure interoperability across different buildpack ecosystems or that are implementing platform, lifecycle, or buildpack components. The specification covers the Buildpack Interface, Platform Interface, Distribution, and several extensions including Bindings, Buildpack Registry, and Project Descriptor specifications.

The project maintains active development with regular updates to specification documents and extensions. Contributions flow steadily across multiple specification sections, indicating ongoing refinement of the standard. The maintainers engage with issues and pull requests addressing clarifications and enhancements to the specification language and requirements. The project tracks API versions explicitly, suggesting careful attention to backward compatibility and versioning practices.