Skill Scanner Files

Skill Scanner 2.3.1

This release keeps the hijacked litellm 1.107.0 out of skill-scanner installs. If you install skill-scanner with pip, upgrade.

Security

• Exclude litellm 1.107.0 from the dependency range, which is now litellm>=1.89.7,<2,!=1.107.0. That PyPI release was hijacked: every platform wheel drops cook.pth and sitecustomize.py into site-packages, and on every Python start (no import litellm needed) they collect environment variables, SSH, GPG and TLS keys, cloud and Kubernetes credentials, browser data and AI-assistant tokens and send them to an attacker host (JFrog write-up, BerriAI/litellm#47826). The 2.3.0 range allowed it. (#276)

PyPI has removed 1.107.0, but mirrors and caches (Artifactory, pip caches) may still serve it. If pip show litellm reports 1.107.0 in an environment where skill-scanner was installed, treat that host as compromised and rotate its credentials; the JFrog post lists the IOCs. The Homebrew formula pins litellm 1.105.1 by hash and was not affected, and uv.lock stays on 1.89.7.

Changes

• Ship the taxonomy's definition of every objective, technique and sub-technique in the bundled snapshot, readable through get_aitech_definition() and get_aisubtech_definition(), plus a generated taxonomy reference covering all 19 objectives, 44 techniques and 130 sub-techniques. threats.py keeps one full table per analyzer, AI Defense labels included, each entry with a description. (#272)
• Replace retired LLM provider defaults: --llm-provider openrouter now resolves to openrouter/openai/gpt-5.6-sol (OpenAI shuts down gpt-4 on 2026-10-23), and gcp-vertex to vertex_ai/gemini-3.8-flash (gemini-1.5-pro is retired on Vertex AI). (#275)

Behavior notes

Findings are unchanged. scan_metadata.taxonomy.snapshot_sha256 changes from 3df746f0… to 413e8ce9… because the snapshot now carries definitions, so update anything that pins it. OpenRouter and Vertex users who relied on the default model get the new one; set SKILL_SCANNER_LLM_MODEL to keep a specific model.

The hash-pinned requirements.txt attached to this release locks certifi 2026.4.22, which pip-audit started flagging this week (PYSEC-2026-4320, fixed in 2026.10.19). A plain pip install resolves the newer certifi; the lock update follows in the next release.

Validation

None of the changes since 2.3.0 change what the static rules detect: [#272] adds definitions without changing finding output and passed the base-versus-head detection comparison, [#275] changes two LLM provider default model names, and [#276] changes a dependency specifier. On c615acb the local release gate passed pre-commit on all files and 6,062 tests (31 skipped, 1 xfailed), and the eval benchmark scored all 29 skills at 100% precision and recall.