Developer toolbar
Inspect the current rendered page from Astro's development toolbar with keyboard-accessible evidence views.
AI content toolsfrom Opace Astro integration · Version 0.1.0
Opace AI Content Integrity for Astro
Inspect rendered content through an Astro toolbar and create bounded build reports with the same named methods used by the browser checker.
SourceExact text and protected factsHeld in memory for this run
SignalsNamed checks with limitsNo universal authorship score
Watermark scanKnown keysReal SynthID mathematics; Anthropic production keys stay private
01 / Current release state
Submission candidate 0.1.0
Local npm and Astro checks passed
The exact package, npm metadata, Astro catalogue fields and repository documentation passed local independent review. It has not been published to npm or submitted to the Astro catalogue.
02 / Product scope
Astro toolbar inspection and report-only build evidence
The integration separates an interactive development view from an automated build report. The toolbar projects the visible page for review, while the build extractor records bounded method states and hashes. Neither route silently edits source files, stops a build or treats an editorial signal as proof of authorship.
Build reports
Write bounded report-only content checks during supported Astro builds without stopping the build.
Projection parity
The browser Worker and build extractor preserve the same visible text and receipt hash across tested rendering modes.
03 / Release evidence
Astro versions, rendering modes and package checks
Astro matrix
Static, server and hybrid builds are covered across the declared Astro 5, 6 and 7 versions.
Browser parity
Chromium, Firefox and WebKit confirm toolbar results match the build report at narrow and desktop viewports.
Package safety
Clean installation, licence inventory, path containment, package identity and dependency closure are verified.
04 / Requirements and limits
Before adding it to an Astro project
Choose the supported Node and Astro combination first, then decide whether the Dev Toolbar, report-only build check or both belong in the project. The integration keeps remote detection disabled and records unavailable methods instead of replacing them with a different claim.
- Use a Node version supported by the selected Astro release.
- Configure toolbar and report-only buildCheck options deliberately rather than treating editorial signals as authorship proof.
- The package does not enable a remote detector or content-bearing network route.
05 / Frequently asked questions
Astro integration questions.
Which Astro versions are covered?
Version 0.1.0 is tested across supported Astro 5, 6 and 7 versions in static, server and hybrid configurations, with the Node versions allowed by each Astro release.
Can a build report include my page content?
The default report uses hashes and method results. The integration keeps report paths inside the build output and does not send content to Opace.
Is the package on npm yet?
No. The exact version 0.1.0 submission candidate passed local independent review, but it has not been published to npm or submitted to the Astro catalogue.
Where should I report a problem?
Use the Opace contact page and include the product version, platform version, expected behaviour and the smallest safe reproduction. Do not include draft text, authentication tokens, personal data or customer information. Contact Opace.
Created by Opace Digital Agency
Need help putting content checks to work?
Opace designs practical AI and publishing workflows for organisations in Birmingham, across the UK and internationally.
Submission candidate
Use the checker now. Return for the release.
The software and submission materials are being checked as one release set. Until approval, this page records the product scope without presenting an unapproved download or store listing.