coverage.sh includes vendored code in coverage metrics

[DeFiVC]

What

The coverage.sh script excludes tests/* and scripts/* from coverage calculations but does NOT exclude vendor/*. The vendored ed25519-dalek crate is included in coverage metrics.

Why

Coverage percentages are inflated by vendored third-party code that the project doesn't own or maintain. The 80% threshold (--fail-under 80) may pass when it shouldn't because vendor code contributes easy-to-cover paths.

Scope

• Add --exclude-files "vendor/*" to the cargo-tarpaulin command in coverage.sh

Acceptance Criteria

• The coverage report excludes vendored code
• The coverage percentage reflects only project-owned code

Technical Context

• scripts/coverage.sh:12-18 — tarpaulin command missing vendor exclusion

[BobbyRichie2]

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

Hello, I’d like to contribute to this issue and would appreciate the opportunity to work on it. Thank you.

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

[canicefavour]

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

I can update scripts/coverage.sh to exclude vendor/* from the cargo-tarpaulin coverage calculation alongside the existing test/script exclusions, ensuring the 80% threshold reflects only project-owned Rust code. I’ll verify the generated report omits vendored ed25519-dalek paths and confirm the coverage command still completes successfully.

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

[Christian01-del]

@Christian01-del has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello Maintainer,

I’ve carefully reviewed the issue and have a clear understanding of the requirements. I’m genuinely interested in contributing to this and confident that I can work toward a reliable solution that meets the expected criteria.

I’d really appreciate the opportunity to take on this issue and contribute to the project. If possible, I’d be grateful if you could assign it to me.

Thank you for your time and consideration. I look forward to contributing.

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

[Philcsweb3]

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

Hello, I understand the issue and the behavior expected from the fix. I’m interested in working on it and can get started right away.

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

[nwosum113-ui]

@nwosum113-ui has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

hello maintainer, i would love to work on this issue

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

[TheHalalHunter]

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

Hi maintainer
I’d love to help out with this issue. I’ve checked the current codebase/documentation and know exactly what needs to be updated to make this clearer. I will ensure everything aligns perfectly with your existing contribution guidelines.

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

[drips-wave]

Congratulations, @nwosum113-ui! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @nwosum113-ui: 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 🌊

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@nwosum113-ui's PR #508 was approved and merged by @DeFiVC.

🏆 @nwosum113-ui: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (436 total points). Track your full progress on GrantFox.

👏 Great work, @nwosum113-ui! Keep contributing to ChainLearnOfficial.