KFKonstantinos Foskolakis

[RELIABILITY AND SECURITY]

Sanitized exports, scoped file access, and validation tooling

The release excludes live credentials, database files, backups, raw secrets, and private runtime state.

Release hygiene

  • Credential IDs removed from public workflow exports.
  • Execution markers redacted from evidence files.
  • Secret-scan script included in the public repo.

Runtime boundaries

  • PostgreSQL was internal to the local Docker environment.
  • File access was scoped with n8n configuration.
  • Backups were validated but not published.

Validation

  • Workflow JSON validation.
  • Sample JSON validation.
  • Screenshot readability checks.

Debugging method

  1. Reproduce exact runtime behavior
  2. Isolate CLI, Docker, file, credential, and database layers
  3. Inspect logs, mounts, node errors, and workflow inputs
  4. Apply minimal fixes such as scoped file access
  5. Verify with PostgreSQL counts and screenshots
  6. Document and package sanitized evidence

Open the public audit files

Repository security auditSanitization notesSecret scan script