score-spec/score-compose

Reference implementation for docker-compose target platform support

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

score-spec/score-compose has 450+ stars and 60+ 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 26 minutes ago
Added to GitGenius on October 15th, 2026
Created on October 17th, 2022
Open Issues & Pull Requests: 16 (+0)
GitHub issues: Enabled
Number of forks: 65
Total Stargazers: 456 (+0)
Total Subscribers: 4 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.1 hours
Mean response time: 16.4 days
90th percentile: 25.9 days
Tracked items: 41

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: 526 days
Stale 30+ days: 6
Stale 90+ days: 6

Recent activity

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

Top labels

  • enhancement (21)
  • good first issue (17)
  • help wanted (17)
  • bug (15)
  • go (12)
  • discussion (5)
  • question (4)
  • contribfest (3)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Score-compose is a reference implementation of the Score specification for Docker Compose, primarily used for local development.

Score-compose solves the problem of translating platform-agnostic workload definitions into Docker Compose configurations for local development environments. It implements the Score specification, which allows developers to define their application workloads once and deploy them across different platforms. The tool parses Score files and generates corresponding Docker Compose manifests, handling the mapping of abstract workload requirements to concrete Compose services and resources.

Developers should choose score-compose when working locally with Docker Compose and needing to test workloads defined in the Score format before deploying to production platforms. It suits projects that use Score as their workload definition standard and want a lightweight local development experience. The tool includes a resource provisioning system that automatically supplies and configures attached services such as databases, queues, storage, and message brokers. Most Score specification features are supported, though container resource limits and HTTP probes are validated but ignored, as the Compose specification lacks reliable equivalents. Out-of-the-box resource support includes environment variables, service ports, volumes, and databases like PostgreSQL, MySQL, and MongoDB, along with Redis, S3, DNS, AMQP, Kafka, Elasticsearch, and MSSQL.

The project maintains active issue tracking with specific features like HTTP probe conversion marked for future work. Development activity shows ongoing refinement of Score specification compliance and resource provisioning capabilities.