# Should Privacy Guides require open-source, source-first or source-available as a criteria for all tools?

**URL:** https://discuss.privacyguides.net/t/should-privacy-guides-require-open-source-source-first-or-source-available-as-a-criteria-for-all-tools/22684
**Category:** Site Development
**Created:** 2024-11-24T09:28:13Z
**Posts:** 97
**Showing post:** 13 of 97

## Post 13 by @jonah — 2024-11-24T10:09:59Z

Because option 3 means we would have to make it a criteria if it’s possible to do so, even if there is a reason it shouldn’t be a criteria.

For example, I think there is a reason to not do [Require Open Source for Password Managers - #139 by jonah](https://discuss.privacyguides.net/t/require-open-source-for-password-managers/12480/139) despite it being possible for the category, but both option 3 and option 2 would imply that we need to add the [Require Open Source for Password Managers](https://discuss.privacyguides.net/t/require-open-source-for-password-managers/12480/) criteria, which I disagree with.

---

_[View the full topic](https://discuss.privacyguides.net/t/should-privacy-guides-require-open-source-source-first-or-source-available-as-a-criteria-for-all-tools/22684)._