# Sourcemap sensitive files leaked

**URL:** https://meta.discourse.org/t/sourcemap-sensitive-files-leaked/259900
**Category:** Support
**Created:** [March 29, 2023, 7:23pm UTC](https://meta.discourse.org/t/sourcemap-sensitive-files-leaked/259900 "2023-03-29T19:23:58Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [March 29, 2023, 7:40pm UTC](https://meta.discourse.org/t/sourcemap-sensitive-files-leaked/259900/2 "2023-03-29T19:40:08Z")

</div>

> [@Rob\_Tsai](#):
>
> Impact： The danger is that the attacker obtains the source code and sensitive information , and non-public api

I think the answer is that there is no non-public API. It’s documented at [GitHub - discourse/discourse: A platform for community discussion. Free, open, simple. · GitHub](https://github.com/discourse/discourse) and if you don’t know how to read that, you can always [Reverse engineer the Discourse API](https://meta.discourse.org/t/reverse-engineer-the-discourse-api/20576).

I really hate bogus security spam.

---

_[View the full topic](https://meta.discourse.org/t/sourcemap-sensitive-files-leaked/259900)._