Skip to main content
All CollectionsProduct release notes
Product Updates // July 2023
Product Updates // July 2023
Gabriele Gallo Stampino avatar
Written by Gabriele Gallo Stampino
Updated over a year ago

Introducing Fix-Bot: automated fixes made easy

“Hey Clayton, how about fixing some code for me?”

With our latest innovation (we call it Fix-Bot), Clayton can now open pull requests with proposed fixes to resolve common errors and styling inconsistencies.

Watch your code transform into clean, optimised, and error-free perfection with a simple click.

Managed updates

Get new rules and policy updates automatically, and stay on top of the latest best practices.

Clayton helps you keep your developments consistent. Our managed updates will keep your standards up-to-date!

Illuminate your experience with Dark Mode

Immerse yourself in a captivating experience that is easy on the eyes and enhances your productivity, focus, and overall enjoyment.

With this release, we have also added the ability to choose your user avatar, making your experience with Clayton more engaging and unique.

Custom Webhook Payloads

Configure your own payloads on webhooks and integrate more easily with your other DevOps tools, such as Copado and many more.

New Security Rules

Here are some juicy additions to our rule catalogue.

  • HTTP Referer Headers detection: HTTP Referer headers can be modified by attackers. Making a decision based on the value of the referer can be dangerous.

  • Inline CSS Styles detection: When using CSS style tags and attributes, the HTML parser switches to CDATA or raw text context, which is prone to code injection. For this reason, using inline CSS is considered unsafe and should be avoided.

  • Autocompletion on password fields: Detect any password fields with autocompletion enabled. The user browser can save and remember the entered values for user input fields with autocomplete-enabled attributes. This might reveal sensitive information like passwords, especially on public and multi-user computers.

  • No insecure cookies: Make sure to allow only allow access to your application cookies through HTTPS. The isSecure attribute controls whether a cookie can only be accessed through HTTPS or not. By setting this attribute to false, sensitive cookies may be exposed if sent over an insecure connection.

Did this answer your question?