score-spec/spec

The Score Specification provides a developer-centric and platform-agnostic Workload specification to improve developer productivity and experience. It...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 24 minutes ago
Added to GitGenius on September 8th, 2026
Created on October 31st, 2022
Open Issues & Pull Requests: 13 (+0)
GitHub issues: Enabled
Number of forks: 2,140
Total Stargazers: 8,092 (+0)
Total Subscribers: 225 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.2 hours
Mean response time: 7.8 days
90th percentile: 33.0 days
Tracked items: 19

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 1% of issues opened in the past year have been closed. Three people close 100% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 188 days
Stale 30+ days: 9
Stale 90+ days: 5

Recent activity

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

Top labels

  • new feature/idea (9)
  • bug (5)
  • question (4)
  • help wanted (2)
  • lfx-mentorship (2)
  • good first issue (1)
  • invalid (1)

Most active issues this week

Detailed Description

Score is a platform-agnostic workload specification that enables developers to describe cloud-native application configuration in a vendor-neutral way.

Score addresses the problem of configuration inconsistency across environments and the cognitive burden of learning platform-specific syntax for tools like Docker Compose and Kubernetes. It works by letting developers declare workload requirements—such as databases and event queues—in a single specification file using familiar concepts, without committing to any particular platform or tool. The specification separates environment-agnostic configuration from environment-specific details, allowing the same Score file to be used across different target platforms through reference implementations that translate it into platform-specific formats like docker-compose.yaml or Kubernetes manifests.

Developers should adopt Score if they want to write workload configuration once and deploy it consistently across multiple environments without rewriting for each platform. It suits teams working with Docker, Kubernetes, Helm, or other container orchestration tools who want to reduce the complexity developers face when defining runtime requirements. The specification is intentionally tightly scoped to workload-level properties rather than attempting to replace platform-specific tools entirely, making it a bridge between developer intent and platform capabilities rather than a comprehensive orchestration solution.

The project maintains a reference specification schema alongside two actively maintained reference implementations: score-compose for Docker Compose output and score-k8s for Kubernetes manifests. The repository structure centers on the specification itself as the primary artifact, with implementation guidance and documentation supporting adoption by teams building custom implementations for their own platforms.