Skip to main content
When creating a leaderboard, optionally restrict it to specific dataset-version UUIDs in the create config:
IDs and refs may be combined; the API resolves refs and stores their UUIDs. Omitting both fields associates every version that exists when the leaderboard is created. Setting both to empty lists associates none. Versions published later are never added automatically. Use harbor hub leaderboard show BOARD to display a curated leaderboard, or add --json to print the complete read API response. BOARD may be a UUID or an org/package/name slug. Export an update-ready YAML or JSON definition, edit it, and apply it:
Simple definition fields can be updated directly; these flags override values from --config when both are provided:
Rows have the same round-trip workflow. Use --all to export every row:
row list shows canonical ranks, configured leaderboard columns, status, trial count, timestamps, and row IDs. It supports --limit, --page, --json, and --quiet using the same paging behavior as hub job list. The create config contains a rows list. Each row accepts metadata, metrics, status, and optional trial_ids. You can also create a leaderboard and its initial rows atomically with harbor hub leaderboard create --rows new-rows.yaml. Definition and batch row changes commit atomically. A schema change is rejected when any resulting row is invalid. Delete incompatible rows explicitly with harbor hub leaderboard row delete, or update them in the same command with --rows. Use --dry-run with the combined --config and --rows migration form to validate it without committing. The API mirrors these resource boundaries: leaderboard-update changes only the definition; row create, read, update, delete, and trial changes use their dedicated endpoints. Only leaderboard-migrate accepts definition and row changes together. Manage row provenance separately:
Leaderboard reads and mutation responses return n_trials rather than every association. row trial list pages through the associations; use --json for one page or --quiet to stream every trial ID. set can also read the complete replacement list from YAML or JSON:
set replaces every association; use set --clear to remove them all. Trial changes do not recompute row metadata or metrics.