# score-spec/spec

The Score Specification provides a developer-centric and platform-agnostic Workload specification to improve developer productivity and experience. It eliminates configuration inconsistencies between environments.

Repository: https://github.com/score-spec/spec
Canonical: https://ross.abutalabs.com/products/spec
Homepage: https://score.dev/
Language: Makefile
License: Apache-2.0
License Family: permissive
Last push: 2026-07-27T01:43:12+00:00

## Health v2 (maintenance only)
Score: 88/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 94, release rhythm 73, longevity 100
- inputs: {"age_days": 1402, "days_push": 38, "days_rel": 100, "gap_med": 71.0, "n_releases_24m": 5}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 8088, forks 2139 (observed 2026-08-28T04:10:12.618078+00:00)

## What it is
Score is an open-source, platform-agnostic workload specification (a YAML schema, score.yaml) for describing container-based workloads and their resource dependencies in a vendor-neutral way. It is a CNCF Sandbox project that lets developers define a workload once and translate it to platforms like Docker Compose, Kubernetes, Helm, Fly.io, or Google Cloud Run via Score implementations.

## Use cases
- define workload configuration once and deploy to both docker compose and kubernetes
- eliminate config drift between local and production environments
- avoid writing kubernetes yaml for simple app deployments
- declare resource dependencies like postgres databases in a vendor-neutral way
- reduce yaml bloat from environment-specific config files
- transition workloads from local development to cloud run or fly.io

## When to choose
- you deploy the same workload to multiple platforms and want a single source of truth
- you want to separate developer-owned workload config from platform-owned infrastructure config
- your team struggles with inconsistent configuration across local and remote environments

## When to avoid
- you need fine-grained, platform-specific Kubernetes features beyond workload-level properties
- you deploy to only one platform and already have stable config there
- you need a fully featured replacement for all platform YAML constructs

## Facets
- artifact type: library
- maturity: active
- function: configuration-management, developer-tools, deployment, microservices
- domain: developer-tools, cloud-computing
- platform: cloud, cross-platform
- tags: workload-specification, platform-agnostic, cncf-sandbox, yaml-spec, cloud-native, portable-configuration, devops, containers, automation, docker, kubernetes

## Member repositories
- score-spec/spec (main) score 88

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:10:12.618078+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-30T08:09:43.264636+00:00, confidence not recorded.
  - readme: https://github.com/score-spec/spec (fetched 2026-08-28T04:10:12.618078+00:00, sha 7bd3c6e7d6da)
  - homepage: https://score.dev/ (fetched 2026-08-29T08:28:50.681285+00:00, sha 8a1749d9d21d)
  - site_page: https://docs.score.dev/docs (fetched 2026-08-29T08:28:50.691119+00:00, sha a339a74d6f6d)
- Data as of 2026-08-30T08:39:29.467469+00:00.