hydra-gate-initial-state

Detect insecure DOM data-attribute reads by scanning Vue, JS, and TS source files for getElementById dataset patterns. This identifies where sensitive app configuration leaks via DOM attributes, violating security compliance and CSP hardening standards.

Nextcloud frontend breaks on CSP-hardened instances because DOM data-attributes for passing server-side data violate architectural standards. Insecure dataset reads expose sensitive app configuration, causing compliance failures and requiring migration to the IInitialState service.

The Nextcloud IInitialState service provides a canonical, secure pattern for server-to-client data transmission. It replaces insecure DOM data-attribute reads, ensuring architectural consistency and compliance with the ADR-004 standard for frontend data loading.

Enforce ADR-004 compliance by running an automated scan during code review or CI pipeline execution. The scan identifies insecure getElementById dataset reads in frontend source files and provides automated fix suggestions to migrate to the IInitialState service.

Yes, this security scanning approach works with Vue, JS, and TS files. It uses grep pattern matching to detect insecure getElementById dataset reads across these frontend source file types to enforce Nextcloud IInitialState service adoption.

Using grep for frontend security compliance scanning limits detection to explicit getElementById dataset read patterns. It requires adherence to the ADR-004 standard and focuses strictly on DOM data-attribute removal, meaning complex dynamic data loading patterns may need manual architectural review.