Skip to content
This repository was archived by the owner on Mar 13, 2026. It is now read-only.

Security: 0xHoneyJar/rune

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
0.2.x
0.1.x
< 0.1

Reporting a Vulnerability

We take security seriously. If you discover a security vulnerability, please follow these steps:

For Private Disclosure (Preferred)

  1. Do NOT create a public GitHub issue

  2. Email the security team at security@honeyjar.xyz with:

    • Description of the vulnerability
    • Steps to reproduce
    • Potential impact assessment
    • Any suggested fixes (optional)
  3. Expect a response within 48 hours

  4. Coordinate disclosure timeline with maintainers

What to Report

  • Authentication/authorization bypasses
  • Injection vulnerabilities (command, code, etc.)
  • Secrets exposure risks
  • Insecure default configurations
  • Agent prompt injection vectors
  • MCP server security issues

What NOT to Report

  • Vulnerabilities in dependencies (report to upstream)
  • Social engineering attacks
  • Physical security issues
  • Denial of service (unless critical)

Security Measures

Automated Security Scanning

This repository uses:

  • TruffleHog - Secret detection
  • GitLeaks - Secret scanning
  • Dependabot - Dependency vulnerability alerts
  • CodeQL - Static code analysis

Branch Protection

The main branch is protected with:

  • Required pull request reviews
  • Required status checks
  • No force pushes
  • No deletions

Secrets Management

  • All secrets must use environment variables
  • No hardcoded credentials in code
  • .env files are gitignored
  • Secret rotation procedures documented

Security Best Practices for Contributors

When Adding New Features

  1. Never commit secrets - Use environment variables
  2. Validate all inputs - Especially in agent prompts
  3. Sanitize outputs - Prevent information disclosure
  4. Review MCP integrations - External APIs need security review

When Using MCP Servers

  1. Use minimal required permissions
  2. Validate data from external sources
  3. Handle errors without exposing sensitive info
  4. Test with mock data before production

Vulnerability Disclosure Timeline

Day Action
0 Vulnerability reported
1-2 Acknowledgment sent
3-7 Initial assessment complete
8-30 Fix developed and tested
31-45 Coordinated disclosure (if approved)

Security Updates

Security updates are announced via:

  • GitHub Security Advisories
  • CHANGELOG.md updates
  • Discord announcements (for critical issues)

Thank you for helping keep Loa secure!

There aren’t any published security advisories