Download the PHP package d3creative/statamic-sentinel without Composer

Sentinel by D3 Creative

Platform and dependency audits for Statamic sites.

Sentinel cross-references your installed versions against the OSV vulnerability database, endoflife.date, Packagist, and the npm registry, then surfaces ranked findings (vulnerabilities by severity, packages past EOL, available updates) directly in the Statamic Control Panel. It tracks a rolling 365-day history so you can diff snapshots and see exactly what moved between updates, and email reports can be sent on demand or on a daily, weekly, or monthly schedule.

Documentation

• Usage - how scanning works, where data lives
• Security - reporting vulnerabilities
• Changelog - release history

What it shows

• Statamic version - current version vs latest stable release
• PHP version - with lifecycle status (Active / Security Only / End of Life)
• Composer vulnerabilities - packages in composer.lock checked against the OSV vulnerability database
• npm vulnerabilities - packages in package-lock.json checked against OSV
• Update history - snapshot of versions and counts is recorded whenever any tracked value changes, viewable in the utility's History tab. Retained for 365 days. Each snapshot also stores per-package installed versions so update diffs can be reconstructed later.

Reporting

• Email status report - super admins can send the full current audit to up to 10 recipients from the utility's Status Report tab.
• Email update report - super admins can send a diff between the two most recent snapshots (platform version changes, packages updated/added/removed, vulnerabilities resolved/introduced) from the utility's Update Report tab. Run an update, hit Refresh to capture a fresh snapshot, then click Send Update Report - recipients see exactly what moved. If nothing changed since the last snapshot, you can opt to resend the last meaningful diff via Send anyway.
• Preview before sending - both report tabs include a Preview button that opens the rendered email in a modal so you can see exactly what recipients will get before clicking Send.
• Scheduled status reports - the Status Report tab includes schedule controls (daily/weekly/monthly cadence, time, recipient list) below the manual send form. The addon auto-registers the matching Laravel scheduler entry on boot, and each scheduled run does a fresh scan first - so the email is current AND the CP's cached audit + history get updated for free. Update reports aren't scheduled - they're meant to verify a manual update + scan, so they're send-on-demand only. Requires the standard * * * * * php artisan schedule:run cron entry on the host.
• Both email send endpoints are rate-limited to 6 requests per minute.

Users (who's online)

The utility's Users tab (super admins only) lists every control-panel user with their current activity and last login:

• Status - a green dot and "Active ..." when the user has made a CP request within the online window (default 5 minutes), otherwise a grey dot with "Last seen ..." or "No recent activity". A count of who's online shows on the tab.
• Last login - Statamic's own last-login timestamp, shown relative (or "Never").

Statamic has no built-in "who's online" concept, so Sentinel tracks it with a lightweight CP middleware that records each authenticated user's last-active time (throttled to about one write per minute per user, persisted so it survives cache:clear). Because activity only advances on a CP request, "online" means "active in the last few minutes" - an open but idle tab drops to "last seen". Only timestamps are stored (no IP or user-agent).

• SENTINEL_TRACK_ACTIVITY=false disables the tracking entirely (the tab then shows last-login only).
• SENTINEL_ONLINE_WINDOW sets the minutes of inactivity still counted as online (default 5).

Content Freeze

Coordinate update windows with CP users. Schedule a heads-up email, show banners through the lifecycle of the work, and send an all-clear when done. Useful for client sites where editors and developers share the CP.

• Scheduling - super admins set two times on the utility's Content Freeze tab: when the heads-up email goes out, and when the freeze starts. Recipients are a comma-separated list (max 10).
• Heads-up email - sent automatically at the notification time. Tells recipients when the window starts and what to expect.
• CP banners - injected below the global header on every authenticated CP page, in normal document flow (no fixed overlay). Three states:
  • Upcoming (blue, dismissable) - shows from schedule through to freeze start. Includes a Learn more button that opens a modal mirroring the heads-up email. Dismissals are session-scoped, so the banner reappears the next time a user signs in.
  • Active (amber, non-dismissible) - shows once the freeze starts. Paired with a first-load modal per user (cookie-scoped to the freeze id, so each new freeze re-prompts).
  • Complete (green, dismissable) - briefly shown after the freeze ends.
• Mark complete - one-click in the CP (or php please sentinel:freeze:complete) sends the all-clear email and switches to the green banner. Available from any pre-complete state, so you can end early if the update finishes faster than scheduled.
• Cancel freeze - one-click in the CP. Aborts a scheduled or notified freeze without sending the all-clear email. The confirm prompt adapts: from notified it warns that recipients already received the heads-up. Not available once the freeze is active - use Mark complete instead so the all-clear still goes out.
• Email previews - both the heads-up and all-clear emails have Preview buttons in the CP that render exactly what recipients will receive.
• Front-end stays live - the freeze only affects the CP. Visitors don't see anything.
• CLI - php please sentinel:freeze:start "2026-05-13 08:00" "2026-05-13 09:00" [email protected] mirrors the CP form. Same validation, same emails.

State transitions are driven by every-minute cron (sentinel:freeze:tick-notifications, sentinel:freeze:tick-activations) registered by the addon. Production sites should rely on the standard * * * * * php artisan schedule:run cron entry. A fallback middleware on the statamic.cp group also ticks state on every CP request, so dev environments and shared hosts without scheduler access still see the expected transitions while an editor is in the CP. Both paths are idempotent.

Display timezone is configurable via SENTINEL_FREEZE_TIMEZONE. Unset, times use the Laravel app timezone and show no timezone letters; set, they show the timezone abbreviation (e.g. BST) and, when it differs from the server tz, render both side-by-side. See Other settings.

Installation

Then add the widget to your CP dashboard by adding sentinel to the widgets array in config/statamic/cp.php:

Usage

Sentinel scans on demand, not on every CP load. After dependency updates, hit Refresh in the widget/utility header to re-read your lockfiles - the cached audit doesn't update on its own. See USAGE.md for scanning, scheduling, and storage details.

Reporting, history, scheduling, and Content Freeze are super-admin only. A non-super user granted the access sentinel utility permission sees a read-only view: the Current audit plus Refresh, without the report/history/freeze tabs.

Branding (optional)

Sentinel ships branded for D3 Creative out of the box - no configuration needed. The widget, utility, and report emails attribute to D3 Creative, link to the managed-maintenance service, and include a Need help with your website? button. Agencies installing Sentinel on a client site can white-label it, or remove the branding entirely.

White-label for your agency - set any of these env vars in the host app's .env:

• SENTINEL_DEV_NAME - replaces the footer attribution with This report was generated by Your Agency. (linked to SENTINEL_DEV_URL when also set, plain text otherwise).
• SENTINEL_DEV_URL - the address the brand name links to in the widget, utility, and email footers.
• SENTINEL_DEV_EMAIL - the address behind the Need help with your website? mailto button on the status report email, pre-filling the subject with the site host.

Remove branding entirely - set:

This renders Sentinel fully unbranded ("Sentinel for Statamic", no link, no CTA button) regardless of the SENTINEL_DEV_* values.

Other settings

• SENTINEL_FREEZE_TIMEZONE - display timezone for content-freeze times in the CP and freeze emails. Example: SENTINEL_FREEZE_TIMEZONE='Europe/London'.
  • Unset (default): times use the Laravel app timezone and render without timezone letters, e.g. 4 Jul 2026, 08:00.
  • Set: times render the timezone abbreviation too, e.g. 4 Jul 2026, 08:00 BST. When the configured zone differs from the server (app) timezone, both are shown side-by-side, e.g. 4 Jul 2026, 09:00 BST / 08:00 UTC.

Publishing the config (survives config:cache)

All the env vars above are read at config-build time. On a host that runs php artisan config:cache in production, reading them only from the addon's vendor config can leave settings blank if anything perturbs the cache build. To make your settings survive config:cache, publish and commit the config file so it loads as a first-class host config:

This writes config/statamic-sentinel.php into your app. Committing it means config:cache always captures the values, independent of addon boot timing.

Requirements

• PHP 8.0+
• Statamic 3.3, 4.x, 5.x, or 6.x
• If your host app sets a Content Security Policy, the freeze banner and modal use inline <style> and <script> to position the overlay and the auto-open dialog. Allow style-src 'unsafe-inline' and script-src 'unsafe-inline' on CP routes, or whitelist Sentinel's inline assets via nonce/hash. With a strict CSP and no allowance, the banner falls back to a normal-flow position and the auto-open modal won't run - the addon's reporting and audit features are unaffected.

Support

This addon is maintained by D3 Creative. For enquiries about managed Statamic maintenance, visit d3creative.uk/services/statamic-maintenance.

License

Released under the MIT License.