What is the preferred process for reporting a security vulnerability in pm2?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
What is the preferred process for reporting a security vulnerability in pm2?
I emailed the same question to contact@keymetrics.io a week ago and haven't seen a reply.
Contributor guide
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
No file, test, or entry point is named. Review the repository's current security-reporting guidance and the unanswered contact@keymetrics.io inquiry first. Done would mean establishing or documenting a clear, maintained process for reporting pm2 vulnerabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100