Nova Ohdear Tool Laravel Package

Product Decisions This Supports

• Dashboard consolidation for internal ops. The tool renders Oh Dear's site monitoring — uptime, SSL certificate health, broken links, scheduled-job checks — directly inside Laravel Nova. For teams already on Nova, this supports the roadmap decision to retire a separate SaaS tab from the daily check ritual, collapsing one dashboard out of on-call and product staff's morning sweep.
• Post-deploy go/no-go confidence. A glanceable health panel inside the admin panel where engineers already are supports release decisions ("is anything red after this deploy?") and shortens the "is this ours or Oh Dear's?" question during an incident. It informs ownership triage and first-glance verification — it does not replace Sentry, Horizon, PagerDuty, or Oh Dear's own alerting.
• Build vs. buy for monitoring surfacing. This package is the concrete baseline for the "subscribe to the SaaS, build the 50-line Nova card" tradeoff. Use it as the effort anchor when deciding whether to keep an internal health widget, fork this, or point stakeholders at Oh Dear's native UI.
• Maintenance-mode reality check. 29 stars, zero dependents, one cosmetic patch (v1.1.4, a tool page title, #31) since April 2021 are decision-grade signals. Treat this as a convenience artifact, not a platform bet: fork-and-own, not a supported dependency in any roadmap spanning more than a year.
• Diligence flag to resolve before sign-off. Package metadata says "display the application log," while the name, README, and integration surface describe Oh Dear monitoring. This changes the security review (log contents and file-path access vs. an outbound API token) and the entire value story. Do not approve adoption until engineering confirms what actually ships.

When to Consider This Package

Consider it only when all of the following hold:

• You already run Laravel Nova 3.x (Laravel 8 / PHP 7-era) with no near-term major upgrade planned.
• Oh Dear is already your source of truth for uptime, SSL, broken links, and cron monitoring — you are consolidating its display, not adopting the SaaS because of this package.
• The audience is internal engineers and PMs with Nova access, and the need is display-only convenience — not paging, on-call rotation, or SLA reporting.
• You are prepared to fork or vendor the MIT-licensed code, pin it, and own patches; upstream velocity is effectively zero.
• The description mismatch is resolved with engineering so access-control and security review match reality.

Look elsewhere — or build a small first-party Nova card — when:

• You are on Nova 4/5 or a modern Laravel/PHP stack; expect composer constraint conflicts, asset-registration breakage, and unaddressed Oh Dear API drift.
• You need alerting, incident workflow, or SLA dashboards — this is a read-only viewer with no writes back to Oh Dear.
• You need maintenance guarantees or security patching — neither exists; one cosmetic release is not a maintenance commitment.
• You don't already use Oh Dear and Nova — adopting both to avoid a bookmark is a poor trade.
• The sole justification is "one fewer browser tab." At this adoption profile, a custom Nova card plus Oh Dear webhooks is comparable effort with far better long-term fit.

How to Pitch It (Stakeholders)

For executives: This is a small, MIT-licensed convenience layer that surfaces our existing Oh Dear monitoring status inside the Laravel admin panel our engineers and PMs already use every day. It is cheap to trial, carries no vendor lock-in, and removes a dashboard from the incident-response routine. The tradeoff is ownership: the only recent upstream change is a cosmetic page-title fix, and adoption is essentially zero (29 stars, zero dependents). Recommendation — trial only if we're on the matching Nova version, and budget a half-day to fork-and-own it; preferably, replicate the same view as a first-party Nova card, which eliminates the maintenance risk entirely while preserving the benefit.

For engineering: It's a thin, read-only Nova tool that renders Oh Dear checks inside the admin panel — no migrations, no scheduled jobs, no writes back. v1.1.4 adds a tool page title (#31) and nothing more; don't read it as renewed compatibility work. The code is small and permissively licensed, so forking is low-friction; the real cost is upgrade tax against Nova and Oh Dear's API. Before committing: verify version compatibility, confirm whether the package is actually an Oh Dear monitor or a log viewer (metadata is inconsistent), store the token in config/services.php rather than reading env() at runtime so config:cache doesn't blank it, gate it behind canSee/authorize for ops roles only, cache the API responses to avoid slow cold loads and rate limits, and pin or vendor the fork. If we want this capability long-term, an in-house Nova card backed by Oh Dear's API is likely cheaper to maintain and lets us add the alerting hooks the original lacks.