Skip to content

Conversation

@Splatcrafter
Copy link
Member

Summary

This PR adds security documentation for safe guidance through configuring input parsers for JSON, YAML and all other formats.

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Refactoring
  • Documentation
  • Build / CI

Related Issues

Closes #40 - [Feature]: Security Documentation for Untrusted Data

Changes

  • added documentation for security configuration

Verification

  • Unit tests added/updated
  • Existing tests pass
  • Manual verification performed (if applicable)

Breaking Changes

No breaking changes were made in this PR.

Checklist

  • Code follows project conventions
  • Public APIs are documented
  • Tests cover new behavior
  • No unnecessary dependencies added

… YAML, including examples and detailed mitigations against XXE and RCE vulnerabilities. Introduce new security documentation sections for serialization formats and updated threat model.
@Splatcrafter Splatcrafter requested a review from a team as a code owner January 31, 2026 21:18
@Splatcrafter Splatcrafter requested a review from a team January 31, 2026 21:18
@Splatcrafter Splatcrafter self-assigned this Jan 31, 2026
@Splatcrafter Splatcrafter added the documentation Improvements or additions to documentation label Jan 31, 2026
@github-actions
Copy link

⚠️ Deprecation Warning: The deny-licenses option is deprecated for possible removal in the next major release. For more information, see issue 997.

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@Splatcrafter Splatcrafter merged commit 3adce06 into develop Jan 31, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant