Security Whitepaper

1. Executive Summary

Meno Studio is a desktop application for visual website building, operating on a local-first architecture. The application was designed with user data privacy and security in mind.

Key Security Features

3. Network Communication and Ports

Locally Used Ports

Outbound Connections

Content Security Policy

Key restrictions enforced in production:

• No unsafe-eval in production

• Scripts only from 'self'

• External connections limited to whitelist

5. Security Mechanisms

Electron Security

Credential Encryption

GitHub tokens are encrypted using Electron's safeStorage API, which leverages OS-level encryption:

• macOS: Keychain Services

• Windows: DPAPI (Data Protection API)

Path Traversal Protection

Three-layer path validation protects against directory traversal attacks:

• Path normalization

• Check if within allowed directory

• Validate project is in ~/Documents/Meno

Rate Limiting

Input Validation

• Zod schemas — All JSON structures

• File size limit — Max 5MB for file reads

• Image size limit — Max 2MB for images

• Filename validation — Disallowed characters: <>:\"/\\|?*

• Binary detection — Exclude binary files from search

7. Cloud Infrastructure

Local-First Architecture

Meno Studio does NOT have a cloud backend. The application runs entirely locally on the user's machine.

External Services (Third-Party)

9. SSO and Authentication

Current Authentication Model

GitHub OAuth 2.0 (Device Flow):

• 1. User clicks "Login with GitHub"

• 2. App sends request to github.com/login/device/code

• 3. GitHub returns device_code and user_code

• 4. User goes to github.com/login/device

• 5. User enters user_code and authorizes

• 6. App polls /login/oauth/access_token

• 7. After authorization, receives access_token

• 8. Token encrypted and saved locally (safeStorage)

OAuth Permissions (Scope)

• repo — Full access to private repositories

• user:email — Access to user's email address

• read:org — Read organization membership

SSO Enterprise Support

GitHub OAuth is the only login method. GitHub OAuth provides SSO for Meno Studio:

Organizations using GitHub Enterprise can enforce SAML SSO authentication at the GitHub level. Since Meno exclusively uses GitHub OAuth for login, it automatically inherits these security controls:

• User must first authenticate through corporate IdP (Okta, Azure AD, etc.) to access GitHub

• Only after passing SSO can they authorize Meno

• Organization can restrict access only to members with enforced SSO

This means Meno supports SSO indirectly through GitHub Enterprise—without requiring native SAML/OIDC integration in the application itself.

11. Compliance and Certifications

Current Status

GDPR Considerations

• Data stored locally — user has full control

• Right to deletion — delete Meno folder

• Analytics (Supabase) — minimal, opt-out possible

• Data processing agreement — available upon request