| name file | size | edit | permission | action |
|---|---|---|---|---|
| .env | 2733 KB | December 22 2024 06:20:07 | 0644 | |
| 404.html | 58370 KB | November 20 2024 15:32:22 | 0644 | |
| 502.html | 58368 KB | November 20 2024 15:32:22 | 0644 | |
| Modules | - | December 11 2024 21:02:56 | 0755 | |
| README.md | 4158 KB | February 14 2023 12:31:56 | 0644 | |
| app | - | December 11 2024 17:57:48 | 0755 | |
| artisan | 1686 KB | February 14 2023 12:31:56 | 0644 | |
| bootstrap | - | December 11 2024 20:23:36 | 0755 | |
| composer.json | 3761 KB | December 11 2024 22:15:00 | 0644 | |
| composer.lock | 512048 KB | December 11 2024 22:13:28 | 0644 | |
| config | - | June 15 2025 02:09:36 | 0755 | |
| database | - | December 05 2024 20:18:12 | 0755 | |
| dfsdf dfds fd fds findex.html | 1420 KB | November 20 2024 15:32:24 | 0644 | |
| error_log | 16989113 KB | July 18 2025 18:35:26 | 0644 | |
| firoz | - | December 23 2024 13:24:46 | 0755 | |
| index.php | 1667 KB | December 14 2024 05:20:36 | 0644 | |
| lang | - | December 11 2024 21:02:48 | 0755 | |
| modules_statuses.json | 472 KB | November 20 2024 15:32:24 | 0644 | |
| mpos | - | March 31 2025 02:36:31 | 0755 | |
| package.json | 226 KB | February 14 2023 12:31:56 | 0644 | |
| phpunit.xml | 1146 KB | February 14 2023 12:31:56 | 0644 | |
| public | - | March 31 2025 02:36:31 | 0755 | |
| resources | - | December 11 2024 21:10:22 | 0755 | |
| routes | - | June 15 2025 02:09:31 | 0755 | |
| storage | - | December 11 2024 21:12:44 | 0755 | |
| tests | - | December 05 2024 20:18:12 | 0755 | |
| vendor | - | December 11 2024 22:13:30 | 0755 | |
| vite.config.js | 263 KB | February 14 2023 12:31:56 | 0644 |
Hello Parsedown!
``` More examples in [the wiki](https://github.com/erusev/parsedown/wiki/) and in [this video tutorial](http://youtu.be/wYZBY8DEikI). ### Security Parsedown is capable of escaping user-input within the HTML that it generates. Additionally Parsedown will apply sanitisation to additional scripting vectors (such as scripting link destinations) that are introduced by the markdown syntax itself. To tell Parsedown that it is processing untrusted user-input, use the following: ```php $parsedown = new Parsedown; $parsedown->setSafeMode(true); ``` If instead, you wish to allow HTML within untrusted user-input, but still want output to be free from XSS it is recommended that you make use of a HTML sanitiser that allows HTML tags to be whitelisted, like [HTML Purifier](http://htmlpurifier.org/). In both cases you should strongly consider employing defence-in-depth measures, like [deploying a Content-Security-Policy](https://scotthelme.co.uk/content-security-policy-an-introduction/) (a browser security feature) so that your page is likely to be safe even if an attacker finds a vulnerability in one of the first lines of defence above. #### Security of Parsedown Extensions Safe mode does not necessarily yield safe results when using extensions to Parsedown. Extensions should be evaluated on their own to determine their specific safety against XSS. ### Escaping HTML > ⚠️ **WARNING:** This method isn't safe from XSS! If you wish to escape HTML **in trusted input**, you can use the following: ```php $parsedown = new Parsedown; $parsedown->setMarkupEscaped(true); ``` Beware that this still allows users to insert unsafe scripting vectors, such as links like `[xss](javascript:alert%281%29)`. ### Questions **How does Parsedown work?** It tries to read Markdown like a human. First, it looks at the lines. It’s interested in how the lines start. This helps it recognise blocks. It knows, for example, that if a line starts with a `-` then perhaps it belongs to a list. Once it recognises the blocks, it continues to the content. As it reads, it watches out for special characters. This helps it recognise inline elements (or inlines). We call this approach "line based". We believe that Parsedown is the first Markdown parser to use it. Since the release of Parsedown, other developers have used the same approach to develop other Markdown parsers in PHP and in other languages. **Is it compliant with CommonMark?** It passes most of the CommonMark tests. Most of the tests that don't pass deal with cases that are quite uncommon. Still, as CommonMark matures, compliance should improve. **Who uses it?** [Laravel Framework](https://laravel.com/), [Bolt CMS](http://bolt.cm/), [Grav CMS](http://getgrav.org/), [Herbie CMS](http://www.getherbie.org/), [Kirby CMS](http://getkirby.com/), [October CMS](http://octobercms.com/), [Pico CMS](http://picocms.org), [Statamic CMS](http://www.statamic.com/), [phpDocumentor](http://www.phpdoc.org/), [RaspberryPi.org](http://www.raspberrypi.org/), [Symfony demo](https://github.com/symfony/symfony-demo) and [more](https://packagist.org/packages/erusev/parsedown/dependents). **How can I help?** Use it, star it, share it and if you feel generous, [donate](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=528P3NZQMP8N2).