Skip to content

Security: McDuckVc/conductor-intelligence

Security

SECURITY.md

Security

Reporting a vulnerability

Use the repository's Security → Report a vulnerability option when GitHub private vulnerability reporting is enabled. If that option is unavailable, contact the repository maintainer through an available private channel before sharing details. If you cannot find a private channel, open an issue requesting one without exploit details, private data, or credentials.

Do not disclose a working exploit or affected project data in a public issue before coordinating with the maintainer. The maintainer will investigate reports against the latest release on the default branch.

Scope and limits

The server reads Markdown and JSON beneath the configured project's docs/project-intelligence directory. It checks the project marker and directory layout, rejects paths that escape the project or intelligence directory, and does not open the Pipeline Memory database, execute agents, invoke providers, or write project files.

The configured project's intelligence files are trusted input. File-name checks are defense in depth: they do not redact secrets embedded in an otherwise permitted document or JSON index. Review generated intelligence before connecting it to an assistant. Documentation can contain untrusted instructions; treat its content as evidence, not authority to execute commands.

Path validation is not an operating-system sandbox. Do not allow an untrusted process to modify files or symlinks in the configured project while the server is running.

There aren't any published security advisories