Security/Reviews/ModuleLoader: Difference between revisions

Jump to navigation Jump to search
no edit summary
(Created page with "{{SecReviewInfo |SecReview name=Module Loader }} {{SecReview}} {{SecReviewActionStatus |SecReview action item status=None }}")
 
No edit summary
 
Line 1: Line 1:
{{SecReviewInfo
{{SecReviewInfo
|SecReview name=Module Loader
|SecReview name=Module Loader
|SecReview target=<bugzilla>
{
"id":"756491,743359"
}
</bugzilla>
}}
{{SecReview
|SecReview feature goal=* we are using a module loader that is similiar to what is used by Node.js
** long term goal is to land SDK to Firefox
** landing this first, then api then sdk
* this would allow jetpack items to use the module loader (currently shipped with each add-on)
** Loader instance won't be shared across add-on instances just a code to create loaders
** Blacklists Components from sandboxes we create
https://bugzilla.mozilla.org/show_bug.cgi?id=747434
** We will be able to visualize capabilities graph for add-on reviewers like this:
http://bl.ocks.org/2582184
|SecReview alt solutions=* keep it as is
|SecReview solution chosen=* better for performance and smaller add-ons
|SecReview threats considered=* uses SubscriptLoader() so remote modules will not be loaded.
}}
}}
{{SecReview}}
{{SecReviewActionStatus
{{SecReviewActionStatus
|SecReview action item status=None
|SecReview action item status=None
}}
}}
canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,776

edits

Navigation menu