Skip to content

Security: smileformylove/XScientist

Security

.github/SECURITY.md

Security Policy

Reporting a vulnerability

Please do not open a public issue for potential security vulnerabilities.

Instead, use GitHub's Private Vulnerability Reporting / Security Advisories for this repository if enabled. If it is not available, open an issue with minimal details and request a private follow-up from maintainers.

Supported versions

Security fixes are applied to the default branch and the latest tagged minor release when one exists. The current 0.1.x source line is alpha software; older untagged snapshots are not supported.

Running generated experiments

Treat generated code and downloaded research artifacts as untrusted. Prefer the isolated executor, keep network access disabled unless inputs must be fetched, pin container images by digest, and never mount credential or personal data directories into an experiment workspace. A valid ARA records provenance; it is not proof that its code or inputs are safe.

Credentials and privacy

Use xscientist provider add for hidden credential input. It writes only to a Git-ignored, user-only .env; provider metadata contains environment-variable names, never values. Run xscientist privacy audit . --history before making a repository public. Findings contain locations and rule names only, not the matched secret or private value. If a real credential ever reached Git history, revoke it first and coordinate a history rewrite separately.

There aren't any published security advisories