Skip to content

Security: agenisea/agentic-mathematical-engine

Security

SECURITY.md

Security Policy

Reporting a Vulnerability

If you discover a security vulnerability in Amy, please report it responsibly:

  1. Do not open a public issue
  2. Email the maintainers directly or use GitHub's private vulnerability reporting feature
  3. Include a detailed description of the vulnerability
  4. Provide steps to reproduce if possible

We will respond within 48 hours and work with you to understand and address the issue.

Supported Versions

Version Supported
Latest Yes

Security Considerations

Local LLM (Ollama)

Amy uses Ollama with DeepSeek-R1 running locally:

  • No external API keys required for default operation
  • Data stays local — queries processed by local Ollama instance
  • No external network calls for LLM inference

Input Validation

All user inputs are validated before processing:

  • Query length limits
  • Type checking on inputs
  • Unit validation via Unitful.jl
  • Bounds checking on numerical operations

Code Execution

The engine does not execute arbitrary code. All computations are limited to predefined tool functions.

Best Practices for Deployment

  1. Run in isolated Julia environment with --project=.
  2. Set resource limits via AgentConfig (max tool calls, timeouts)
  3. Keep Julia and dependencies updated
  4. Monitor for unusual query patterns
  5. Validate external data sources (ephemeris, reference values)

Data Handling

  • Queries are not logged by default
  • Session data is in-memory only
  • No telemetry collected
  • Full offline operation supported

There aren’t any published security advisories