Progress badges and reporting

Publish a progress report

Link decomphub.progress.json from your README. Every track needs a stable ID, precise scope and measurement. Use null for unknown progress. Keep code matching, shader decoding and compatibility separate.

JSON schema · Read the progress guide

Example structure: replace the repository and scope. No percentage is assumed.

{
  "format": "decomphub.progress/v1",
  "repository": "https://github.com/boykopovar/anyps5",
  "tracks": [
    {
      "id": "matching-code",
      "label": "Matching code",
      "scope": "Target version and measurement boundary",
      "measurement": null
    }
  ]
}

Add this report link to your README

[Progress data](decomphub.progress.json)

Each measurement keeps its source and scope. Dates are optional: without a publisher date, we show when we read the source. Different tracks are never averaged.

Update after a merge

Generate and publish the report in your existing CI after changes reach the default branch. Then add this notification step. The existing worker checks the source, at most once per hour per project and within provider limits. A notification never supplies a percentage. Periodic collection continues.

- name: Notify DecompHub
  env:
    PROJECT_REPOSITORY: https://github.com/${{ github.repository }}
    PROJECT_REVISION: ${{ github.sha }}
  run: |
    jq -n --arg repository "$PROJECT_REPOSITORY" --arg revision "$PROJECT_REVISION" \
      '{repository: $repository, revision: $revision}' |
      curl --fail --silent --show-error --max-time 20 \
        -H "Content-Type: application/json" --data-binary @- \
        https://app.decomphub.com/api/progress/refresh