Product

Gray Safe

Detect and fix malformed YAML frontmatter, enforce content rules, and keep multi-locale pages consistent.

Request Beta Access Overview & Details

Features

Web + CLI Validator

Localhost-only web validator and CLI scanner for bulk checks; clear errors/warnings and optional auto-fix.

Primary Table Enforcement

Enforce a single primary table in page headers (modes: `auto_fix` or `strict`).

Locale helpers

Create missing locale markdown files and propagate metadata like `logo_size` across locales.

Low-risk security model

Local-only endpoint, permission checks, rate-limiting and path privacy to avoid exposure.

Obfuscation

Simple obfuscation helpers to reduce easy client-side analysis (not a security boundary).

Gallery

Gray Safe screenshot

Licensing

Columns
Single site
€49 (one-time)
25%/yr (optional)
1 domain
Developer (5 sites)
€199
25%/yr (optional)
Up to 5 sites
Agency / Unlimited
€599
25%/yr (optional)
Unlimited

Overview

Gray Safe helps Grav site maintainers and developers detect and fix malformed YAML frontmatter and keep site content consistent across locales. Use the Admin validator (localhost-only) or the CLI tool for full scans. The plugin enforces a single primary table in page headers, offers auto_fix or strict modes, includes locale helpers and a small obfuscation helper for client assets.

Security & hack protection

  • Local-only validator endpoint (configurable LAN allow)
  • Permission checks: admin.gray_safe_validate required
  • Rate limits / blocking recorded in user/data/r4it_gray_safe/ips.json
  • Responses use safe relative paths (no absolute filesystem paths)

Admin: Rate limits & blocking (non‑sensitive)

  • Gray Safe dampens repeated, suspicious or malformed requests per source. Measures escalate stepwise (e.g. throttling → temporary block). Exact thresholds are intentionally not published; administrators can tune parameters in user/config/plugins/r4it_gray_safe.yaml.
  • Incidents are logged locally in user/data/r4it_gray_safe/ips.json. Entries contain aggregated metrics (hit counts, first/last seen, status) — no full request payloads or absolute server paths.
  • Blocked IPs can be inspected and released via the Admin UI or by rotating/inspecting the data files; automated rotation/archiving of older entries is recommended.

Admin: Input protection & YAML validation (non‑sensitive)

  • Validators focus on structural frontmatter issues (indentation, data types, duplicate keys) and on consistency rules (single primary table enforcement).
  • Inputs are normalized and unnecessary control characters removed; UI output only includes safe relative path references. Absolute server paths and sensitive internals are never revealed.
  • The web validator and audit reports are local and rights‑protected; CLI tools are intended for maintenance tasks and should be used with care in production.

Demo & Support

  • Demo ZIP in the info repo: packaging/demo.zip
  • EULA included in plugin: user/plugins/r4it_gray_safe/LICENSE.en.md
  • For beta access or questions: contact via the site contact form