Using and training an LLM and/or ML model to identify data leakage and code anomalies 🤖

オープン
  • 何か問題がありますか？
#561 コメント 4 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@vaibssingh がすでに取り組んでいます。

2024年7月29日 から。

評価

この issue はまだ評価されていません。

説明

citi-hackathon question

LLMs, Machine Learning and Data Leakage Prevention

LLMs appear to be very capable (with caveats, no doubt) at detecting anomalous text, data and information used in some given context. A couple of experiments will quickly prove their capability. With the help of Perplexity AI, I have run the following experiments:

Experiment 1, Data Exfiltration

Inserting a price property into a package.json and asking Perplexity AI to identify the anomalous property.

Screenshot 2024-05-11 at 09 25 19
Experiment 2, Treasure Island

Inserting a phrase about social media in the second paragraph of the first chapter of Treasure Island by Robert Louis Stevenson.

Input 🔽
Screenshot 2024-05-11 at 09 32 03
Output 📤
Screenshot 2024-05-11 at 09 32 14
Models of usage ♻️

A couple of "finger in the air" models for implementation:

  1. Converting company policies around code creation and open source into prompts asked of the code before it is accepted for push or publication; results shared as informational
  2. Implementing a prompt for internal agents to ask further or more expansive questions of the code set; different coding ecosystems and languages introduce nuances that people can bring expertise too
  3. Use the basis of inputs and outputs, as confirmed with human support, to re-train and strengthen a given model
Feedback 💬

On reflection, this seems extremely useful for our mission of reducing enterprise data leakage for code creation and contribution. Whilst I am not per se advocating for full automation with an LLM, it could certainly be additive and informational when a given agent is assessing potential leakage in a given snippet of code or an entire codebase.

I'd be keen to hear the opinion of others and reflections of whether this is "just another AI idea (JAAII)" or something that is practical, implementable and helpful to us. I am aware that accuracy of some model is no doubt a looming issue that would need to be addressed. Hallucinations and false positives come with a high risk in this scenario (i.e. leakage) - I would be curious to hear any feedback on how this could be mitigated or addressed.

If you think you can present experiments that better demonstrate the power of an LLM in detecting and preventing data or IP leakage in code, feel free to share ❤️

主要言語
TypeScript
スター
263
フォーク
185
平均マージ
2日 15時間
マージ済み PR（30日）
39

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

finos/git-proxy のほかの issue

finos/git-proxy の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。