Skip to content

Commit eafab52

Browse files
authored
refactor: markdownlint SECURITY.md (#32258)
1 parent efdfa00 commit eafab52

File tree

1 file changed

+18
-17
lines changed

1 file changed

+18
-17
lines changed

SECURITY.md

Lines changed: 18 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,7 @@ When building such applications developers should remember to follow good securi
1111
* [**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.
1212

1313
Risks of not doing so include, but are not limited to:
14+
1415
* Data corruption or loss.
1516
* Unauthorized access to confidential information.
1617
* Compromised performance or availability of critical resources.
@@ -27,10 +28,10 @@ design and secure your applications.
2728

2829
## Reporting OSS Vulnerabilities
2930

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.
3233

33-
Please report security vulnerabilities associated with the LangChain
34+
Please report security vulnerabilities associated with the LangChain
3435
open source projects [here](https://huntr.com/bounties/disclose/?target=https%3A%2F%2Fgithub.com%2Flangchain-ai%2Flangchain&validSearch=true).
3536

3637
Before reporting a vulnerability, please review:
@@ -45,39 +46,39 @@ Before reporting a vulnerability, please review:
4546

4647
The following packages and repositories are eligible for bug bounties:
4748

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
5354

5455
### Out of Scope Targets
5556

5657
All out of scope targets defined by huntr as well as:
5758

58-
- **langchain-experimental**: This repository is for experimental code and is not
59+
* **langchain-experimental**: This repository is for experimental code and is not
5960
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
6061
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
6263
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)
6667
for more details, but generally tools interact with the real world. Developers are
6768
expected to understand the security implications of their code and are responsible
6869
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
7071
case basis, but likely will not be eligible for a bounty as the code is already
7172
documented with guidelines for developers that should be followed for making their
7273
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)).
7475

7576
## Reporting LangSmith Vulnerabilities
7677

7778
Please report security vulnerabilities associated with LangSmith by email to `[email protected]`.
7879

79-
- LangSmith site: https://smith.langchain.com
80-
- SDK client: https://github.com/langchain-ai/langsmith-sdk
80+
* LangSmith site: <https://smith.langchain.com>
81+
* SDK client: <https://github.com/langchain-ai/langsmith-sdk>
8182

8283
### Other Security Concerns
8384

0 commit comments

Comments
 (0)