Security fixes are applied to the latest released ADR Guard version. Consumers should prefer an exact SemVer tag or commit pin when reproducibility is required and upgrade to a newer release when a security fix is published.
Do not open a public issue containing exploit details, credentials, private ADR contents, or other sensitive information.
Use GitHub's private vulnerability reporting / Security Advisory flow for this repository when the Report a vulnerability option is available.
If private vulnerability reporting is not available, contact the maintainer through the GitHub profile and request a private reporting channel without including vulnerability details in the public message:
https://github.com/rodri-oliveira-dev
Please include privately:
- affected component and version / Action ref;
- affected execution mode (.NET Tool, MCP server, VS Code extension, container, or GitHub Action);
- impact and attack prerequisites;
- minimal reproduction;
- whether the issue is already public;
- suggested mitigation if known.
The reusable Action supports deterministic check and index, opt-in advisory or policy-enforced review, opt-in advisory impact, and explicit, read-only architectural drift verification. The drift adapter uses repository-local rules, an optional existing baseline, and explicitly supplied evidence; it does not run evidence producers or create or update baselines. The Action does not expose new, draft, or baseline as commands. Review credentials are accepted only through the caller step environment after review is selected explicitly; they are never Action inputs.
Version boundary: drift is included in the released Action @v1.10.0 and in the moving @v1 reference (currently pointing to v1.10.0). It is not included in the older @v1.9.0 release. Source changes and compatibility tags should not be assumed to have the same contract; verify the selected Action ref and the compatibility matrix.
Its runtime hardening, token model, workspace write boundaries, anonymous GHCR pull policy, version pinning, and annotation escaping are documented in:
Never place provider API keys or repository secrets in ADR Markdown, workflow inputs, issue reports, or command-line arguments. check, index, impact, and read-only drift do not require provider credentials. For explicit review, supply only the selected provider variable through the caller step environment as documented; the Action validates the provider-specific environment before forwarding it to the isolated container.
Please allow reasonable time for investigation and remediation before public disclosure. Once a fix is released, the maintainer may publish release notes or a security advisory describing the affected versions and mitigation.