Base44: Security Scan Fixes Now Tracked in the AI Chat
Base44Base44 now records every applied security scan fix as a message in the app's AI chat, automatically creating a checkpoint beforehand so developers can see exactly what changed and revert if needed. The update covers data permission fixes, security header fixes, and package fixes. It also adds a new table view for reviewing flagged issues, letting users filter by type or severity, select which ones to fix, and ignore items that aren't a concern for their app (with the option to restore them later).
Security Fixes Get Full Visibility and Reversibility
Base44's built-in security scanner has long helped developers catch common vulnerabilities, such as exposed data permissions, missing security headers, and risky package configurations, before publishing an app. Previously, applying a suggested fix happened somewhat silently: the change was made, but tracing exactly what was altered required digging through version history. Base44 closed that gap by tying security fixes directly into the AI chat interface that most builders already use to track their app's evolution.
Fixes Now Appear as Chat Messages with Checkpoints
When a user applies a security scan fix, Base44 automatically creates a checkpoint first, then logs the fix as a message in the app's AI chat. This means developers get a running, readable history of every security-related change alongside their regular build conversation, rather than a separate, disconnected changelog. If a fix causes unexpected behavior, breaks a feature, or simply isn't wanted, the checkpoint makes it straightforward to revert back to the exact state before the fix was applied.
This update applies across the three main categories of fixes the scanner supports: data permission issues, security header issues, and package-related issues.
A New Table View for Managing Issues
Alongside the chat integration, Base44 introduced a dedicated table view for reviewing scan results. Instead of working through a flat list, users can now filter detected issues by type or severity, making it easier to prioritize what to fix first on larger or more complex apps. The table also supports selecting specific issues to fix in a batch rather than one at a time.
Ignoring Issues That Don't Apply
Not every flagged issue is relevant to every app. The updated flow lets users mark specific issues as "not a concern" so they no longer clutter the active issue list, while still preserving the ability to restore and revisit them later if circumstances change (for example, if the app's audience or use case shifts).
Why It Matters
For a platform where non-technical builders are frequently the ones deciding whether to accept security recommendations, this update reduces the risk of blindly applying fixes that could break functionality. By surfacing the change in the same chat thread used for app development and pairing it with an automatic checkpoint, Base44 gives users a lightweight, familiar safety net for security-related changes, without requiring a separate audit or rollback process.