Skip to content

Security: sane-apps/SaneScript

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
1.x.x

Security Model

App Sandbox

SaneScript uses a Finder Extension architecture:

  • Main app is sandboxed
  • Finder extension has limited entitlements
  • Scripts execute in user context (not elevated)

Script Execution

SaneScript runs user-defined scripts on files:

  • Scripts run with the user's permissions
  • No elevated privileges are used
  • Scripts have access to files selected in Finder

Code Signing

  • Signed with Developer ID: Stephan Joseph (M78L6FXD48)
  • Notarized by Apple
  • Hardened runtime enabled

Data Security

  • Scripts are stored locally in app container
  • No cloud sync or remote storage
  • No credentials or tokens stored

Reporting a Vulnerability

If you discover a security vulnerability, please:

  1. DO NOT open a public issue
  2. Email security concerns to: security@saneapps.com
  3. Or use GitHub's private vulnerability reporting

What to Include

  • Description of the vulnerability
  • Steps to reproduce
  • Potential impact
  • Suggested fix (if any)

Response Timeline

  • Initial Response: Within 48 hours
  • Assessment: Within 1 week
  • Fix Timeline: Depends on severity
    • Critical: Patch release within 48 hours
    • High: Patch release within 1 week
    • Medium: Next regular release
    • Low: Backlog for future release

Recognition

Security researchers who report valid vulnerabilities will be:

  • Credited in release notes (unless they prefer anonymity)
  • Added to SECURITY.md acknowledgments

Security Best Practices for Users

  1. Download from official sources only

    • saneapps.com
  2. Verify code signature

    codesign -dv --verbose=4 /Applications/SaneScript.app
    # Should show: Developer ID Application: Stephan Joseph (M78L6FXD48)
  3. Keep the app updated

    • Enable auto-update checks
    • Security fixes are prioritized
  4. Review scripts before running

    • Especially imported scripts
    • Scripts have full user-level access to files

Known Security Considerations

Script Execution Risks

SaneScript executes user-defined scripts. A malicious script could:

  • Delete or modify files
  • Access sensitive data
  • Execute arbitrary commands

Mitigations:

  • Scripts run with user permissions (not root)
  • Review all scripts before running
  • Be cautious with imported scripts
  • Test scripts on non-critical files first

Imported Script Risks

When importing scripts:

  • Scripts may contain malicious code
  • No automatic safety validation is performed

Mitigations:

  • Only import scripts from trusted sources
  • Review script content before importing
  • Test in a safe environment first

Acknowledgments

Thanks to the following for responsible disclosure:

  • (No reports yet)

There aren’t any published security advisories