Ross ROSS = Recommend OSS · open-source software intelligence for agents

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. observed · 2026-08-28

github.com/score-spec/spec · homepage · Makefile · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

88/100

  • Activity 94
  • Release rhythm 73
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 71.0
  • age_days: 1402
  • days_rel: 100
  • days_push: 38
  • n_releases_24m: 5

Full methodology

Adoption not part of the score

8088 stars · 2139 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

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

library · maturity active

configuration-management developer-tools deployment microservices developer-tools cloud-computing cloud cross-platform workload-specification platform-agnostic cncf-sandbox yaml-spec cloud-native portable-configuration devops containers automation docker kubernetes

3 sources

Member repositories

RepositoryRoleHealth v2
score-spec/specmain88

For agents

markdown · JSON · MCP: product_card(name="score-spec/spec")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem