Security maintenance covers the current paper-production tooling and workflows on main. Older stored manuscripts and calculation files are preserved as research records; they are not separately maintained software releases.

Use GitHub private vulnerability reporting or email adam@adamgetchell.org. Include the affected revision, reproduction steps, and expected impact. Report security vulnerabilities privately rather than in a public issue.

Relevant reports include compromised build inputs, unsafe handling of untrusted LaTeX or filenames, credential exposure, vulnerable dependencies, and workflow permission or publication defects. Scientific critique and manuscript corrections can use ordinary issues when they contain no sensitive information.

The maintainer will triage reports as availability allows and coordinate fixes and any necessary disclosure. Publication delivery is tracked separately in issue #2.