indygreg / indygreg/PyOxidizer
Security Address
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 256
- PR merge metrics
- No merged PRs in 30d
Description
Hello!
I may have found a security issue in latest version of PyOxidizer. Following responsible disclosure, is there an email or other private channel where I could share the details?
Thank you
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, reproduction steps, or implementation scope. Review the PyOxidizer repository context and establish a private channel with the maintainers for the undisclosed security details; completion criteria cannot be determined from the public issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100