{"id":24901076,"url":"https://github.com/umair9747/leakygpt","last_synced_at":"2026-05-03T04:39:00.237Z","repository":{"id":274302760,"uuid":"922470711","full_name":"umair9747/leakyGPT","owner":"umair9747","description":"The one-stop DLP browser extension to stop users from sharing sensitive information with chatGPT.","archived":false,"fork":false,"pushed_at":"2025-01-26T12:06:35.000Z","size":487,"stargazers_count":6,"open_issues_count":0,"forks_count":3,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-03-27T18:18:25.452Z","etag":null,"topics":["ai","artificial-intelligence","chatgpt","compliance","cybersecurity","data-leakage-prevention","dlp","gpt","llm","openai","openai-chatgpt","security","security-compliance"],"latest_commit_sha":null,"homepage":"","language":"JavaScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/umair9747.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2025-01-26T09:56:15.000Z","updated_at":"2025-02-16T19:23:06.000Z","dependencies_parsed_at":"2025-01-26T13:32:18.343Z","dependency_job_id":null,"html_url":"https://github.com/umair9747/leakyGPT","commit_stats":null,"previous_names":["umair9747/leakygpt"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/umair9747%2FleakyGPT","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/umair9747%2FleakyGPT/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/umair9747%2FleakyGPT/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/umair9747%2FleakyGPT/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/umair9747","download_url":"https://codeload.github.com/umair9747/leakyGPT/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":245898319,"owners_count":20690466,"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":["ai","artificial-intelligence","chatgpt","compliance","cybersecurity","data-leakage-prevention","dlp","gpt","llm","openai","openai-chatgpt","security","security-compliance"],"created_at":"2025-02-01T21:14:59.438Z","updated_at":"2026-05-03T04:39:00.192Z","avatar_url":"https://github.com/umair9747.png","language":"JavaScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003ch1 align=\"center\"\u003eleakyGPT 🕸️\u003c/h1\u003e\n\u003cp align=\"center\"\u003e\n\u003cimg src=\"banner.png\" height=\"350px\" width=\"500px\"\u003e\n\u003c/p\u003e\n\u003cp align=\"center\"\u003e\u003cb\u003eThe one-stop browser-based DLP extension to stop users from sharing sensitive information with chatGPT.\u003c/b\u003e\u003c/p\u003e\n\u003cbr\u003e\n\n## Description:\nSince OpenAI does \u003ca href=\"https://help.openai.com/en/articles/5722486-how-your-data-is-used-to-improve-model-performance\"\u003eadmits\u003c/a\u003e that they can use our data to train their models, the looming threat of secret leakge as part of user prompts had to be addressed. While OpenAI does take steps to reduce the amount of personal information going into their training datasets, no individual or organization would want their secret keys or tokens to be a part of the training data. This is a major issue for companies whose teams largely depend on ChatGPT for their day-to-day work and could be passing sensitive data as part of their prompts.\n\nIntroducing leakyGPT, a browser-based DLP extension that looks for any secret exposures (with the help of our \u003ca href=\"./regexes.json\"\u003esignatures\u003c/a\u003e) within user prompts before they are submitted to chatGPT. The user can decide whether to prevent the prompt from being submitted or continue with it, thus helping prevent secrets from accidentally being trained in the datasets.\n\n## Why Is the Extension Not on Chrome Web Store?\nThe extension uses Manifest version 2 which is deprecated and hence Chrome is no longer accepting such submissions to the chrome web store. While the version is deprecated, it should still work fine on the latest versions of Chrome as long as they continue to support it. In the long run, I plan on rewriting the code to make it compatible to Manifest version 3 and then launch it over Chrome Web Store.\n\n## Does It Log Any Data?\nNo data is logged in any step or process of this extension making it completely safe for personal or enterprise use. Which also makes me want to state it here that the extension is completely free of cost and will not have any subscription involved for the time being.\n\n## How to Install?\nSimply clone or download the repository and then head over to `chrome://extensions/` and click on \"Load unpacked\" button. After that, just choose the directory containing the source code / project and it should now be imported onto your browser. \n\n## How to Use?\nNo additional steps are required after the installation. Just head over to chatGPT and use it like you always do. In case it detects any exposures it will inform you through a dialog box.\n\n## How to Disable/Uninstall?\nIf you head to `chrome://extensions/` you can either click on \"Remove\" button to uninstall the extension or click on \"Details\" button and toggle `off` the extension in case you would like to disable it.\n\n## How to modify/add custom keyword/regex detection?\nOpen the `regexes.json` file present in the repo folder which you earlier downloaded or cloned, add up new signatures or modify existing one and then head to `chrome://extensions/` to finally click the reload button next to the toggle one.\n\n\u003ch2\u003e Let's Connect! \u003c/h2\u003e\nIf you have any questions or feedback about Genzai or just want to connect with me, feel free to reach out via \u003ca href=\"https://x.com/0x9747\"\u003eTwitter/X\u003c/a\u003e, \u003ca href=\"https://in.linkedin.com/in/umair-nehri-49699317a\"\u003eLinkedIn\u003c/a\u003e or \u003ca href=\"mailto:umairnehri9747@gmail.com\"\u003eEmail\u003c/a\u003e.\n\u003c/div\u003e\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fumair9747%2Fleakygpt","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fumair9747%2Fleakygpt","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fumair9747%2Fleakygpt/lists"}