Automatically create a folder badges/ and add the coverage.svg, test.svg et version.svg
Go to file
Dandaedre af5f84808e
ci: add Cargo supply-chain gates
2026-10-04 02:18:04 +02:00
badges Work on a progress bar 2025-03-20 12:41:21 -05:00
src ci: add Cargo supply-chain gates 2026-10-04 02:18:04 +02:00
.gitignore ci: add Cargo supply-chain gates 2026-10-04 02:18:04 +02:00
.run_status.toml Work on a progress bar 2025-03-20 12:41:21 -05:00
Cargo.lock ci: add Cargo supply-chain gates 2026-10-04 02:18:04 +02:00
Cargo.toml ci: add Cargo supply-chain gates 2026-10-04 02:18:04 +02:00
Jenkinsfile ci: add Cargo supply-chain gates 2026-10-04 02:18:04 +02:00
LICENSE Initial commit 2024-11-05 16:01:41 +01:00
README.md ci: add Cargo supply-chain gates 2026-10-04 02:18:04 +02:00
deny.toml ci: add Cargo supply-chain gates 2026-10-04 02:18:04 +02:00

README.md

rust_autobadges

code coverage version code coverage

Runs cargo-tarpaulin to generate coverage and automatically create a badges/ folder with the generated coverage.svg, test.svg and version.svg

Dependency security and policy

CI pins cargo-audit 0.22.2 and cargo-deny 0.20.2. Run the same supply-chain gates locally from the repository root:

cargo audit --deny warnings
cargo deny check

Both commands require network access so they can refresh RustSec advisory and crates.io registry data. A failed refresh is an error; CI does not silently accept stale data.

cargo audit checks the tracked Cargo.lock for RustSec vulnerabilities, unmaintained or unsound advisories, and yanked packages. It is limited to advisories present in RustSec and cannot detect undisclosed vulnerabilities or assess source-code behavior.

cargo deny enforces deny.toml: only the licenses used by the current dependency graph are allowed (with a confidence threshold of 0.8), wildcard requirements are denied, duplicate versions are reported as warnings, unknown registries and Git sources are denied, crates.io is the only allowed registry, and no Git sources are allowed. It builds the graph with all features enabled. Advisory ignores, crate bans, duplicate skips, license exceptions, and license clarifications start empty. The tool validates dependency metadata and known advisories; it is not a source-code or runtime scanner.

No other hardening tools are in scope for these CI gates.

Usage

Usage: rust_autobadges [OPTIONS]

Options:
  -s, --skip-clean
          Skip the cargo clean that tarpaulin would run, see tarpaulin --skip-clean for more documentation
  -t, --no-test
          Dont generate the test:failing/passing badge
  -c, --no-coverage
          Don't run the coverage and dont generate the coverage:(percent) badge
  -v, --no-version
          Don't run the version tag check and dont generage the version:(number) badge
      --version-color <VERSION_COLOR>
          The color used to use on the version badge [default: orange]
      --failing-color <FAILING_COLOR>
          The color used to indicate failure on the test badges [default: red]
      --success-color <SUCCESS_COLOR>
          The color used to indicate success on the badges [default: green]
      --high-coverage-color <HIGH_COVERAGE_COLOR>
          The color used on a high coverage [default: green]
      --mid-coverage-color <MID_COVERAGE_COLOR>
          The color used on a mid coverage [default: orange]
      --low-coverage-color <LOW_COVERAGE_COLOR>
          The color used on a low coverage [default: red]
      --high-coverage-percent <HIGH_COVERAGE_PERCENT>
          The percent indicating a high coverage [default: 1]
      --mid-coverage-percent <MID_COVERAGE_PERCENT>
          The percent indicating a mid coverage [default: 0.8]
  -o, --output <OUTPUT>
          The output directory where all the badges will be saved [default: badges]
  -h, --help
          Print help
  -V, --version
          Print version

Future Features

  • Only run tests
  • Clean the badges folder
  • Have a better indication of the actions of tarpaulin run
  • (optionnal) Save info of the previous run to allow a progress bar

TODO

  • Better error handling
  • Structs to allow centralisation of pb/error handling/.close()
  • Better alignment
  • (consideration) A config file to avoid passing so many arguments and have a better CI
  • Having a coverage above 0% ? (even if testing something that runs tests require some smart)