Guidance on Electron Vulnerabilities
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.9k
- Forks
- 279
- PR merge metrics
- No merged PRs in 30d
Description
electron^36, used by @vue/devtools-electron, has 20+ vulnerabilities as of now, 7 high. I realize although this PR updates that dependency https://github.com/vuejs/devtools/pull/1083, upgrading electron major versions would likely be considered a breaking change in this package and possibly alot more work than a simply dependency update to ensure no functionality is broken with this devtools package.
What is the general guidance on vulnerabilities as it relates to electron? is it not prioritized because this is a standalone devtools app for your local computer? Or is the goal to eventually merge that PR and release a new major version for @vue/devtools-electron?
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
Start by reviewing the @vue/devtools-electron package and linked pull request #1083, then check how Electron dependencies and release guidance are handled in this repository. Done means recording a clear decision about vulnerability handling and whether the dependency update requires a new major release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, typescript
- Domain
- desktop, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100