# Audit testing the code

**URL:** <https://meta.discourse.org/t/audit-testing-the-code/228780>\
**Category:** Development\
**Created:** [June 1, 2022, 7:08pm UTC](https://meta.discourse.org/t/audit-testing-the-code/228780 "2022-06-01T19:08:11Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![matt\_c](https://avatars.discourse-cdn.com/v4/letter/m/c0e974/32.png) [@matt\_c](https://meta.discourse.org/u/matt_c)\
**Post date:** [June 1, 2022, 7:41pm UTC](https://meta.discourse.org/t/audit-testing-the-code/228780/3 "2022-06-01T19:41:29Z")

</div>

Thank you for the fast response.

> [@pfaffman](#):
>
> The Discourse team takes security very seriously and, in addition to their team of full-time developers, has HackerOne actively looking for security issues: [HackerOne](https://hackerone.com/discourse?type=team). See also [How secure is Discourse?](https://meta.discourse.org/t/how-secure-is-discourse/78156)

I have seen that. Even if I fully trust the security of discourse, I had to run audit for company policy to ease the integration process. Everything else seems perfect, so that’s why I was wondering if they include audit testing functionalities.

---

_[View the full topic](https://meta.discourse.org/t/audit-testing-the-code/228780)._