Skip to content
Credimi Docs

Scoreboard Feature

Scoreboard Feature

Section titled “Scoreboard Feature”

Overview

Section titled “Overview”

The Scoreboard shows aggregated pipeline execution results across the platform. The public UI reads pre-aggregated rows from the PocketBase pipeline_scoreboard_cache collection. A Temporal workflow periodically refreshes that cache from per-namespace pipeline statistics.

API Endpoints

Section titled “API Endpoints”

GET /api/pipeline/scoreboard/{namespace}

Section titled “GET /api/pipeline/scoreboard/{namespace}”

Returns aggregated pipeline statistics for a single Temporal namespace (organization).

Authentication: Internal / trusted callers (used by the aggregation workflow)

POST /api/pipeline/scoreboard/save-results

Section titled “POST /api/pipeline/scoreboard/save-results”

Accepts merged aggregation output and refreshes pipeline_scoreboard_cache.

Authentication: Internal admin API key

POST /api/pipeline/scoreboard/aggregate/start

Section titled “POST /api/pipeline/scoreboard/aggregate/start”

Starts the AggregateScoreboardWorkflow. Optional ?schedule=<seconds> creates a recurring schedule.

DELETE /api/pipeline/scoreboard/aggregate/schedule/{schedule_id}

Section titled “DELETE /api/pipeline/scoreboard/aggregate/schedule/{schedule_id}”

Cancels a scheduled aggregation workflow.

Legacy (removed from active routes)

Section titled “Legacy (removed from active routes)”

The older /api/my/results and /api/all-results endpoints described an OpenTelemetry tabbed scoreboard. That implementation is commented out in scoreboard_handler.go and is no longer used by the frontend.

Data Model

Section titled “Data Model”

pipeline_scoreboard_cache

Section titled “pipeline_scoreboard_cache”

Primary read model for the scoreboard UI. One row per pipeline, with fields such as:

  • total_runs, total_successes, success_rate
  • pipeline relation (may be hidden when the pipeline is private)
  • Expanded relations for wallets, issuers, verifiers, credentials, runners, conformance checks, and latest successful execution artifacts

Frontend type

Section titled “Frontend type”
webapp/src/lib/scoreboard/types.ts
export type ScoreboardRow = PipelineScoreboardCacheResponse<...>;

Frontend

Section titled “Frontend”

Public Scoreboard (/scoreboard)

Section titled “Public Scoreboard (/scoreboard)”
  • Loads rows via Scoreboard.loadData() ($lib/scoreboard/functions.ts)
  • Renders Scoreboard.Component with a Scoreboard.Instance table controller
  • Columns include pipeline name, screenshot, success rate, wallets, issuers, credentials, verifiers, use-case verifications, conformance checks, custom integrations, runners, and minimum running time
  • Supports client-side pagination and sorting

Homepage Section

Section titled “Homepage Section”

webapp/src/routes/(public)/_partials/scoreboard-section.svelte shows a small random sample of scoreboard rows on the public landing page.

Library exports

Section titled “Library exports”
import { Scoreboard } from '$lib';


Scoreboard.loadData();
Scoreboard.Component;
Scoreboard.Instance;
Scoreboard.EntityDisplay;

Aggregation Workflow

Section titled “Aggregation Workflow”

AggregateScoreboardWorkflow (pkg/workflowengine/workflows/scoreboard.go):

  1. Enumerate organization namespaces
  2. Fetch per-namespace stats from /api/pipeline/scoreboard/{namespace}
  3. Merge results across tenants
  4. Persist via /api/pipeline/scoreboard/save-results

Handlers live in pkg/internal/apis/handlers/scoreboard.go.

Usage Examples

Section titled “Usage Examples”

Load scoreboard data in a SvelteKit route

Section titled “Load scoreboard data in a SvelteKit route”
import { Scoreboard } from '$lib';


export const load = async ({ fetch }) => {
  const data = await Scoreboard.loadData({ fetch });
  return { scoreboardData: data.items };
};

Start aggregation manually

Section titled “Start aggregation manually”
Terminal window
curl -X POST "https://your-domain/api/pipeline/scoreboard/aggregate/start" \
  -H "X-Api-Key: $CREDIMI_INTERNAL_ADMIN_KEY"

Future Enhancements

Section titled “Future Enhancements”
  • Filtering and column presets on the public table
  • Historical trending from pipeline_results
  • Per-organization public views
  • Scheduled aggregation monitoring in the admin UI