Skip to content

ci: Add cargo-deny + cargo-audit + cargo-mutants nightly workflow #650

Closed

Description

@nanaf6203-bit

Restore the nightly cargo-mutants workflow (#547) and add cargo-deny and cargo-audit to the same workflow. Surface results in AUDIT_LOG.md.

Activity

  1. Israel-light commented on Jun 26, 2026

    @Israel-light

    @Israel-light has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

    I’m interested in this issue because it strengthens the repository’s supply-chain and code-quality guarantees by adding automated dependency auditing and mutation testing. Combining cargo-deny, cargo-audit, and cargo-mutants in a nightly workflow provides early detection of vulnerabilities, licensing issues, and weak test coverage.

    I’ve worked with Rust CI pipelines and GitHub Actions workflows, including integrating cargo-audit, dependency policy checks, and test coverage/mutation tooling. I’m comfortable setting up reproducible nightly jobs and ensuring outputs are properly surfaced for review.

    For this task, I would:

    restore the existing nightly cargo-mutants workflow,
    integrate cargo-deny and cargo-audit into the same CI job,
    ensure all outputs are captured and written to AUDIT_LOG.md,
    and structure the workflow so failures are clearly reported but non-blocking if required.

    I would also ensure the workflow runs efficiently and produces consistent, readable audit logs for maintainers.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Israel-light to this issue.

  2. anumukul commented on Jun 26, 2026

    @anumukul

    @anumukul has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

    Hi, I’d like to take this issue and can deliver a fix within 24 hours.
    I’ve worked on similar projects before and have relevant experience, so I should be able to handle this efficiently.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @anumukul to this issue.

  3. warisu commented on Jun 26, 2026

    @warisu
    Contributor

    @warisu has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

    Hello, I can handle this, my ETA is 12hrs

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @warisu to this issue.

  4. drips-wave commented on Jun 26, 2026

    @drips-wave

    Congratulations, @warisu! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

    🧑‍💻 @warisu: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  5. drips-wave commented on Jun 26, 2026

    @drips-wave

    This issue has been completed by @warisu as part of the Stellar Wave Program's 6th Wave 🥳

    😎 @warisu: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions