Bring all monitored repositories to 100% in CLOMonitor
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 50/100
Research direction
Start with the linked CLOMonitor report and the named repositories, comparing each repository's release status and compliance checks. Inspect .github/workflows/build-verify.yml in microcks-docker-desktop-extension and the .clomonitor.yml files for the two source-only GitHub Actions. Done means every monitored repository reports 100% after the next CLOMonitor refresh.
Written by the indexing model from the issue text.
Description
The CLOMonitor audit conducted on 2026-09-18 reports an overall Microcks score of 98.49% (A). Fourteen of the twenty monitored repositories are already at 100%.
The remaining work is:
-
hub.microcks.io: publish a recent release. -
microcks-backstage-provider: publish a recent release. -
microcks-jenkins-plugin: publish a recent release. -
import-github-action: publish a recent release and address the SBOM and signed-release checks. -
test-github-action: publish a recent release and address the SBOM and signed-release checks. -
microcks-docker-desktop-extension:- Publish a recent release.
- Provide or document an SBOM.
- Sign the release artifacts or provide provenance.
- Define restrictive
GITHUB_TOKENpermissions in.github/workflows/build-verify.yml.
For the two source-only GitHub Actions, maintainers should decide whether to produce signed release artifacts and SBOMs or declare documented exemptions in each repository's .clomonitor.yml when those checks are not applicable.
References:
Completion criteria: every monitored repository reports 100% after the next CLOMonitor refresh.
- Dominant language
- No language data
- Stars
- 8
- Forks
- 41
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 7
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microcks/.github
-
github_actions
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in microcks/.github
Similar issues
-
kind/bug needs-triage
Difficulty 1/5 Under an hour Newbie friendliness 72/100
matrixorigin/matrixone#29223 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
bug ci-failure high priority
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
vllm-project/vllm-omni#7972 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
amponce/archive-movie-browser#166 ·