
Document and Reverse Engineer Chrome Extension
- or -
Post a project like this$$
- Posted:
- Proposals: 1
- Remote
- #1438991
- Expired
Description
Experience Level: Intermediate
General information for the business: Document and Reverse Engineer Chrome Extension
Description of requirements/functionality: The goal is to document, and reverse engineer/deconstruct this chrome extension and document exactly how it works so that a similar one can be created. I am looking for a proposal price and deadline for this project. If you do a good job on this project, there will be a second project to extract and host a modified version of this extension.
Please propose
- Project price
- Project duration
- Please show samples of your documentation
The project deliverable are listed below.
The chrome extension is available here:
- https://chrome.google.com/webstore/detail/rapportive/hihakjfhbmlmjdnnhegiciffjplmdhin?hl=en
Please look at the scope of this project closely and it will probably be given to a person that can give sample examples of the documentation you will create for this project.
Project Deliverables:
1 > Document and catalogue every script that is dynamically(or statically) called or loaded by the extension.
2 > Document and catalogue every api that is dynamically(or statically) called or loaded by the extension.
- Please include an example url call for each api called and response text
3 > Download the source code for every dynamically(or statically) called/loaded script, assets (images) and html or other files. If there is a script used to render, process or otherwise make the extension work missing it's incomplete.
4 > Sequence Diagrams
There should be a sequence diagram for each script, showing if it calls a webservice (which webservice and samples of the data sent), other extension script or dynamically loaded javascript on the gmail page.
Use http://sequencediagram.org/ for the sequence diagrams. (If you want to use another solution please propose and get approval first)
Provide diagrams with (source and miage)
- rapportive.js
- scriptTagContext.js
- high level - how everything gets called from one another.
- One for every Documented and catalogued script (found in requirement(1))
5 > Highlevel Architecture Diagram
- As a Gliffy Diagram - https://www.gliffy.com/ or https://chrome.google.com/webstore/detail/gliffy-diagrams/bhmicilclplefnflapjmnngmkkkkpfad?hl=en
6 > Document every function
For every function you should document the following
* What the function does - It inserts code to detect email addresses (this is a high level example, it should be much more detailed than this)
* How it works - e.g. it parses some json and then supplies x parameters to a webservice to update a webview (this is a high level example, it should be much more detailed than this). It should also explain what the functions do. This can be done by adding inline comments to the downloaded code.
* What is the function signature - e.g. what are the parameters that the function accepts.
* Example calls of each function
- exact parameter values for each function call
- exact return values for each function call
- rapportive.js
- scriptTagContext.js
- One for every Documented and catalogued script (found in requirement(1))
7 > High level documentation on how the extension works.
- How does it work when logged in
- How does it work when a user isn't logged in
8 > Document the Manifest and how each section affects the plugin.
Go into detail about content_security_policy and what each subsection does.
- "update_url": "https://clients2.google.com/service/update2/crx",
- "manifest_version": 2,
- "name": "Rapportive",
- "description": "Shows LinkedIn profiles in your Gmail",
- "version": "1.4.3",
- "icons"
- "content_scripts": [{
- "exclude_globs": [],
- "include_globs": [],
- "js"
- "matches"
- "permissions"
- "content_security_policy"
The extension is available here:
- https://chrome.google.com/webstore/detail/rapportive/hihakjfhbmlmjdnnhegiciffjplmdhin?hl=en
The extension can be downloaded easily here:
- http://chrome-extension-downloader.com/
Learn how to debug chrome extensions
- https://developer.chrome.com/extensions/tut_debugging
Specific technologies required: chrome extension, javascript
Extra notes:
Description of requirements/functionality: The goal is to document, and reverse engineer/deconstruct this chrome extension and document exactly how it works so that a similar one can be created. I am looking for a proposal price and deadline for this project. If you do a good job on this project, there will be a second project to extract and host a modified version of this extension.
Please propose
- Project price
- Project duration
- Please show samples of your documentation
The project deliverable are listed below.
The chrome extension is available here:
- https://chrome.google.com/webstore/detail/rapportive/hihakjfhbmlmjdnnhegiciffjplmdhin?hl=en
Please look at the scope of this project closely and it will probably be given to a person that can give sample examples of the documentation you will create for this project.
Project Deliverables:
1 > Document and catalogue every script that is dynamically(or statically) called or loaded by the extension.
2 > Document and catalogue every api that is dynamically(or statically) called or loaded by the extension.
- Please include an example url call for each api called and response text
3 > Download the source code for every dynamically(or statically) called/loaded script, assets (images) and html or other files. If there is a script used to render, process or otherwise make the extension work missing it's incomplete.
4 > Sequence Diagrams
There should be a sequence diagram for each script, showing if it calls a webservice (which webservice and samples of the data sent), other extension script or dynamically loaded javascript on the gmail page.
Use http://sequencediagram.org/ for the sequence diagrams. (If you want to use another solution please propose and get approval first)
Provide diagrams with (source and miage)
- rapportive.js
- scriptTagContext.js
- high level - how everything gets called from one another.
- One for every Documented and catalogued script (found in requirement(1))
5 > Highlevel Architecture Diagram
- As a Gliffy Diagram - https://www.gliffy.com/ or https://chrome.google.com/webstore/detail/gliffy-diagrams/bhmicilclplefnflapjmnngmkkkkpfad?hl=en
6 > Document every function
For every function you should document the following
* What the function does - It inserts code to detect email addresses (this is a high level example, it should be much more detailed than this)
* How it works - e.g. it parses some json and then supplies x parameters to a webservice to update a webview (this is a high level example, it should be much more detailed than this). It should also explain what the functions do. This can be done by adding inline comments to the downloaded code.
* What is the function signature - e.g. what are the parameters that the function accepts.
* Example calls of each function
- exact parameter values for each function call
- exact return values for each function call
- rapportive.js
- scriptTagContext.js
- One for every Documented and catalogued script (found in requirement(1))
7 > High level documentation on how the extension works.
- How does it work when logged in
- How does it work when a user isn't logged in
8 > Document the Manifest and how each section affects the plugin.
Go into detail about content_security_policy and what each subsection does.
- "update_url": "https://clients2.google.com/service/update2/crx",
- "manifest_version": 2,
- "name": "Rapportive",
- "description": "Shows LinkedIn profiles in your Gmail",
- "version": "1.4.3",
- "icons"
- "content_scripts": [{
- "exclude_globs": [],
- "include_globs": [],
- "js"
- "matches"
- "permissions"
- "content_security_policy"
The extension is available here:
- https://chrome.google.com/webstore/detail/rapportive/hihakjfhbmlmjdnnhegiciffjplmdhin?hl=en
The extension can be downloaded easily here:
- http://chrome-extension-downloader.com/
Learn how to debug chrome extensions
- https://developer.chrome.com/extensions/tut_debugging
Specific technologies required: chrome extension, javascript
Extra notes:

Steve M.
0% (0)Projects Completed
-
Freelancers worked with
-
Projects awarded
0%
Last project
25 Apr 2025
United States
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies