-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Add a security policy for arrow-rs #9727
Copy link
Copy link
Closed
Labels
arrowChanges to the arrow crateChanges to the arrow cratearrow-avroarrow-avro cratearrow-avro cratearrow-flightChanges to the arrow-flight crateChanges to the arrow-flight cratedocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementAny new improvement worthy of a entry in the changelogAny new improvement worthy of a entry in the changelogparquetChanges to the parquet crateChanges to the parquet crateparquet-derive
Metadata
Metadata
Assignees
Labels
arrowChanges to the arrow crateChanges to the arrow cratearrow-avroarrow-avro cratearrow-avro cratearrow-flightChanges to the arrow-flight crateChanges to the arrow-flight cratedocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementAny new improvement worthy of a entry in the changelogAny new improvement worthy of a entry in the changelogparquetChanges to the parquet crateChanges to the parquet crateparquet-derive
Type
Fields
Give feedbackNo fields configured for issues without a type.
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Other arrow subprojects (C++ in particular) has been beset recently by a deluge of low quality bug reports masquerading as security problems.
To reduce this flow and make it easier to direct people to the appropriate bug vs feature venue, we should document our securty posture better
Describe the solution you'd like
Document security posture
Describe alternatives you've considered
Additional context
Related arrow issues