Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
langchain-benchmarks
Advanced tools
A package to help benchmark various LLM related tasks.
The benchmarks are organized by end-to-end use cases, and utilize LangSmith heavily.
We have several goals in open sourcing this:
Read some of the articles about benchmarking results on our blog.
See tool usage docs to recreate!
Explore Agent Traces on LangSmith:
To install the packages, run the following command:
pip install -U langchain-benchmarks
All the benchmarks come with an associated benchmark dataset stored in LangSmith. To take advantage of the eval and debugging experience, sign up, and set your API key in your environment:
export LANGCHAIN_API_KEY=ls-...
The package is located within langchain_benchmarks. Check out the docs for information on how to get starte.
The other directories are legacy and may be moved in the future.
Below are archived benchmarks that require cloning this repo to run.
FAQs
🦜💪 Flex those feathers!
We found that langchain-benchmarks demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.