Skip to content

Security: ENDEVSOLS/LongTracer

Security

SECURITY.md

Security Policy

Supported Versions

Version Supported
0.1.x ✅ Yes

Older versions are not actively maintained. Please upgrade to the latest release.

Reporting a Vulnerability

Do not open a public GitHub issue for security vulnerabilities.

Please report security issues privately via one of the following:

What to include

  • A clear description of the vulnerability
  • Steps to reproduce or a proof-of-concept
  • Affected version(s)
  • Potential impact assessment

Response timeline

Stage Timeframe
Acknowledgement Within 48 hours
Initial assessment Within 5 business days
Fix or mitigation Within 30 days (critical issues prioritized)
Public disclosure After fix is released

We follow coordinated disclosure. You will be credited in the release notes unless you prefer to remain anonymous.

Scope

Issues in scope:

  • Arbitrary code execution via crafted inputs to CitationVerifier or LongTracer
  • Path traversal or unsafe file writes in trace export functions
  • Credential or secret leakage through logs or trace output
  • Dependency vulnerabilities with direct exploitability

Out of scope:

  • Vulnerabilities in optional third-party backends (MongoDB, Redis, PostgreSQL) — report those upstream
  • Issues requiring physical access to the machine
  • Social engineering

Security Best Practices for Users

  • Secrets: Never pass API keys or credentials as part of response or sources strings — they may appear in trace output
  • Trace storage: Restrict access to ~/.longtracer/traces.db and any configured database backends
  • HTML reports: export_trace_html() output contains raw LLM response text — treat it as untrusted content before serving in a browser
  • Dependencies: Pin dependency versions in production and audit with pip audit or safety

Dependency Security

LongTracer uses a minimal core dependency set. To audit your installation:

pip install pip-audit
pip-audit

There aren’t any published security advisories