llms.txt
Compare with other sites' llms.txt files →# Skylos
> Open-source (Apache-2.0) static analysis CLI and pull request checks. Finds dead code, security issues, secrets, vulnerable dependencies, and quality regressions, and `skylos done` runs your tests and checks an AI agent's branch for shortcuts such as deleted or skipped tests. Runs locally without an account; Skylos Cloud adds shared scan history and pull request gates.
Last updated: 2026-10-27
## Canonical Facts
- License: Apache-2.0. Source: https://github.com/duriantaco/skylos
- Install: pip install skylos (Python 3.10+), with no C compiler needed. Dart support is an optional extra whose parser builds from source and needs a C compiler; the Docker image ghcr.io/duriantaco/skylos includes it. GitHub Action: duriantaco/skylos@1cdfa2be023b31fc99a4c5d11acdb725b7cae89a # v5.1.1.
- First run: skylos . (dead code) or skylos . -a (dead code, security, secrets, quality, and dependencies).
- Languages: Dead code, security and quality checks, deepest in Python, TypeScript/JavaScript, and Java; PHP and Dart get dead-code and security checks; Rust gets security checks and experimental dead code. Go dead-code and security checks use the native skylos-go engine, included in the PyPI wheels for Linux, macOS and Windows (x86_64 and arm64), the container image and the GitHub Action. C# support is partial, Kotlin is dead code only, C++ is limited to unused file-local functions, and Shell is security only. CI and deployment config: GitHub Actions, GitLab CI, Dockerfiles, Docker Compose, and more.
- Agent branches: skylos done --base main runs your tests (pytest automatically; other runners need a test_command setting) and fails when tests fail, tests were deleted, skipped, or weakened, test settings or CI test steps were loosened, code was written to pass particular tests, Skylos settings were edited, or secrets were added. Silenced lint or type checks, unresolved imports, and untested changed lines are reported as advice.
- Network: A normal scan sends no source code anywhere and calls no AI model. Dependency and import checks look up package names and versions in public registries and OSV. AI-assisted commands (skylos agent ...) are opt-in and use your own model key.
- MCP server: python -m skylos_mcp (included in pip install skylos). MCP scans don't use credits. analyze (dead code) works without a token, 5 calls a day; every other tool, except the three that read saved results, needs a free Skylos Cloud project token (SKYLOS_API_KEY). remediate is the only tool that costs credits: 10 per call.
- Pricing: The CLI, agent hooks and PR gate are free on any repository. Skylos Cloud has a Free plan (1 project, 10 stored scans, a pass/fail check on pull requests) and a Workspace plan for teams: $990 per workspace for 12 months with unlimited members, paid once, or 12 months with any credit pack from $9 (every pack covers up to 3 people). Nothing renews by itself; there are no seats, line-of-code meters or subscriptions.
- Support: https://github.com/duriantaco/skylos/issues
## Important URLs
- [Home](https://skylos.dev/): Product overview
- [Pricing](https://skylos.dev/pricing): Free CLI, Cloud Free and Workspace plans, credit costs
- [Docs](https://docs.skylos.dev/): Getting started, install, and product guides
- [Rules Reference](https://docs.skylos.dev/rules-reference): Rule catalog and scanner reference
- [Blog](https://skylos.dev/blog): Research, comparisons, and implementation guides
- [Compare](https://skylos.dev/compare): Side-by-side tool comparisons
- [Use Cases](https://skylos.dev/use-cases): Step-by-step workflows
- [VS Code](https://skylos.dev/vscode): VS Code extension page
- [Sitemap](https://skylos.dev/sitemap.xml): Crawlable page inventory
- [RSS](https://skylos.dev/blog/feed.xml): Blog feed
## Agent checks
- [How skylos done works](https://github.com/duriantaco/skylos/blob/main/docs/done-gate.md): each check, what blocks by default, and its limits
## Key Guides: Find and remove dead code in Python
- [How to Find Dead Code in Python (Unused Functions, Imports, Classes)](https://skylos.dev/use-cases/detect-dead-code-python): Run a whole-project scanner such as Vulture, deadcode or Skylos (skylos .), check code your framework calls before deleting, then fail CI on new dead code.
- [Deadcode vs Vulture vs Skylos: Python Dead Code Tools (2026)](https://skylos.dev/compare/deadcode-vs-vulture-vs-skylos): Vulture: maintained, MIT, needs framework config. deadcode: auto-fix, AGPL, last release 2024. Skylos: framework-aware, less config. Tested on Flask and Django.
- [Vulture False Positives: Tested Configs for Flask, Django and pytest](https://skylos.dev/blog/vulture-false-positives): Vulture flags routes, signals and fixtures as unused because the framework calls them, not your code. Tested pyproject.toml configs and whitelists fix it.
- [Does Ruff Detect Dead Code? What It Finds and What It Misses](https://skylos.dev/blog/ruff-dead-code): No. Ruff flags unused imports (F401) and local variables (F841) per file, with no rule for functions or classes nothing calls. Add Vulture, deadcode or Skylos.
- [Is There a Knip for Python? Unused Code, Files and Deps](https://skylos.dev/blog/knip-for-python): No single tool. Closest: chokkin (early, Knip-style). Otherwise Vulture or Skylos for unused code, deptry or FawltyDeps for dependencies. Tested 10 Oct 2026.
- [Django Dead Code: Find Unused Views, Helpers and Methods](https://skylos.dev/use-cases/django-dead-code): Find unused Django views: what Vulture, deadcode, Ruff, django-deadcode and Skylos found on one Django 5.2 app, and configs that fix false positives.
- [We Tested Dead-Code Detection by Sending Cleanup PRs to Mature OSS Repos](https://skylos.dev/blog/dead-code-detection-oss-cleanup-prs): We opened 26 dead-code cleanup PRs in 22 open-source projects; 10 merged into default branches across 9 projects. The rest were closed, reverted or are open.
- [Dead Code in Python Isn't Just Tech Debt — It's a Security Liability](https://skylos.dev/blog/dead-code-security-liability): Dead code is a security risk when it is still deployed: old routes nobody patches, unused dependencies with CVEs, stale credentials. How to find and remove it.
- [How to Find Dead Code in TypeScript: Unused Exports, Classes and Files](https://skylos.dev/blog/find-dead-code-typescript): tsc and ESLint catch unused locals and imports, but not unused exports, classes or files. We tested what each tool finds on the same TypeScript project.
## Key Guides: Check what AI coding agents change
- [Claude Code Hooks Examples for Security (Codex and Cursor Too)](https://skylos.dev/use-cases/ai-coding-agent-hooks): Copy-paste Claude Code hooks with real output: PreToolUse hooks that block fake package installs and secret reads, a PostToolUse edit check and a Stop hook.
- [Your AI Agent Just Tried to Install a Package That Doesn't Exist](https://skylos.dev/blog/stop-ai-agent-installing-fake-packages): Coding agents sometimes run pip or npm install on made-up or typo'd packages. One hook blocks the install and tells the agent why, before anything downloads.
- [Claude Code Stop Hook: Block "Done" Until Tests Pass (and Catch Deleted Tests)](https://skylos.dev/use-cases/claude-code-stop-hook): A Claude Code Stop hook runs when Claude tries to finish; print decision block and a reason to send it back. A tested script, and why it misses deleted tests.
- [AI Agent Says the Tests Pass? How to Verify AI-Generated Code Before Merge](https://skylos.dev/use-cases/verify-ai-agent-done): Run skylos done --base main: it re-runs the tests and fails if the agent deleted, skipped, emptied or special-cased tests, or loosened test settings or CI.
- [Testwashing: When Coding Agents Delete Tests to Pass CI](https://skylos.dev/blog/testwashing-coding-agents-delete-tests): Coding agents sometimes delete, skip or rig a failing test so CI goes green. We tried 9 versions: pytest passed every one. Here's what catches each.
- [Claude Code Security Review: /security-review, Hooks and a PR Check That Blocks](https://skylos.dev/use-cases/claude-code-security-review): /security-review and Claude Code Review are AI reviewers that don't block merges. Add .claude/settings.json hooks for each edit and a required PR check.
- [Cursor Security Scanner for Python: Hooks That Check Every Agent Edit](https://skylos.dev/use-cases/cursor-security-scanner): Scan Cursor agent edits as they happen with Cursor hooks: skylos agent install-hooks --cursor writes .cursor/hooks.json for reads, installs, edits and stop.
- [GitHub Copilot Code Review and Security: Gate Copilot Agent PRs in Python](https://skylos.dev/use-cases/github-copilot-security-review): Copilot's review comments, its approvals and its agent's CodeQL checks don't stop a removed auth check or a deleted test. Add a required status check that does.
- [AI Coding Agent Security Checklist: 12 Controls Before Agents Open PRs](https://skylos.dev/blog/ai-coding-agent-security-checklist): 12 controls to set before Claude Code, Cursor, Codex, Copilot or Devin open pull requests in production repos: trust, tools, dependencies and merge gates.
- ["All Tests Pass": What One Free Scan Found in an AI-Style Pull Request](https://skylos.dev/blog/free-code-scanner-ai-generated-code): pytest said 2 passed. One free scan found a deleted test, SQL and command injection, a leaked Stripe key, a made-up package and 14 advisories.
## Key Guides: SonarQube alternatives
- [SonarQube Alternative: Skylos vs SonarQube (2026)](https://skylos.dev/compare/sonarqube-vs-skylos): A free SonarQube alternative: Skylos checks every pull request on any branch, with no lines-of-code billing and checks for coding-agent mistakes.
- [SonarQube Community Build Pull Request Analysis (2026)](https://skylos.dev/blog/sonarqube-community-build-pull-request-analysis): SonarQube Community Build doesn't analyze pull requests or branches; Sonar starts both in Developer Edition. Here are your options, including free ones.
- [SonarQube Pricing (2026): Cloud, Server and Free Plans](https://skylos.dev/blog/sonarqube-pricing): How SonarQube is priced in 2026: lines-of-code billing, the free tier's 50k-line limit, Server editions per instance, and what happens at your limit.
- [A SonarQube-Style PR Gate in GitHub Actions, With No Server](https://skylos.dev/blog/sonarqube-alternative-github-actions): A pass/fail pull request check in GitHub Actions without a SonarQube server: one generated workflow, no account, no secrets, no lines-of-code limit.
- [Does SonarQube Detect Dead Code? What Its Rules Cover in 2026](https://skylos.dev/blog/does-sonarqube-detect-dead-code): SonarQube flags unused local or private code: variables, parameters, imports, private methods. We found no rule for unused public functions or exports.
## Key Guides: Compare static analysis tools
- [Best Python SAST Tools in 2026 Compared](https://skylos.dev/compare/best-python-sast-tools-2026): Semgrep, Bandit, CodeQL, Vulture and Skylos compared for Python: security scanning, dead code, CI setup, pricing and AI-generated code review in 2026.
- [Semgrep vs Skylos: Which Python SAST Tool Should You Use?](https://skylos.dev/compare/semgrep-vs-skylos): A detailed comparison of Semgrep and Skylos for Python static analysis. Where Semgrep has the edge, where Skylos is stronger, and which one fits your workflow.
- [Snyk vs Skylos: Python Security Comparison](https://skylos.dev/compare/snyk-vs-skylos): Compare Snyk and Skylos for Python security, including SCA, source analysis, containers, IaC, dead code, changed-code checks, deployment, and pricing.
- [Bandit vs Skylos: Which Python Security Scanner Should You Use?](https://skylos.dev/compare/bandit-vs-skylos): Bandit vs Skylos for Python security scanning: where Bandit is stronger, where Skylos adds taint, dead code and AI-code checks, and when to run both.
- [Bandit vs CodeQL vs Semgrep for Python Security Scanning](https://skylos.dev/compare/bandit-vs-codeql-vs-semgrep-python): Bandit, CodeQL and Semgrep all scan Python but fit different workflows. Compare setup, rule model, customization, GitHub fit, pricing and dead code.
- [GitHub Code Quality vs Skylos: Pricing, Dead Code, CI](https://skylos.dev/compare/github-code-quality-vs-skylos): GitHub Code Quality and Skylos compared: where each runs, what each costs, which Python dead code each finds, and when to use both together.
## Recent Comparison Pages
- [GitHub Code Quality vs Skylos: Pricing, Dead Code, CI](https://skylos.dev/compare/github-code-quality-vs-skylos): GitHub Code Quality and Skylos compared: where each runs, what each costs, which Python dead code each finds, and when to use both together.
- [Bandit vs CodeQL vs Semgrep for Python Security Scanning](https://skylos.dev/compare/bandit-vs-codeql-vs-semgrep-python): Bandit, CodeQL and Semgrep all scan Python but fit different workflows. Compare setup, rule model, customization, GitHub fit, pricing and dead code.
- [Bandit vs Skylos: Which Python Security Scanner Should You Use?](https://skylos.dev/compare/bandit-vs-skylos): Bandit vs Skylos for Python security scanning: where Bandit is stronger, where Skylos adds taint, dead code and AI-code checks, and when to run both.
- [Snyk vs Skylos: Python Security Comparison](https://skylos.dev/compare/snyk-vs-skylos): Compare Snyk and Skylos for Python security, including SCA, source analysis, containers, IaC, dead code, changed-code checks, deployment, and pricing.
- [SonarQube Alternative: Skylos vs SonarQube (2026)](https://skylos.dev/compare/sonarqube-vs-skylos): A free SonarQube alternative: Skylos checks every pull request on any branch, with no lines-of-code billing and checks for coding-agent mistakes.
- [Best Python SAST Tools in 2026 Compared](https://skylos.dev/compare/best-python-sast-tools-2026): Semgrep, Bandit, CodeQL, Vulture and Skylos compared for Python: security scanning, dead code, CI setup, pricing and AI-generated code review in 2026.
- [Deadcode vs Vulture vs Skylos: Python Dead Code Tools (2026)](https://skylos.dev/compare/deadcode-vs-vulture-vs-skylos): Vulture: maintained, MIT, needs framework config. deadcode: auto-fix, AGPL, last release 2024. Skylos: framework-aware, less config. Tested on Flask and Django.
- [Semgrep vs Skylos: Which Python SAST Tool Should You Use?](https://skylos.dev/compare/semgrep-vs-skylos): A detailed comparison of Semgrep and Skylos for Python static analysis. Where Semgrep has the edge, where Skylos is stronger, and which one fits your workflow.
## Recent Use Cases
- [Claude Code Stop Hook: Block "Done" Until Tests Pass (and Catch Deleted Tests)](https://skylos.dev/use-cases/claude-code-stop-hook): A Claude Code Stop hook runs when Claude tries to finish; print decision block and a reason to send it back. A tested script, and why it misses deleted tests.
- [Claude Code Hooks Examples for Security (Codex and Cursor Too)](https://skylos.dev/use-cases/ai-coding-agent-hooks): Copy-paste Claude Code hooks with real output: PreToolUse hooks that block fake package installs and secret reads, a PostToolUse edit check and a Stop hook.
- [Django Dead Code: Find Unused Views, Helpers and Methods](https://skylos.dev/use-cases/django-dead-code): Find unused Django views: what Vulture, deadcode, Ruff, django-deadcode and Skylos found on one Django 5.2 app, and configs that fix false positives.
- [AI Agent Says the Tests Pass? How to Verify AI-Generated Code Before Merge](https://skylos.dev/use-cases/verify-ai-agent-done): Run skylos done --base main: it re-runs the tests and fails if the agent deleted, skipped, emptied or special-cased tests, or loosened test settings or CI.
## Recent Blog Posts
- [Testwashing: When Coding Agents Delete Tests to Pass CI](https://skylos.dev/blog/testwashing-coding-agents-delete-tests): Coding agents sometimes delete, skip or rig a failing test so CI goes green. We tried 9 versions: pytest passed every one. Here's what catches each.
- [Does SonarQube Detect Dead Code? What Its Rules Cover in 2026](https://skylos.dev/blog/does-sonarqube-detect-dead-code): SonarQube flags unused local or private code: variables, parameters, imports, private methods. We found no rule for unused public functions or exports.
- [How to Find Dead Code in TypeScript: Unused Exports, Classes and Files](https://skylos.dev/blog/find-dead-code-typescript): tsc and ESLint catch unused locals and imports, but not unused exports, classes or files. We tested what each tool finds on the same TypeScript project.
- ["All Tests Pass": What One Free Scan Found in an AI-Style Pull Request](https://skylos.dev/blog/free-code-scanner-ai-generated-code): pytest said 2 passed. One free scan found a deleted test, SQL and command injection, a leaked Stripe key, a made-up package and 14 advisories.