Skip to content

Security: SylphxAI/lockdocs

SECURITY.md

Security

Reporting

Report vulnerabilities privately via GitHub Security Advisories on SylphxAI/lockdocs. Do not open public issues for sensitive reports.

Boundary

  • lockdocs reads lockfiles and installed package files. Its network use is: the embedding model, downloaded once from huggingface.co at a pinned revision and checked against a pinned SHA-256 (disable with LOCKDOCS_EMBED=0 or --offline); and, only with lockdocs fetch, --fetch or LOCKDOCS_FETCH=1, package archives from the registries below and docs files from api.github.com / raw.githubusercontent.com (a GITHUB_TOKEN in the environment is sent to api.github.com only). No project data is ever sent: requests name public packages and versions.
  • With fetching enabled it downloads only the exact package versions requested, from registry.npmjs.org, pypi.org / files.pythonhosted.org, static.crates.io and proxy.golang.org, over HTTPS. Archives are unpacked with path checks (no absolute paths, no ..), only documentation and source files are written, and downloads are capped at 64 MB.
  • Subprocesses: the system python3 once (to list its site-packages; disable with LOCKDOCS_NO_SYSTEM_PYTHON=1), and the claude CLI in lockdocs setup.
  • The MCP server speaks stdio only.
  • The cache lives in your OS cache directory (LOCKDOCS_CACHE overrides it) and holds extracted docs and symbols of your dependencies.

There aren't any published security advisories