Astro Integration
Astro Status
A static-first status endpoint for Astro — honest about what static sites can and cannot claim.
Last Updated: 01 April 2026
Usage Snapshot
153
Downloads in Last 30 Days
v1.1.0
Latest npm Version
Source: npm registry
Why This Plugin Exists
Static sites cannot truthfully report runtime health, yet many status endpoints pretend they can.
Astro Status exposes a build-time status instead — answering one honest question: did this site build successfully, and when?
The result is a deterministic, cache-safe status file designed for monitoring systems and tooling.
Design Principles
- Static-first honesty
- Deterministic output
- No runtime claims
- Machine-readable by default
- Zero user input
What This Plugin Delivers
- Generates a static /status.json file at build time
- Includes build timestamp
- Detects Astro output mode automatically
- Cache-safe and CDN-friendly
- No runtime JavaScript
- No environment variable access
- No request handling
Installation
npm install astro-status
The plugin runs during astro build and writes a static status file to the output directory.
FAQs
Is Astro Status a live health check?
No. Astro Status reports build success only. It makes no claims about runtime liveness.
Where is the status file written?
The plugin writes a static /status.json file to the final build output directory.
Is the output cache-safe?
Yes. The file is static and safe to cache indefinitely behind any CDN.
Implementation FAQs
What question does Astro Status answer?
It answers whether the site built successfully and when — nothing more.
Does Astro Status run at runtime?
No. The plugin runs only at build time and produces static output.
Does Astro Status claim the site is live?
No. It explicitly avoids claiming runtime liveness.
Is Astro Status compatible with CDNs?
Yes. The static output works perfectly behind any CDN.
What happens if the status file cannot be written?
A warning is logged and the build continues safely.
Will runtime status be supported?
Possibly in v2, for hybrid or server output. v1 intentionally does not attempt this.
Project Links
Source code, package distribution, releases, and documentation.
Need Implementation Details?
Read the FAQs for usage patterns, integration caveats, and rollout guidance.