We provide security updates for the following versions:

If you are using an older version, we strongly recommend upgrading to the latest stable release.

This project uses multiple automated security tools:

• GitHub CodeQL – Static Application Security Testing (SAST)
• OWASP Dependency-Check – Known vulnerability detection in dependencies
• GitHub Dependency Review – Pull request dependency analysis
• Dependabot – Automated dependency updates

All scans are executed automatically in CI pipelines on every pull request and release build.

All official release artifacts of Aether Datafixers are cryptographically signed to guarantee integrity and authenticity.

• All release artifacts are GPG signed
• Signatures are generated during the release pipeline
• Each published artifact is accompanied by a corresponding .asc signature file
• Consumers can verify artifacts before usage

Example verification flow:

gpg --verify artifact.jar.asc artifact.jar

Unsigned or modified artifacts must not be trusted.

• A dedicated GPG key is used for automated GitHub releases and deployments
• Release signing keys are separate from personal developer keys
• Private key material is never committed to the repository
• Keys are stored securely using CI secret management

The signing process is fully automated and enforced during release builds.

If you discover a security vulnerability in Aether Datafixers, please report it privately.

• Email: security@splatgames.de
• GitHub Security Advisories:
  https://github.com/aether-framework/aether-datafixers/security/advisories/new
• GitHub Issues:
  Do not report security vulnerabilities in public issues.

1. Report the issue privately
2. Acknowledgment within 48 hours
3. Fix timeline provided within 7 days
4. Critical vulnerabilities (CVSS ≥ 9.0): patch within 72 hours
5. High severity (CVSS ≥ 7.0): patch within 14 days
6. Security advisory published after resolution

• Always use the latest stable version
• Verify GPG signatures of all downloaded artifacts
• Enable automated dependency updates
• Validate input data at system boundaries
• Use appropriate DynamicOps implementations for untrusted data
• Avoid sensitive data in logs
• Review the attached SBOM for dependency transparency

We follow a coordinated disclosure process:

1. Private disclosure
2. Fix development
3. Advisory preparation
4. Coordinated release
5. Public disclosure after a grace period

Security audits are welcome.

• Contact security@splatgames.de before starting
• Follow responsible disclosure practices
• Researchers may be credited with permission

For encrypted communication and release verification:

• Key Purpose: Release artifact signing
• Key ID: 37B59B93DC756EE8
• Fingerprint: C6BE25BF2A4639A67A491EBD37B59B93DC756EE8
• Accessable in repository: KEYS

Contact: security@splatgames.de

Thank you for helping keep Aether Datafixers secure.