[Wolfi Package Update]: gocover-cobertura

Open
#78,706 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
66/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
devops

Research direction

Start with the upstream gocover-cobertura project at https://github.com/boumenot/gocover-cobertura and locate the Wolfi package metadata and nearby Go package definitions that follow the repository’s packaging conventions. Confirm the package builds at version 1.5.0 and that the resulting package can be installed through Wolfi’s usual package manager.

Written by the indexing model from the issue text.

Description

needs-triage
Package name

gocover-cobertura

Current version in Wolfi

n/a

Requested version

1.5.0 (latest)

Upstream project URL

https://github.com/boumenot/gocover-cobertura

Problem

Gocover-cobertura is widely used in CI/CD pipelines, where it enables Go coverage reports to be ingested by other tools for reporting purposes (e.g. GitLab, SonarQube)

Being able to install it into CI/CD worker images via the usual package manager would be more secure than using go install.

Steps to reproduce

No response

Root cause (if known)

No response

Proposed solution

No response

Testing performed

No response

Acceptance criteria
  • The requested version is the latest stable upstream release (no pre-releases or RCs)
  • The upstream project uses an OSI-approved license
  • The change aligns with Wolfi’s packaging and security model
  • The package can be reasonably maintained over time
  • There are no known unresolved security or supply-chain concerns
Dominant language
Shell
Stars
1.3k
Forks
443
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wolfi-dev/os

All issues in wolfi-dev/os

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.