score-spec/score-go

Reference library for parsing and loading Score files

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

score-spec/score-go has 30+ stars and 10+ forks on GitHub, is written in Go, and was last pushed on Oct 13, 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 16th, 2022
Open Issues & Pull Requests: 7 (+0)
GitHub issues: Enabled
Number of forks: 14
Total Stargazers: 34 (+0)
Total Subscribers: 2 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.1 hours
Mean response time: 36.7 hours
90th percentile: 2.9 days
Tracked items: 12

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

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 (6)
  • bug (5)
  • good first issue (4)
  • help wanted (4)
  • go (3)
  • wontfix (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

score-go is a reference library for parsing and loading Score files in Go.

Score is a specification for defining workloads, services, and resources in a portable way. This library solves the problem of implementing Score support by providing pre-built Go types, validation logic, and loading functions that handle the complexity of parsing and interpreting Score files. Rather than each implementation writing its own types and validation, developers can use the generated types derived from the official JSON schema, a schema validation package, and utility functions for loading validated structures into workload objects.

Teams building Score implementations in Go should use this library as their foundation. It is particularly suited for projects that need to read and interpret Score files without reimplementing schema validation or type definitions. The library includes packages for schema validation, auto-generated types, file loading, and framework utilities. Projects still using hand-written types from earlier versions can remain on the older release branch, though newer schema fixes will only be applied to the current version. The reference implementation score-compose demonstrates how to build a complete Score implementation using this library.

The project maintains close alignment with the official Score specification by regenerating its types whenever the JSON schema is updated in the specification repository. Test coverage is verified after schema updates to ensure compatibility. The library is structured as a set of focused packages that separate concerns between schema validation, type definitions, file loading, and framework abstractions, allowing implementations to use only the components they need.