🤔 Why the AGPL License?¶
Siyarix is a cybersecurity tool, meaning its code can be used for defense or harm. I chose the AGPL-3.0-or-later license deliberately as a structural safeguard for this project.
🛡️ Security Demands Openness¶
Security tools occupy a unique space. A bug in a vulnerability scanner can cause real problems.
The AGPL ensures that: - Every fix stays open: If someone finds and patches a bug in their fork, they are obligated to share that fix. - No hidden flaws: Proprietary forks hide their internals, making audits impossible. AGPL guarantees the source code is always exposed.
⚖️ Ethical Accountability¶
AGPL helps enforce accountability. If a modified version of Siyarix is utilized as a backend service, the code must be available for review. This prevents opaque security services from profiting off community work while hiding their methods.
Note
The one exception to this is the Plugin Exception. Third-party plugins can use any license, allowing developers to build specific workflows while the core engine remains open.
🤝 Community Trust¶
Open-source security requires trust. You need to trust that the code does what it claims.
The AGPL keeps Siyarix open.
The project's code remains the community's work. As an operator, you deserve to know: - The code you audit today is exactly the code that runs tomorrow. - There is no secret "Enterprise Edition" hoarding features.
💡 The Bottom Line¶
I chose the AGPL because a cybersecurity tool without strong copyleft protection risks being closed and turned against the community that built it.
Keep Siyarix open. Keep Siyarix safe.