Skip to content

docs: route security reports privately - #103

Merged
jsugg merged 1 commit into
mainfrom
docs/route-private-security-reports
Oct 13, 2026
Merged

jsugg merged 1 commit into
mainfrom
docs/route-private-security-reports

Conversation

@jsugg

@jsugg jsugg commented Oct 13, 2026

Copy link
Copy Markdown
Owner

Changes

  • Send security reports to the existing private GitHub reporting route, with the email option retained in the security policy.
  • Warn before the public bug form and request sanitized atx doctor --json output, using the failing command's state override.
  • Keep blank issues enabled. No approval to disable them is assumed.
  • Gate the private route, doctor command and privacy guidance with the existing CI policy checks.

Doctor JSON does not report OS release or ATX version. The form still asks for those details once, without changing the JSON API.

Checks

  • YAML/template contract passes, after first rejecting the absent contact config.
  • Policy mutations reject a missing private contact, unapproved blank-issue disabling and a missing doctor request.
  • All shell scripts, real workflow guards, canonical Markdown and diff checks pass. Template YAML/content are checked separately from the intentionally excluded Markdown templates.
  • Clean scripts/check.sh full passes in an owned fresh Cargo target, with 552 unchanged application tests, actual Rust 1.85, docs, dependency policy, package dry run and offline links.
  • The existing anonymous security UI labels the native contact as private. The chooser itself redirects to sign-in, so authenticated UI verification remains pending. No issue or report was submitted.

PR #101/#102 and the obsolete CodeQL comparison decision remain separate. No settings, analysis deletion, publication or branch cleanup.

Keep vulnerability reports out of public issues and request sanitized
doctor output for ordinary bugs. Leave blank issues enabled.
@jsugg
jsugg merged commit 131be42 into main Oct 13, 2026
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant