Skip to content

Security: ecomxco/setup-data-warehouse

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
1.4.x ✅ Current
1.3.x
1.2.x
1.1.x ⚠️ Security fixes only
1.0.x ❌ End of life

Data Sensitivity

This repo handles customer PII (emails, names, purchase history, support tickets, identity graph). Key rules:

  • warehouse.dbnever commit. Contains raw customer data.
  • data-warehouse/**/*.jsonlnever commit. Raw API responses.
  • data-warehouse/**/*.csvnever commit. Platform exports.
  • data-warehouse/cursors.jsonnever commit. Contains table timestamps.
  • data-warehouse/manifest.jsonnever commit. Contains run metadata.
  • environments/**/.envnever commit. API keys and secrets.

All of the above are in .gitignore by default.

Identity Data

The identity_graph table links customer identities across platforms via email matching. This data is considered high-sensitivity PII and must never be exported, logged, or shared outside the warehouse.

API Keys

  • Store all credentials in environments/{service}/.env
  • Use Apple Keychain via /setup-environment where possible
  • Rotate API keys periodically
  • Never log access tokens to stdout

Reporting a Vulnerability

If you discover a security vulnerability, please report it privately:

  1. Email: jim@ecom-x.com
  2. Do NOT open a public GitHub issue for security vulnerabilities
  3. Include steps to reproduce and potential impact
  4. We will respond within 48 hours

Responsible Disclosure

We follow responsible disclosure practices. Security issues will be patched and credited to the reporter (if desired) once a fix is released.

There aren't any published security advisories