Commenter
GitHubAdmin Panel
v2
v2
  • 😍Commenter
  • Overview
    • 💡Why Commenter
    • 🗞️Articles
    • ✨Key Features
    • 🤖Technologies
  • Basics
    • 🧠Concept
    • ®️Requirements
    • 🔨Installation
    • ✈️Usage
    • 🌈Themes
  • Demo
    • 👩‍🏫Project
    • 📺Basic Demo Video
    • 📼Full Demo Video
  • Configuration
    • 📜Publish Config
    • Migrations/Tables
    • ⚖️Change Mode
    • 🔐Authorization
    • ⏲️Limit comments per user
    • 😍Reactions
    • ⛔Approval
    • 🚧Validations
    • Sorting
    • 🛠️Other Options
  • Advance
    • 🔏Security
    • 🚀Performance
    • ⚡Events
    • 🌍Localization
    • 🛟Customization
    • 🕵️Testing
  • 🛣️Roadmap
  • 💓Sponsor
Powered by GitBook
On this page
  • XSS Protection
  • Spam Protection

Was this helpful?

Edit on GitHub
  1. Advance

Security

Security is one of the major factors we considered when developing this package. We have taken several actions to strengthen its security, which are described on this page.

PreviousOther OptionsNextPerformance

Last updated 7 months ago

Was this helpful?

XSS Protection

The package uses the editor to provide rich features such as headers, code blocks, and lists. Although the editor itself filters vulnerable inputs, we haven't relied on it solely. We also filter inputs using the package. We believe these two layers of security provide solid protection against XSS attacks.

Spam Protection

Spam can cause significant damage to your commenting system by adding redundant, mutated comments, and it can also harm your site through attacks like DOS. We have used a package to prevent spam invasion, but we cannot stop DOS attacks. For that, we recommend adding some robot checks.

Though we have taken some steps to mitigate security attacks we can never be perfect in security. If you found any vulnerability please don't use issue tracker instead send email to

🔏
Quill
Graham-Campbell/Security
spatie/laravel-honeypot
epmadushanka@gmail.com