[Chore] SECURITY.md doesn't mention asserter-consumer's scope

[collinsezedike]

Summary

SECURITY.md's Scope section (lines 27-32) says: "In scope: the contracts under contracts/ in this repository. Out of scope: third-party dependencies (soroban-sdk, the Stellar network itself), and the contracts/demo-consumer example, which exists to validate integration patterns and is not intended for production use on its own."

contracts/asserter-consumer isn't named anywhere in that section. As written, the blanket "In scope: the contracts under contracts/" technically covers it, but a reader skimming the doc for what's excluded has no way to tell whether asserter-consumer was deliberately included or just forgotten, especially since it sits right next to demo-consumer, which the doc does call out by name.

Scope

• Update SECURITY.md's Scope section to explicitly state whether contracts/asserter-consumer is in scope alongside contracts/tholos and contracts/tholos-v2, or call out any reason it isn't.

Proposed approach

Add contracts/asserter-consumer to the in-scope list explicitly, for example:

In scope: the contracts under `contracts/` in this repository, including
`contracts/tholos`, `contracts/tholos-v2`, and `contracts/asserter-consumer`.
Out of scope: third-party dependencies (`soroban-sdk`, the Stellar network
itself), and the `contracts/demo-consumer` example, which exists to validate
integration patterns and is not intended for production use on its own.

[Iker2522]

I would like to work on this issue because clearly defining the security scope helps contributors understand which contracts are covered and avoids ambiguity when reporting potential vulnerabilities. I can update the Scope section to explicitly include "contracts/asserter-consumer", keeping the documentation change focused and consistent with the existing wording.

[ZacLou]

I'd like to work on this. I'll update SECURITY.md to explicitly mention contracts/asserter-consumer in the Scope section and open a PR shortly.

[grantfox-oss]

🦊 GrantFox — @Iker2522 has been assigned to this issue!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #122)
2. Your PR will be reviewed by the drydocs maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@Iker2522's PR #136 was approved and merged by @collinsezedike.

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

👏 Great work, @Iker2522! Keep contributing to drydocs.