@@ -12,8 +12,7 @@ SPDX-License-Identifier: LicenseRef-PlainMIT OR MIT
 [![Documentation](https://docs.rs/submod/badge.svg)](https://docs.rs/submod)
 [![Static Badge](https://img.shields.io/badge/Plain-MIT-15db95?style=flat-square&labelColor=0d19a3&cacheSeconds=86400&link=https%3A%2F%2Fplainlicense.org%2Flicenses%2Fpermissive%2Fmit%2Fmit%2F)](https://plainlicense.org/licenses/permissive/mit/)
 [![Rust](https://img.shields.io/badge/rust-1.89%2B-blue.svg)](https://www.rust-lang.org)
-[![codecov](https://codecov.io/gh/bashandbone/submod/branch/main/graph/badge.svg?token=MOW92KKK0G)](https://codecov.io/gh/bashandbone/submod)
-![Crates.io Downloads (latest version)](https://img.shields.io/crates/dv/submod)
+[![codecov](https://codecov.io/gh/bashandbone/submod/graph/badge.svg?token=O9PDZZD741)](https://codecov.io/gh/bashandbone/submod)![Crates.io Downloads (latest version)](https://img.shields.io/crates/dv/submod)
 
 Git submodules solve a real problem. **Managing submodules is a pain.** You use them infrequently enough that you always forget which command does what — and when something breaks, the recovery steps are a small nightmare. New contributors hit this especially hard: onboarding onto a project that uses submodules is its own obstacle course.