alpinejs-django

Pass

Audited by Gen Agent Trust Hub on Jul 6, 2026

Risk Level: SAFE
Full Analysis
  • [SAFE]: The skill outlines a secure architecture for client-side state management using Alpine.js within a Django environment, emphasizing clear ownership of state between the server and the browser.
  • [EXTERNAL_DOWNLOADS]: The skill references standard web development dependencies, including Alpine.js and HTMX, which are managed through established package managers (npm) and local static asset copying.
  • [SAFE]: Data handling instructions prioritize security by recommending x-text for automatic escaping of interpolated data and cautioning against the use of x-html or the |safe filter for untrusted content.
  • [SAFE]: Guidance is provided for maintaining Content Security Policy (CSP) compatibility, recommending the use of Alpine.js's specific CSP-compliant build to avoid the requirement for unsafe-eval in the browser.
  • [SAFE]: An analysis of data ingestion patterns demonstrates the use of secure practices:
  • Ingestion points: Server-side data enters the client-side context via Django template variables and json_script blocks as shown in SKILL.md.
  • Boundary markers: The instructions recommend using json_script to provide structured and delimited data to the browser, which is a secure standard for passing data to JavaScript.
  • Capability inventory: Functionality is restricted to ephemeral browser-side UI state management and accessibility attribute updates; no file system writes or unauthorized network operations are instructed.
  • Sanitization: Explicit instructions are provided to use character-escaping directives and to avoid raw HTML rendering of external data, reducing the risk of cross-site scripting (XSS).
Audit Metadata
Risk Level
SAFE
Analyzed
Jul 6, 2026, 01:03 AM
Security Audit — agent-trust-hub — alpinejs-django