UCOSP-winter-2018_TrackingTechnologies/schema.md

• call_stack:
  • Type: String
  • Description: The call stack at the point when the function is called. The output is in the format: (function_name)(@)(javascript_source_file)(:)(line_number)(column_number)(new_line_character)
  • Example:

  jQuery.cookie@https://cdn.livechatinc.com/js/embedded.20171215135707.js:5:8393\nStore</s.get@https://cdn.livechatinc.com/js/embedded.20171215135707.js:8:3323\nStore</</s[p]@https://cdn.livechatinc.com/js/embedded.20171215135707.js:8:3746\nWindowsCommunicator.prototype.startCheckingForMainWindow/e<@https://cdn.livechatinc.com/js/embedded.20171215135707.js:10:11730
  

• crawl_id:
  • Type: Integer
  • Description: Crawl_id appears to be the value 1 for all json files. It is possible this field was not used when generating the data using the crawler.
  • Example: 1
• func_name:
  • Type: String
  • Description: The name of the javascript function. Due to obfuscation the functions are often nonsensical and thus can be thought of as tokens. Anonymous functions will not have a name and the value will be an empty string.
  • Examples:

  ""
  a<4k
  getName
  

• in_iframe:
  • Type: boolean
  • Description: in_iframe is a boolean that indicates that the javascript code was run inside of an iframe. This is new functionality that was added ontop of the origional OpenWPM repository.
• location:
  • Type: string
  • Description: The url of the file that was being crawled to generate the json file. For iFrame resources, the location will be different that the parent url where the iFrame was encountered. For example, if Parent.html contains iFrame.html, iFrame.html is added inside an