MaartenGr / MaartenGr/BERTopic

How to report a security issue responsibly?

Open
#2,264 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
7.8k
Forks
920
Avg merge
22h 24m
Merged PRs (30d)
5

Description

### Have you searched existing issues? 🔎

- [X] I have searched and found no existing issues

### Desribe the bug

I have just found a potential security issue in the repo and want to know how I can report it to your team privately, thanks!

### Reproduction

_No response_

### BERTopic Version

Latest

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no file, test, or entry point. Start by checking the repository's existing guidance for private security reports and determine what reporting route should be documented; done means contributors can find clear instructions for reporting a security issue privately.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.