mathisonian / mathisonian/requirify
Consider inlining the script in the browser extension
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 95
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Currently there is no guarantee that the extension will continue to work the way it does today. The script at https://s3.amazonaws.com/s3.mathisonian.com/javascripts/requirify-browser.js could potentially be changed to do something malicious instead.
Rather than loading https://s3.amazonaws.com/s3.mathisonian.com/javascripts/requirify-browser.js off your server it would be more secure to inline it in the browser extension. This would also save you some bandwidth.
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 locating the browser extension entry point that loads https://s3.amazonaws.com/s3.mathisonian.com/javascripts/requirify-browser.js and inspect how the script is packaged. Done means the extension no longer depends on that remote script, while its current behavior continues to work and no longer carries the stated security risk.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100