You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: SECURITY.md
+18-17Lines changed: 18 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,7 @@ When building such applications developers should remember to follow good securi
11
11
*[**Defense in Depth**](https://en.wikipedia.org/wiki/Defense_in_depth_(computing)): No security technique is perfect. Fine-tuning and good chain design can reduce, but not eliminate, the odds that a Large Language Model (LLM) may make a mistake. It's best to combine multiple layered security approaches rather than relying on any single layer of defense to ensure security. For example: use both read-only permissions and sandboxing to ensure that LLMs are only able to access data that is explicitly meant for them to use.
12
12
13
13
Risks of not doing so include, but are not limited to:
14
+
14
15
* Data corruption or loss.
15
16
* Unauthorized access to confidential information.
16
17
* Compromised performance or availability of critical resources.
@@ -27,10 +28,10 @@ design and secure your applications.
27
28
28
29
## Reporting OSS Vulnerabilities
29
30
30
-
LangChain is partnered with [huntr by Protect AI](https://huntr.com/) to provide
31
-
a bounty program for our open source projects.
31
+
LangChain is partnered with [huntr by Protect AI](https://huntr.com/) to provide
32
+
a bounty program for our open source projects.
32
33
33
-
Please report security vulnerabilities associated with the LangChain
34
+
Please report security vulnerabilities associated with the LangChain
34
35
open source projects [here](https://huntr.com/bounties/disclose/?target=https%3A%2F%2Fgithub.com%2Flangchain-ai%2Flangchain&validSearch=true).
35
36
36
37
Before reporting a vulnerability, please review:
@@ -45,39 +46,39 @@ Before reporting a vulnerability, please review:
45
46
46
47
The following packages and repositories are eligible for bug bounties:
47
48
48
-
- langchain-core
49
-
- langchain (see exceptions)
50
-
- langchain-community (see exceptions)
51
-
- langgraph
52
-
- langserve
49
+
* langchain-core
50
+
* langchain (see exceptions)
51
+
* langchain-community (see exceptions)
52
+
* langgraph
53
+
* langserve
53
54
54
55
### Out of Scope Targets
55
56
56
57
All out of scope targets defined by huntr as well as:
57
58
58
-
-**langchain-experimental**: This repository is for experimental code and is not
59
+
***langchain-experimental**: This repository is for experimental code and is not
59
60
eligible for bug bounties (see [package warning](https://pypi.org/project/langchain-experimental/)), bug reports to it will be marked as interesting or waste of
60
61
time and published with no bounty attached.
61
-
-**tools**: Tools in either langchain or langchain-community are not eligible for bug
62
+
***tools**: Tools in either langchain or langchain-community are not eligible for bug
62
63
bounties. This includes the following directories
63
-
- libs/langchain/langchain/tools
64
-
- libs/community/langchain_community/tools
65
-
- Please review the [Best Practices](#best-practices)
64
+
* libs/langchain/langchain/tools
65
+
* libs/community/langchain_community/tools
66
+
* Please review the [Best Practices](#best-practices)
66
67
for more details, but generally tools interact with the real world. Developers are
67
68
expected to understand the security implications of their code and are responsible
68
69
for the security of their tools.
69
-
- Code documented with security notices. This will be decided on a case by
70
+
* Code documented with security notices. This will be decided on a case by
70
71
case basis, but likely will not be eligible for a bounty as the code is already
71
72
documented with guidelines for developers that should be followed for making their
72
73
application secure.
73
-
- Any LangSmith related repositories or APIs (see [Reporting LangSmith Vulnerabilities](#reporting-langsmith-vulnerabilities)).
74
+
* Any LangSmith related repositories or APIs (see [Reporting LangSmith Vulnerabilities](#reporting-langsmith-vulnerabilities)).
74
75
75
76
## Reporting LangSmith Vulnerabilities
76
77
77
78
Please report security vulnerabilities associated with LangSmith by email to `[email protected]`.
0 commit comments