You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
SECURITY.md audit scope line counts are significantly understated #487
SECURITY.md lines 181-187 list the audit scope with line counts that are roughly half the actual values:
Contract
Listed
Actual (lib.rs alone)
learn-token
~1400
2700+
credential-nft
~750
1500+
progress-tracker
~1500
2800+
Total
~3710
6500+
Why
Security auditors and contributors rely on these numbers to estimate review effort. Understating the code size by nearly 2x could lead to insufficient review coverage.
Scope
Update the line counts in SECURITY.md to reflect the current codebase. Include all source files (lib.rs, storage.rs, events.rs, types.rs, metadata.rs, etc.) not just the main lib.rs.
@Johnsource-hub has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hi! I’d like to work on this issue if it’s still available.
I have experience building web applicationsand I’m comfortable working with Git and collaborative development workflows. I’m confident I can implement a clean, maintainable solution while following the project’s contribution guidelines.
@Hibhee01 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hello Maintainer, I reviewed the issue carefully and the requirements are clear to me. I’m ready to take ownership of the task and work toward a clean implementation that satisfies the acceptance criteria.
@drmfsltdoh has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
I would like to work on correcting the http://SECURITY.md audit scope line counts — experienced in auditing documentation accuracy, repository analysis, and maintaining security docs to reflect actual codebase metrics.
@Gabriel-123-diamond has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
I would like to correct the audit-scope inventory. I will enumerate every source file under each listed contract, including storage, events, types, metadata, and other modules, and recalculate per-contract and aggregate line counts from the current checkout. I will document a consistent counting method and the revision used so auditors can reproduce the totals, distinguish production and test code where applicable, and update only the relevant SECURITY.md scope section. I will verify that all source files are represented and the totals meet the stated accuracy requirement.
Congratulations, @Joeloo1! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Joeloo1: 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.
😎 @Joeloo1: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.
Activity
Johnsource-hub commentedon Sep 30, 2026
@Johnsource-hub has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Johnsource-hub to this issue.
Maxl500 commentedon Sep 30, 2026
@Maxl500 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Maxl500 to this issue.
Hibhee01 commentedon Sep 30, 2026
@Hibhee01 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Hibhee01 to this issue.
dhikbass commentedon Sep 30, 2026
@dhikbass has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @dhikbass to this issue.
Oprimecloud commentedon Sep 30, 2026
@Oprimecloud has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oprimecloud to this issue.
solaawojobi00-bit commentedon Sep 30, 2026
@solaawojobi00-bit has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @solaawojobi00-bit to this issue.
umarhussainiagaie-bot commentedon Sep 30, 2026
@umarhussainiagaie-bot has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @umarhussainiagaie-bot to this issue.
drmfsltdoh commentedon Sep 30, 2026
@drmfsltdoh has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @drmfsltdoh to this issue.
shobhamerabacha-star commentedon Oct 7, 2026
Greetings,
I would like to work on this issue.
Solution overview:
Ready to implement immediately upon assignment. Please feel free to assign!
Gabriel-123-diamond commentedon Oct 19, 2026
@Gabriel-123-diamond has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Gabriel-123-diamond to this issue.
Joeloo1 commentedon Oct 19, 2026
@Joeloo1 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Joeloo1 to this issue.
drips-wave commentedon Oct 19, 2026
Congratulations, @Joeloo1! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.
🧑💻 @Joeloo1: 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 🌊
fix: audit scope counts, redeploy guide, and pause guards (#487, #488, …
grantfox-oss commentedon Oct 19, 2026
🎉 This issue has been marked as completed on GrantFox!
@Joeloo1's PR #658 was approved and merged by @DeFiVC.
🏆 @Joeloo1: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,988 total points). Track your full progress on GrantFox.
👏 Great work, @Joeloo1! Keep contributing to ChainLearnOfficial.
drips-wave commentedon Oct 19, 2026
This issue has been completed by @Joeloo1 as part of the Stellar Wave Program's 10th Wave 🥳
😎 @Joeloo1: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, 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.