langroid
11 published advisories; version 0.65.5 or later fixes all of them.
- Registry
- PyPI
- Advisories
- 11
- Latest fix
- 0.65.5
- Exploited in the wild
- None listed
Check your projects
shieldpi agent-config checks agent and MCP packages from npm and PyPI, not langroid. Any scanner that reads the OSV database finds it in your lockfiles, for example Google's open-source OSV-Scanner.
osv-scanner scan source -r .Or check a lockfile against ShieldMap in your browser.
0 of the last 10 releases of langroid were published with build provenance: a signed record of the repository and commit each was built from, which the registry checks before it accepts the release.
- 0.69.24
- 0.69.23
- 0.69.22
- 0.69.21
- 0.69.20
- 0.69.19
- 0.69.18
- 0.69.17
- 0.69.16
- 0.69.15
Green: published with provenance. Grey: without.
OpenSSF Scorecard has not scored this package's repository.
Provenance from deps.dev (CC BY 4.0); Scorecard from OpenSSF (CDLA-Permissive-2.0). As of 2026-11-18.
Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].