<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/vendor/feed/atom.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-GB">
                        <id>https://phptoptens.com/authors/stephen-rees-carter/feed</id>
                                <link href="https://phptoptens.com/authors/stephen-rees-carter/feed" rel="self"></link>
                                <title><![CDATA[Artisan Weekly — Author Feed]]></title>
                    
                                <subtitle>Featured links for a given author across Artisan Weekly editions.</subtitle>
                                                    <updated>2026-09-10T14:38:18+01:00</updated>
                        <entry>
            <title><![CDATA[Security Tip: The Trap That Caught Me!]]></title>
            <link rel="alternate" href="https://securinglaravel.com/security-tip-the-trap-that-caught-me/" />
            <id>https://securinglaravel.com/security-tip-the-trap-that-caught-me/</id>
            <author>
                <name><![CDATA[Stephen Rees-Carter]]></name>
                <email><![CDATA[hello@example.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[A security tip exploring how to detect and block suspicious bot activity in Laravel applications by monitoring Livewire exceptions, with recommendations for enhancing IP-based banning strategies and implementing alerting systems.]]>
            </summary>
                                    <updated>2026-09-10T14:38:18+01:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Security Tip: Help Password Managers Get It Right!]]></title>
            <link rel="alternate" href="https://securinglaravel.com/security-tip-help-password-managers-get-it-right/" />
            <id>https://securinglaravel.com/security-tip-help-password-managers-get-it-right/</id>
            <author>
                <name><![CDATA[Stephen Rees-Carter]]></name>
                <email><![CDATA[hello@example.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Learn how to use Laravel's password validation rule to generate HTML passwordrules attributes that help password managers suggest compliant passwords, improving user experience whilst maintaining security requirements.]]>
            </summary>
                                    <updated>2026-09-03T21:44:30+01:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Security Tip: Have You Heard Of Slopsquatting?]]></title>
            <link rel="alternate" href="https://securinglaravel.com/security-tip-have-you-heard-of-slopsquatting/" />
            <id>https://securinglaravel.com/security-tip-have-you-heard-of-slopsquatting/</id>
            <author>
                <name><![CDATA[Stephen Rees-Carter]]></name>
                <email><![CDATA[hello@example.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[A security warning about slopsquatting, where attackers register package names that AI coding agents commonly hallucinate. Includes practical advice on protecting your Laravel applications from malicious packages by carefully managing composer installs when using AI development tools.]]>
            </summary>
                                    <updated>2026-07-02T15:22:18+01:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Security Tip: Safely Updating Dependencies]]></title>
            <link rel="alternate" href="https://securinglaravel.com/security-tip-safely-updating-dependencies/" />
            <id>https://securinglaravel.com/security-tip-safely-updating-dependencies/</id>
            <author>
                <name><![CDATA[Stephen Rees-Carter]]></name>
                <email><![CDATA[hello@example.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[A comprehensive guide on safely updating dependencies in Laravel projects, covering the latest security features in Composer and npm like malware policies and minimum release age settings, plus practical tips for protecting your development environment from compromised packages.]]>
            </summary>
                                    <updated>2026-06-23T07:52:36+01:00</updated>
        </entry>
            <entry>
            <title><![CDATA[In Depth: Version Numbers Are Vanity Labels]]></title>
            <link rel="alternate" href="https://securinglaravel.com/in-depth-version-numbers-are-vanity-labels/" />
            <id>https://securinglaravel.com/in-depth-version-numbers-are-vanity-labels/</id>
            <author>
                <name><![CDATA[Stephen Rees-Carter]]></name>
                <email><![CDATA[hello@example.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[A deep dive into how supply chain attacks exploit version tags in package management systems. Examines recent attacks on tj-actions/changed-files and Laravel-Lang, explaining how attackers manipulate repository tags to inject malicious code into trusted dependencies.]]>
            </summary>
                                    <updated>2026-06-10T07:51:54+01:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Security Tip: Secure Your Repositories with Laravel Moat]]></title>
            <link rel="alternate" href="https://securinglaravel.com/security-tip-secure-your-repositories-with-laravel-moat/" />
            <id>https://securinglaravel.com/security-tip-secure-your-repositories-with-laravel-moat/</id>
            <author>
                <name><![CDATA[Stephen Rees-Carter]]></name>
                <email><![CDATA[hello@example.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[A practical guide to securing your Laravel repositories using Laravel Moat, a new tool from Nuno Maduro that reviews GitHub security posture and provides actionable recommendations for hardening your repositories against supply chain attacks.]]>
            </summary>
                                    <updated>2026-05-27T16:20:24+01:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Security Tip: The Signed URL Trap]]></title>
            <link rel="alternate" href="https://securinglaravel.com/security-tip-the-signed-url-trap/" />
            <id>https://securinglaravel.com/security-tip-the-signed-url-trap/</id>
            <author>
                <name><![CDATA[Stephen Rees-Carter]]></name>
                <email><![CDATA[hello@example.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[A crucial security tip revealing how Laravel's signed URLs can be exploited when not properly tied to specific user sessions, with practical examples of the magic login link vulnerability. Learn how to protect against this subtle but dangerous trap by making your signed URLs unique to prevent session hijacking attacks.]]>
            </summary>
                                    <updated>2026-04-30T20:28:03+01:00</updated>
        </entry>
            <entry>
            <title><![CDATA[In Depth: Don't Trust Public Livewire Properties]]></title>
            <link rel="alternate" href="https://securinglaravel.com/in-depth-dont-trust-public-livewire-properties/" />
            <id>https://securinglaravel.com/in-depth-dont-trust-public-livewire-properties/</id>
            <author>
                <name><![CDATA[Stephen Rees-Carter]]></name>
                <email><![CDATA[hello@example.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[An in-depth security analysis exploring how Laravel Livewire's public properties can be manipulated by malicious users through browser JavaScript, even when input fields are removed. This tutorial demonstrates the vulnerability with practical examples and explains why developers should never trust client-side data in Livewire components.]]>
            </summary>
                                    <updated>2026-04-23T21:29:08+01:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Security Tip: Stop Putting Actions on GET Requests!]]></title>
            <link rel="alternate" href="https://securinglaravel.com/security-tip-stop-putting-actions-on-get-requests/" />
            <id>https://securinglaravel.com/security-tip-stop-putting-actions-on-get-requests/</id>
            <author>
                <name><![CDATA[Stephen Rees-Carter]]></name>
                <email><![CDATA[hello@example.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[A crucial security guide explaining why GET requests should never be used for actions or state-changing operations in Laravel applications. The article covers the security differences between GET and POST requests and highlights the many ways GET requests can be exploited by malicious third parties.]]>
            </summary>
                                    <updated>2026-03-19T15:50:58+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Security Tip: Validate Config at Boot]]></title>
            <link rel="alternate" href="https://securinglaravel.com/security-tip-validate-config-at-boot/" />
            <id>https://securinglaravel.com/security-tip-validate-config-at-boot/</id>
            <author>
                <name><![CDATA[Stephen Rees-Carter]]></name>
                <email><![CDATA[hello@example.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[Learn why validating critical configuration values in your service provider's boot method is superior to checking them in controllers or middleware. This security-focused tutorial shows how to catch configuration issues early in your Laravel application lifecycle, preventing deployment failures and protecting users from unexpected errors.]]>
            </summary>
                                    <updated>2026-03-13T16:26:05+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Security Tip: Your JWT Might Be a Forever Key!]]></title>
            <link rel="alternate" href="https://securinglaravel.com/security-tip-your-jwt-might-be-a-forever-key/" />
            <id>https://securinglaravel.com/security-tip-your-jwt-might-be-a-forever-key/</id>
            <author>
                <name><![CDATA[Stephen Rees-Carter]]></name>
                <email><![CDATA[hello@example.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[A crucial security warning about JWT tokens without expiration dates that can become permanent access keys, even after users leave or credentials are compromised. Learn why setting proper expiration times is essential for Laravel applications using JWT authentication.]]>
            </summary>
                                    <updated>2026-03-13T16:26:52+00:00</updated>
        </entry>
            <entry>
            <title><![CDATA[Security Tip: Update your packages! (Yes, this again!)]]></title>
            <link rel="alternate" href="https://securinglaravel.com/security-tip-update-your-packages-yes-this-again/" />
            <id>https://securinglaravel.com/security-tip-update-your-packages-yes-this-again/</id>
            <author>
                <name><![CDATA[Stephen Rees-Carter]]></name>
                <email><![CDATA[hello@example.com]]></email>

            </author>
            <summary type="html">
                <![CDATA[When Stephen Rees-Carter tells you to update your packages you update your packages! This timely security reminder highlighting recent vulnerabilities in Livewire v3 and PsySH that are being actively exploited in the wild. The post emphasises the critical importance of keeping Laravel packages updated to protect against known security threats.]]>
            </summary>
                                    <updated>2026-02-20T10:13:14+00:00</updated>
        </entry>
    </feed>
