{"id":18552955,"url":"https://github.com/cryptosense/w3c-crypto-inspector","last_synced_at":"2025-11-09T03:03:53.594Z","repository":{"id":19364868,"uuid":"22604885","full_name":"cryptosense/w3c-crypto-inspector","owner":"cryptosense","description":"Chromium extension to inspect W3C Web Cryptography API calls and keys.","archived":false,"fork":false,"pushed_at":"2014-08-29T10:08:15.000Z","size":184,"stargazers_count":14,"open_issues_count":1,"forks_count":1,"subscribers_count":3,"default_branch":"master","last_synced_at":"2025-03-24T13:21:19.073Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"bsd-2-clause","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/cryptosense.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.md","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2014-08-04T13:23:44.000Z","updated_at":"2019-08-16T00:50:42.000Z","dependencies_parsed_at":"2022-09-13T10:40:52.657Z","dependency_job_id":null,"html_url":"https://github.com/cryptosense/w3c-crypto-inspector","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cryptosense%2Fw3c-crypto-inspector","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cryptosense%2Fw3c-crypto-inspector/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cryptosense%2Fw3c-crypto-inspector/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/cryptosense%2Fw3c-crypto-inspector/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/cryptosense","download_url":"https://codeload.github.com/cryptosense/w3c-crypto-inspector/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248123805,"owners_count":21051537,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-06T21:15:37.922Z","updated_at":"2025-11-09T03:03:53.548Z","avatar_url":"https://github.com/cryptosense.png","language":"JavaScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"#Cryptosense Key Inspector\n(C) Cryptosense 2014, see LICENSE.md\n\nA very simple chromium extension that traces calls to the W3C WebCrypto API. Both keys and calls can be exported in JSON format.\n\nSend feedback, bugs, comments, questions to webcrypto@cryptosense.com\n\n\n##Absence from Chrome Web Store\n\nWe're releasing this little extension in source code only to find out\nif it corresponds to the expectations of the community.  We will\nsubmit this extension to the Chrome Web store by ourselves when it is\nready. Please don't do it yourself.\n\nVersions for other browsers will follow as their implementations of\nthe API become available.\n\n##Usage\n\nTo install, go to \"chrome://extensions\" and choose\n\"Load unpacked extension...\", then select the extension directory.\n\nThe extension will run on each page you visit. You can see the current\nkeys by clicking the extension icon. A green key icon indicates a key\nusing a secure algorithm (in the sense of \"secure for future use\" at\nhttp://cryptosense.com/choice-of-algorithms-in-the-w3c-crypto-api/ ),\nan orange key means an algorithm secure for the moment but not\napproved for future use, and a red keys means an algorithm considered\ninsecure. Attention - this does not mean that the key value itself is\nsecure, or that the applications use of the algroithm is secure,\netc. etc.\n\nYou can download the JSON of current keys or the JSON of all function\ncalls by clicking the corresponding button.\n\n##Extra notes and issues\n\nThis extension adds some data in the key to allow them to be more\neasily identified (ID, usage and creation date).\n\nIt is possible that the overwrite of the standard W3C webcrypto API\nfunctions breaks the promise mechanism somewhat.\n\nOccasionally, if a script calls generate key immediately this\nexecutes before the function has been redefined so it escapes tracing.\n\nWhen viewing keys, the popup doesn't resize itself when extending a\nnode and reducing it afterwards. If you know how to do this, tell us,\nor submit a patch!\n\n##How it works\n\n* popup.js : The page displayed when clicking the extension icon, it\nmanages the displaying and downloading of the differents required\ndatas.\n\n* contentscript.js : Code that runs with each page but not in the same\nenvironment.  It injects hooker.js on each page and receives the\nmessages from the popup.\n\n* hooker.js : The code that polyfills the standard W3C WebCrypto API\nfunctions.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcryptosense%2Fw3c-crypto-inspector","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcryptosense%2Fw3c-crypto-inspector","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcryptosense%2Fw3c-crypto-inspector/lists"}