Skip to content

Conversation

@opwvhk
Copy link
Contributor

What is the purpose of the change

Describe when using Avro is secure. This is necessary documentation, given the world-wide shift to extend product liability to "digital elements" (this includes software). Users of the Avro library will want to know how using Avro affects the security of their product.

See AVRO-4145.

Verifying this change

This change only adds documentation. No code has been changed.

Documentation

  • Does this pull request introduce a new feature? (yes / no)
  • If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Describe when using Avro is secure. This is necessary documentation, given the world-wide shift to extend product liability to "digital elements" (this includes software).
@opwvhkopwvhk merged commit 907bc85 into apache:mainJun 27, 2025
2 checks passed
@opwvhkopwvhk deleted the AVRO-4145-Document-Security-Model branch June 27, 2025 22:10
opwvhk added a commit to opwvhk/avro that referenced this pull request Sep 5, 2025
Describe when using Avro is secure. This is necessary documentation, given the world-wide shift to extend product liability to "digital elements" (this includes software).
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@opwvhk@martin-g@KalleOlaviNiemitalo