PAGES
← all tools
◆ AI Red Teaming & Testing

SkillSpector

v2.13.3 open-source

SkillSpector is a security scanner for AI agent skills that detects vulnerabilities, malicious patterns, and security risks before installation.

Summary

SkillSpector is an open-source, Apache-licensed command-line scanner that checks AI agent skills — the kind used by Claude Code, Codex CLI, and Gemini CLI — for vulnerabilities and malicious patterns before they're installed. It's built for teams building or vetting AI agent supply chains rather than for general application security work, running static analysis across 70 vulnerability patterns (prompt injectionprompt injectionAn attack where text the model reads, such as a web page, file or tool result, carries instructions that override the user's. It is the main security risk for agents with tools., data exfiltrationdata exfiltrationMoving data out of a system or organization without authorization. It can happen through network transfers, removable media or other channels., supply-chain issues, and more) with an optional LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code.-based semantic pass, and outputting terminal, JSON, Markdown, or SARIFSARIFStatic Analysis Results Interchange Format, a standard for sharing code-analysis findings, including locations and rule details. It lets scanners report results to a common review interface. reports for gating installs in CI. It underpins NVIDIA's Verified Skills pipeline, which scans and signs skills before they reach NVIDIA's public skills catalog. First committed in 2026, it already has 44 contributors and 61 releases in the past year, including one this week, so development is active.

SkillSpector is a security scanner for AI agent skills that detects vulnerabilities, malicious patterns, and security risks before installation.

How SkillSpector helps

Is this skill safe to install before it reaches an agent runtime?

runs 70 static vulnerability patterns across 17 categories (prompt injection, exfiltration, privilege escalation, supply chain, and more) plus an optional LLM semantic pass, and returns a 0-100 risk score with severity labels and recommendations

Did a scan actually finish, or did it fail quietly and report zero findings by default?

records an execution-completeness ledger with per-component coverage and out-of-scope notes, sets a top-level success flag, and exits with a distinct failure code so an incomplete or crashed scan can't be mistaken for a clean one

Does a skill pull in other skills that carry their own risks?

walks referenced skills transitively to a bounded depth, with prefix allow and deny lists, so supply-chain risk in the dependency graph is caught rather than just the top-level skill

Is a flagged finding I previously accepted still tied to the exact code that was reviewed?

binds baseline suppressions to the scanner version, source content, and full finding evidence, so a changed file or upgraded scanner invalidates the old acceptance instead of silently carrying it forward

Is a skill hiding an executable inside a document or archive rather than its script files?

inspects hidden files and nested ZIP-based formats such as DOCX, XLSX, and PPTX without extracting or running their contents, and raises a high-severity finding when a concealed executable is found

all 39 features, with the evidence for each →

Languages

Not documented

Features

39 capabilities across 6 areas

Built from SkillSpector's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • SkillSpector covers 1 of the 5 supply chain security capabilities we track.

What SkillSpector offers you

  • Command-line interface8
  • JSON data export4
  • CI/CD pipeline integration2
  • Scripting language support1
Vulnerability and supply-chain detection 2 capabilities SkillSpector identifies security risks introduced through skill content, including hidden prompt-injection attempts and unsafe supply-chain artefacts. These detections form the core of what the cyber tool scans for.
Prompt-injection and obfuscation detection shipped Detects whitespace-padding tricks used to conceal prompt-injection instructions inside skill content. 5 releases · first seen Aug 2026

release

  • Keeps each P2 hidden-instruction match inside one HTML comment, including --!>, <!-->, and <!---> closers, so visible text between comments and words such as target or POSTGRES are no longer reported as hidden instructions. v2.13.1 · Oct 2026 · source · release history
  • Detects text-direction control characters that disguise code in bundled scripts, not just Markdown. v2.13.0 · Oct 2026 · source · release history
  • Adds detection for whitespace-padding techniques used to hide prompt-injection instructions in skill content. v2.9.4 · Aug 2026 · source · release history
  • Adds detection of whitespace-padding attempts used to obfuscate malicious prompt-injection instructions in skill metadata. v2.9.4 · Aug 2026 · source · release history
  • Adds detection for whitespace-padding techniques used to conceal prompt-injection instructions inside skill content. v2.9.4 · Aug 2026 · source · release history
Python bytecode supply-chain detection shipped Flags skills that ship Python bytecode or cache directories as a high-severity supply-chain risk. 5 releases · first seen Aug 2026

release

  • Detects reflective Python module lookups and shipped bytecode inside Python environments. v2.12.0 · Sep 2026 · source · release history
  • Adds detection of reflective Python module lookups and shipped bytecode inside Python environments. v2.12.0 · Sep 2026 · source · release history
  • Existing scans may now report new BH1–BH3 findings for supported bundled hook and settings files (hooks/hooks.json, .claude/settings.json, .claude/settings.local.json); review those findings and use the existing baseline mechanism only after validating the declared execution or permission surface. v2.11.0 · Aug 2026 · source · release history
  • Adds SC8 HIGH finding for skills shipping Python bytecode or __pycache__ content to detect supply-chain risks. v2.9.4 · Aug 2026 · source · release history
  • Adds a HIGH-severity SC8 finding when a skill ships Python bytecode or __pycache__ content, expanding supply-chain coverage. v2.9.4 · Aug 2026 · source · release history
Scan integrity and CI pipeline control 2 capabilities SkillSpector gives pipelines reliable signals about whether a scan completed fully and correctly, so builds can be blocked on failure rather than passing silently. Recursive scan failures and fatal errors are surfaced explicitly rather than swallowed.
Scan completeness reporting and CI blocking shipped Reports whether a scan completed successfully and exposes diagnostic detail so CI pipelines can block on incomplete or failed scans. 26 releases · 9 other sources · first seen Jul 2026

Also counts toward: CI/CD pipeline integration, Command-line interface, JSON data export

release 26 total

  • SkillSpector now reports incomplete inspection when a requested custom YARA rule directory is unavailable. v2.13.3 · Nov 2026 · source · release history
  • Report incomplete inspection when a requested custom YARA rule directory is unavailable. v2.13.3 · Nov 2026 · source · release history
  • scan --recursive with --use-shipped-baseline now exits with code 2 when child skills are detected, instead of silently ignoring the flag. v2.13.1 · Oct 2026 · source · release history
  • scan --mcp-registry combined with --use-shipped-baseline, --transitive, --transitive-depth, --transitive-allow-prefix, or --transitive-deny-prefix now exits with code 2 instead of silently ignoring those options. v2.13.1 · Oct 2026 · source · release history
  • A complete recursive scan with a highest score of MEDIUM (21-50) now exits with CAUTION instead of SAFE. v2.13.1 · Oct 2026 · source · release history
  • Reports a complete recursive scan whose highest score is MEDIUM (21-50) as CAUTION instead of SAFE, matching child reports. v2.13.1 · Oct 2026 · source · release history

example 9 total

  • Detect that a partial batch gap-fill failure was reported as incomplete rather than silently dropped, by checking the exit code and gap_fill_status field in the JSON output. python -m contrib.batch_scan.batch_scan ./my-skills/ --no-llm -f json -o report.json; echo "Exit: $?"; jq '[.[] | select(.gap_fill_status == "incomplete")]' report.json v2.13.1 · Oct 2026 · source
  • Fail CI immediately when a skill scan surfaces any active finding, useful as a hard gate in a pull-request pipeline. skillspector scan ./my-skill/ --fail-on-findings v2.12.0 · Sep 2026 · source
  • Fail CI immediately when a scan of a PR's skill directory surfaces any active finding, regardless of risk-score threshold. skillspector scan ./my-skill/ --fail-on-findings v2.12.0 · Sep 2026 · source
  • Fail CI if any active findings are detected, including those below risk thresholds skillspector scan --fail-on-findings ./my-skill v2.12.0 · Sep 2026 · source
  • Configure the tool to fail if any issue reaches HIGH severity, useful for CI policy gates. cat <<EOF > .skillspector.yaml risk_assessment: max_issue_severity: HIGH EOF skillspector scan ./my-skill v2.10.0 · Aug 2026 · source
  • Surface ledger exceptions in CI to diagnose why an incomplete scan was blocked. skillspector scan ./my-skill/ --format json --output report.json; jq '.analysis_completeness.ledger_exceptions' report.json v2.5.0 · Jul 2026 · source
Baseline fingerprint versioning shipped Ties accepted-finding baselines to the scanner version and source content, and forces regeneration of outdated baseline files to prevent stale suppressions. 11 releases · 4 other sources · first seen Jul 2026

Also counts toward: Command-line interface

release 11 total

  • Baseline generation now uses atomic replacement and refuses updates that cannot preserve file ownership or group — write a new baseline file in those cases. v2.13.0 · Oct 2026 · source · release history
  • Baseline generation uses atomic replacement; updates that cannot preserve ownership or group safely are refused — write a new baseline file instead. v2.13.0 · Oct 2026 · source · release history
  • Exact-fingerprint baselines are version-bound and must be regenerated after upgrading to v2.13.0. v2.13.0 · Oct 2026 · source · release history
  • Adds opt-in auto-discovery of a top-level .skillspector-baseline.yaml file, keeping explicitly supplied baselines authoritative when both are present. v2.9.5 · Aug 2026 · source · release history
  • Adds opt-in auto-discovery of a top-level .skillspector-baseline.yaml file while keeping explicitly supplied baselines authoritative. v2.9.5 · Aug 2026 · source · release history
  • Adds opt-in automatic discovery of a top-level .skillspector-baseline.yaml file; explicitly supplied baselines via --baseline remain authoritative. v2.9.5 · Aug 2026 · source · release history

example

  • Let SkillSpector auto-discover the committed baseline so CI suppresses known findings without an explicit flag. skillspector baseline ./my-skill/ -o .skillspector-baseline.yaml # commit .skillspector-baseline.yaml to the repo root, then in CI: skillspector scan ./my-skill/ v2.9.5 · Aug 2026 · source
  • Regenerate a v2 baseline after upgrading from v1 so fingerprint suppressions are accepted again. skillspector baseline ./my-skill/ -o .skillspector-baseline.yaml v2.5.0 · Jul 2026 · source
  • After upgrading, regenerate a version 2 baseline so fingerprints bind to the new scanner version before committing. skillspector baseline ./my-skill/ -o .skillspector-baseline.yaml v2.5.0 · Jul 2026 · source
  • Accept current findings into a baseline skillspector baseline ./my-skill/ -o .skillspector-baseline.yaml
Resource and ingest controls 2 capabilities SkillSpector enforces configurable limits on the size and volume of content it processes, whether downloaded, archived, or cloned. This prevents runaway resource use and ensures the cyber tool fails safely rather than silently accepting oversized input.
Ingest size and resource limits shipped Caps the size and entry count of URLs, zip archives, and Git repositories the cyber tool will process, erroring out if any limit is exceeded. 10 releases · 1 other source · first seen Aug 2026

release 10 total

  • Raises the default aggregate end-to-end workflow deadline from 60 seconds to 600 seconds across direct CLI, recursive, transitive, and multi-skill analysis paths. v2.11.1 · Sep 2026 · source · release history
  • Applies the configured deadline consistently across direct CLI, recursive, transitive, and multi-skill analysis paths. v2.11.1 · Sep 2026 · source · release history
  • Raises the default aggregate end-to-end workflow and transitive traversal deadline from 60 seconds to 600 seconds, preventing larger valid scans from timing out. v2.11.1 · Sep 2026 · source · release history
  • Adds SKILLSPECTOR_MAX_WORKFLOW_SECONDS environment variable to configure the aggregate workflow deadline for direct, recursive, transitive, and multi-skill scans. v2.11.1 · Sep 2026 · source · release history
  • Adds SKILLSPECTOR_MAX_WORKFLOW_SECONDS environment variable to set a custom aggregate workflow deadline (positive finite seconds); invalid, zero, negative, infinite, or NaN values fall back to the 600-second default. v2.11.1 · Sep 2026 · source · release history
  • Adds SKILLSPECTOR_MAX_WORKFLOW_SECONDS environment variable to set a custom positive finite aggregate workflow deadline; invalid, zero, negative, infinite, and NaN values fall back to the 600-second default. v2.11.1 · Sep 2026 · source · release history

docs

  • Scans AI agent skills for vulnerabilities, malicious patterns, and security risks using static analysis and optional LLM semantic evaluation.
LLM analyzer concurrency control shipped Lets operators set a ceiling on how many LLM analyser requests run at once, avoiding bursts that breach provider rate limits. 5 releases · 3 other sources · first seen Jul 2026

release

  • Control the tool-description comparison batch limit with SKILLSPECTOR_TP4_MAX_BATCHES (default 256) and the workflow deadline with SKILLSPECTOR_MAX_WORKFLOW_SECONDS (default 1,080 seconds), and honor LLM concurrency via SKILLSPECTOR_MAX_LLM_CONCURRENCY.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v2.13.3 · Nov 2026 · source · release history
  • CLI-backed providers now honor SKILLSPECTOR_MODEL_REGISTRY for per-model context and output-token limits. v2.12.0 · Sep 2026 · source · release history
  • Adds SKILLSPECTOR_MAX_LLM_CONCURRENCY environment variable to configure the default async LLM batch concurrency; blank or invalid values retain the default of 10, and values below 1 clamp to 1. v2.5.1 · Jul 2026 · source · release history
  • Adds SKILLSPECTOR_MAX_LLM_CONCURRENCY environment variable to configure the default asynchronous LLM batch concurrency v2.5.1 · Jul 2026 · source · release history
  • Adds SKILLSPECTOR_MAX_LLM_CONCURRENCY environment variable to control the default concurrency of asynchronous LLM analyzer batches (default 10; values below 1 clamp to 1; blank or invalid values retain the default). v2.5.1 · Jul 2026 · source · release history

example

  • Serialize LLM analyzer requests to avoid bursting a rate-limited provider such as Anthropic. export SKILLSPECTOR_MAX_LLM_CONCURRENCY=1 export SKILLSPECTOR_PROVIDER=anthropic export ANTHROPIC_API_KEY=sk-ant-... skillspector scan ./my-skill/ v2.5.1 · Jul 2026 · source
  • Serialize LLM analyzer requests to avoid bursting a rate-limited provider such as one with a strict requests-per-minute cap. SKILLSPECTOR_MAX_LLM_CONCURRENCY=1 skillspector scan ./my-skill/ v2.5.1 · Jul 2026 · source
  • Persist a reduced concurrency limit for all scans run in a Docker-based workflow by adding it to your .env file. SKILLSPECTOR_PROVIDER=anthropic ANTHROPIC_API_KEY=sk-ant-... SKILLSPECTOR_MAX_LLM_CONCURRENCY=3 v2.5.1 · Jul 2026 · source
Transport and access security 1 capability SkillSpector restricts what scan targets and rule sources are reachable depending on how the cyber tool is connected to. This limits the attack surface when the tool is exposed over a network transport.
MCP transport security boundary shipped Blocks HTTP MCP transport from reaching local file targets or local YARA-rule directories, while keeping full local access available over stdio. 10 releases · 1 other source · first seen Aug 2026

release 10 total

  • MCP HTTP listeners are restricted to loopback; remote deployments must add an authenticating proxy. v2.13.0 · Oct 2026 · source · release history
  • MCP HTTP listeners are restricted to loopback; remote MCP deployments that previously accepted direct connections now require an authenticating proxy. v2.13.0 · Oct 2026 · source · release history
  • Restricts MCP HTTP listeners to loopback; remote deployments require an authenticating proxy.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v2.13.0 · Oct 2026 · source · release history
  • Supports safe traversal of intermediate path components via O_PATH on Linux, allowing scans in restricted sandboxes where ancestor directories lack read permission, while preserving final-file and no-symlink protections. v2.11.0 · Aug 2026 · source · release history
  • Supports safe file traversal in restricted Linux sandboxes by opening intermediate path components with O_PATH where available, without requiring read access to every ancestor directory. v2.11.0 · Aug 2026 · source · release history
  • HTTP MCP transport now rejects local filesystem scan targets, requiring remote repository or URL instead. v2.9.4 · Aug 2026 · source · release history

example

  • Run SkillSpector's MCP server over stdio (trusted local transport) to retain the ability to scan local filesystem paths after the HTTP restriction. skillspector mcp --transport stdio v2.9.4 · Aug 2026 · source
Remediation and least-privilege guidance 1 capability SkillSpector links findings to actionable remediation advice, including least-privilege permission guidance. This helps users understand not just what was found but how to address it.
Least-privilege permission guidance shipped Incorporates least-privilege tool-permission guidance into finding remediations so developers know how to scope skill permissions correctly. 1 release · first seen Aug 2026

release

  • Recognises allowed-tools as valid least-privilege permission guidance in remediations and documentation. v2.9.4 · Aug 2026 · source · release history
Other 31 capabilities
static_analysis_coverage shipped Expands static analysis findings to include insecure deserialization patterns and actionable external model/provider selection risks. 18 releases · first seen Aug 2026

release 18 total

  • SkillSpector now follows credential reads nested in urllib request headers into network sinks. v2.13.3 · Nov 2026 · source · release history
  • Detects encoded shell payloads that are decoded and executed. v2.13.0 · Oct 2026 · source · release history
  • Detects sensitive data passed to urllib opener requests, including inline opener calls. v2.13.0 · Oct 2026 · source · release history
  • Improves executable-file detection by checking complete TypeScript declaration files before treating them as non-executable, so partial or disguised runtime code is not skipped, and by recognizing more executable Python files, including .pyw files and extensionless launchers. v2.13.0 · Oct 2026 · source · release history
  • Inspects readable instructions hidden behind binary file prefixes while keeping ordinary PDF/GIF assets and XMP metadata from producing false alarms. v2.13.0 · Oct 2026 · source · release history
  • Recognizes more executable Python files, including .pyw files and extensionless launchers. v2.13.0 · Oct 2026 · source · release history
Lifecycle and permission surface detection shipped Detects bundled lifecycle hooks, sensitive content transfer, and broad project permission surfaces in skill configuration files. 9 releases · first seen Aug 2026

release 9 total

  • SkillSpector now inspects npx commands in JSON MCP configurations and recognizes additional Claude, Cline, and Roo Code credential and configuration filenames. v2.13.3 · Nov 2026 · source · release history
  • Adds a HIGH MP3 finding for an explicit instruction to treat or adopt linked state as the agent's memory or conversation state, unless that instruction is directly prohibited. v2.13.1 · Oct 2026 · source · release history
  • Inspects hooks declared in Claude plugin manifests and reports incomplete coverage when those declarations cannot be fully checked. v2.13.0 · Oct 2026 · source · release history
  • Adds detection for bundled settings that use the short -r flag to load and run extra code, and flags bundled settings that run commands, redirect AI traffic, or automatically approve connected tool servers. v2.13.0 · Oct 2026 · source · release history
  • Flags bundled settings that run commands, redirect AI traffic, automatically approve connected tool servers, or use the short -r flag to load and run extra code in Node settings. v2.13.0 · Oct 2026 · source · release history
  • Adds new BH1, BH2, and BH3 findings for bundled lifecycle hooks, sensitive content transfer, and project permission modes. v2.11.0 · Aug 2026 · source · release history
multilingual_output shipped Sets the language of human-readable LLM-generated finding text via an environment variable across discovery, meta-analysis, and MCP analysis. 5 releases · 3 other sources · first seen Aug 2026

release

  • Non-English gap-fill findings are now included in contributed batch-scan scores, recommendations, and exit status instead of retaining a stale SAFE verdict. v2.13.3 · Nov 2026 · source · release history
  • Include non-English gap-fill findings in contributed batch-scan scores, recommendations, and exit status instead of retaining a stale SAFE verdict. v2.13.3 · Nov 2026 · source · release history
  • Adds SKILLSPECTOR_OUTPUT_LANGUAGE environment variable to set the language of human-readable LLM-generated finding text. v2.10.0 · Aug 2026 · source · release history
  • Adds SKILLSPECTOR_OUTPUT_LANGUAGE environment variable to set the language of human-readable LLM-generated finding text across discovery analyzers, the meta-analyzer, and MCP tool-poisoning analysis. v2.10.0 · Aug 2026 · source · release history
  • Adds SKILLSPECTOR_OUTPUT_LANGUAGE environment variable for human-readable LLM finding text in output. v2.10.0 · Aug 2026 · source · release history

example

  • Scan a directory of skills in batch and get non-English gap-fill findings correctly reflected in scores and exit status. python -m contrib.batch_scan.batch_scan ./my-skills/ --workers 20 -f json -o report.json v2.13.3 · Nov 2026 · source
  • Produce LLM finding text in French for a report shared with a francophone security team. SKILLSPECTOR_OUTPUT_LANGUAGE=French skillspector scan ./my-skill/ --format markdown --output report.md v2.10.0 · Aug 2026 · source
  • Set the environment variable so LLM-generated findings are rendered in German instead of English. export SKILLSPECTOR_OUTPUT_LANGUAGE=de && skillspector scan ./my-skill --output json v2.10.0 · Aug 2026 · source
transitive_dependency_scanning shipped Scans referenced skills and their transitive dependencies with bounded depth and configurable allow/deny prefixes to detect supply-chain risks. 4 releases · 3 other sources · first seen Aug 2026

Shared capability: Dependency scanning

Also counts toward: Command-line interface

release

  • Rejects scan --mcp-registry combined with --use-shipped-baseline, --transitive, --transitive-depth, --transitive-allow-prefix, or --transitive-deny-prefix with exit code 2, before the registry is read or a report is written; previously these options were silently ignored. v2.13.1 · Oct 2026 · source · release history
  • Adds --transitive flag to opt into transitive scanning of referenced skills, with --transitive-depth, --transitive-allow-prefix, and --transitive-deny-prefix controls for bounded traversal and source filtering. v2.10.0 · Aug 2026 · source · release history
  • Adds --transitive, --transitive-depth, --transitive-allow-prefix, and --transitive-deny-prefix flags for opt-in transitive reference scanning with bounded traversal. v2.10.0 · Aug 2026 · source · release history
  • Adds --transitive flag to opt into transitive scanning of referenced skills, with --transitive-depth, --transitive-allow-prefix, and --transitive-deny-prefix controls for bounded traversal. v2.10.0 · Aug 2026 · source · release history

example

  • Scan a skill bundle and its transitive dependencies up to depth 3, allowing only refs starting with refs/skills/ and denying refs/external/. skillspector scan ./my-skill --transitive --transitive-depth 3 --transitive-allow-prefix 'refs/skills/' --transitive-deny-prefix 'refs/external/' v2.10.0 · Aug 2026 · source
  • Scan a skill and all skills it references transitively, limiting traversal depth and restricting allowed prefixes, to catch supply-chain risks in the full dependency graph. skillspector scan ./my-skill/ --transitive --transitive-depth 2 --transitive-allow-prefix https://github.com/trusted-org/ --transitive-deny-prefix https://github.com/untrusted-org/ v2.10.0 · Aug 2026 · source
  • Scan a skill and all skills it references transitively, limiting depth and restricting allowed sources, to catch supply-chain risks in referenced dependencies. skillspector scan ./my-skill/ --transitive --transitive-depth 2 --transitive-allow-prefix https://github.com/trusted-org/ v2.10.0 · Aug 2026 · source
llm_provider_integration shipped Adds support for Ollama local inference, Azure OpenAI routing, and generic OpenAI-compatible provider endpoints. 7 releases · first seen Aug 2026

release 7 total

  • NVIDIA Build now defaults to GLM-5.3 after retirement of GLM-5.2; explicit model overrides continue to work. v2.13.0 · Oct 2026 · source · release history
  • NVIDIA Build defaults to GLM-5.3 after retirement of the previous default (GLM-5.2); explicit model overrides remain supported. v2.13.0 · Oct 2026 · source · release history
  • Registers gemini-3.5-flash model budgets for the root and OpenAI-compatible registries, enabling use through the existing openai provider. v2.12.0 · Sep 2026 · source · release history
  • Adds gemini-3.5-flash model budgets to the root and OpenAI-compatible registries, usable through the existing openai provider. v2.12.0 · Sep 2026 · source · release history
  • Adds Ollama provider for local OpenAI-compatible inference, Azure OpenAI deployment routing, and a configurable generic OpenAI-compatible provider endpoint. v2.9.5 · Aug 2026 · source · release history
  • Adds Ollama support for local OpenAI-compatible inference, Azure OpenAI deployment routing, and a configurable provider for generic OpenAI-compatible endpoints. v2.9.5 · Aug 2026 · source · release history
LLM sampling reproducibility controls shipped Configures LLM temperature and seed parameters to ensure deterministic scan results across repeated executions. 4 releases · 3 other sources · first seen Aug 2026

release

  • Adds SKILLSPECTOR_TEMPERATURE (values 0–1) and SKILLSPECTOR_SEED (integer) environment variables for optional LLM sampling control; forwarded to OpenAI-compatible and Azure OpenAI endpoints, and left unset to preserve provider defaults. v2.11.0 · Aug 2026 · source · release history
  • Expands skillspector scan --help to list all supported hosted, local, compatible, and CLI-backed LLM providers with their authentication paths. v2.11.0 · Aug 2026 · source · release history
  • Adds SKILLSPECTOR_TEMPERATURE and SKILLSPECTOR_SEED environment variables to control LLM sampling behavior. v2.11.0 · Aug 2026 · source · release history
  • Adds SKILLSPECTOR_TEMPERATURE (values 0–1) and SKILLSPECTOR_SEED (integers) environment variables for optional LLM sampling control; forwarded to OpenAI-compatible and Azure OpenAI endpoints; leaving either unset preserves provider defaults. v2.11.0 · Aug 2026 · source · release history

example

  • Pin LLM output for reproducible scans when using an OpenAI-compatible endpoint — useful for CI pipelines where you want consistent results across runs. SKILLSPECTOR_TEMPERATURE=0 SKILLSPECTOR_SEED=42 skillspector scan ./my-skill/ v2.11.0 · Aug 2026 · source
  • Control LLM non-determinism for reproducible scanning results by setting temperature and seed before invocation. SKILLSPECTOR_TEMPERATURE=0.2 SKILLSPECTOR_SEED=42 skillspector scan --repo . v2.11.0 · Aug 2026 · source
  • Pass LLM sampling controls via a .env file for Docker-based scans to keep credentials and tuning out of shell history. SKILLSPECTOR_PROVIDER=openai OPENAI_API_KEY=sk-... SKILLSPECTOR_TEMPERATURE=0 SKILLSPECTOR_SEED=42 v2.11.0 · Aug 2026 · source
GitHub subdirectory scan support shipped Supports scanning specific repository subdirectories via HTTPS GitHub tree URLs, resolving the longest advertised branch or tag name. 3 releases · 3 other sources · first seen Sep 2026

release

  • Supports HTTPS GitHub /tree/ URLs to select a repository subdirectory as scan input, resolving the longest advertised branch/tag name including refs containing slashes. v2.12.0 · Sep 2026 · source · release history
  • Support for HTTPS GitHub /tree/ URLs to scan subdirectories by longest advertised branch/tag name v2.12.0 · Sep 2026 · source · release history
  • Adds support for HTTPS GitHub /tree/ URLs to select an existing repository subdirectory as scan input, resolving using the longest advertised branch/tag name including refs containing slashes. v2.12.0 · Sep 2026 · source · release history

example

  • Scan a specific repository subdirectory via GitHub URL skillspector scan https://github.com/owner/repo/tree/main/path/to/subdir v2.12.0 · Sep 2026 · source
  • Scan only the src/ subdirectory of a GitHub repository by passing a /tree/ URL directly. skillspector scan https://github.com/example-org/my-skill/tree/main/src v2.12.0 · Sep 2026 · source
  • Scan only a specific subdirectory of a GitHub repository, such as a single skill inside a monorepo. skillspector scan https://github.com/org/skills-monorepo/tree/main/skills/my-skill v2.12.0 · Sep 2026 · source
Supply-chain dependency resolution detection shipped Identifies noncanonical or unresolved dependency sources across major package managers, shell scripts, and documentation code fences. 5 releases · first seen Sep 2026

Also counts toward: Scripting language support

release

  • Extract Pipenv dependencies and check locked versions, preserving incomplete coverage for malformed or unsupported dependency declarations. v2.13.3 · Nov 2026 · source · release history
  • SkillSpector now extracts Pipenv dependencies and checks locked versions, preserving incomplete coverage for malformed or unsupported dependency declarations. v2.13.3 · Nov 2026 · source · release history
  • Adds SC10 detection of noncanonical or unresolved dependency sources across npm, Yarn, pip, Poetry, Maven, and Cargo configuration, shell scripts, generated heredocs, and actionable shell fences in SKILL.md/README.md. v2.12.0 · Sep 2026 · source · release history
  • New SC10 detection for noncanonical or unresolved dependency sources in npm, Yarn, pip, Poetry, Maven, Cargo, shell scripts, and code fences v2.12.0 · Sep 2026 · source · release history
  • Adds SC10 detection of noncanonical or unresolved dependency sources in npm, Yarn, pip, Poetry, Maven, and Cargo configuration, supported shell scripts, generated heredocs, and actionable shell fences in SKILL.md/README.md. v2.12.0 · Sep 2026 · source · release history
Baseline-based scanning shipped Performs scans against an existing baseline to isolate and report only new or changed findings. 3 releases · 2 other sources · first seen Aug 2026

Also counts toward: Command-line interface

release

  • Rejects --use-shipped-baseline with exit code 2 when scan --recursive detects one or more child skills, before any report is written. v2.13.1 · Oct 2026 · source · release history
  • Rejects --use-shipped-baseline with exit code 2 when scan --recursive detects child skills, before any report is written; previously the option was silently ignored. v2.13.1 · Oct 2026 · source · release history
  • scan --recursive now rejects --use-shipped-baseline with exit code 2 when child skills are detected; previously the option was silently ignored. v2.13.1 · Oct 2026 · source · release history

example

  • Let SkillSpector automatically pick up a project-level baseline without passing it explicitly on every run. # Place your baseline at the repo root, then run normally — SkillSpector will discover it automatically cp my-baseline.yaml .skillspector-baseline.yaml skillspector scan . v2.9.5 · Aug 2026 · source
  • Scan against baseline for new findings skillspector scan ./my-skill/ --baseline .skillspector-baseline.yaml
JSON output generation shipped Outputs structured scan results in JSON format for programmatic consumption. 3 releases · 2 other sources · first seen Oct 2026

Also counts toward: Command-line interface, JSON data export

release

  • Adds skillspector baseline <path> -o - to write a baseline as JSON to stdout.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v2.13.1 · Oct 2026 · source · release history
  • Writes report files (scan, scan --recursive, scan --mcp-registry, and --output) and baselines atomically through an already-opened, no-follow parent directory; skillspector baseline <path> -o - writes the baseline as JSON to stdout.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v2.13.1 · Oct 2026 · source · release history
  • Writes report files (scan, scan --recursive, scan --mcp-registry, and the batch scanner's --output) and baselines atomically through an already-opened, no-follow parent directory, refusing symlinked or special-file destinations. v2.13.1 · Oct 2026 · source · release history

example

  • Write a baseline to stdout as JSON for piping or inspection, using the new -o - shorthand. skillspector baseline ./my-skill/ -o - v2.13.1 · Oct 2026 · source
  • Output scan results as JSON skillspector scan ./my-skill/ --format json --output report.json
Local CLI-based LLM provider support shipped Enables semantic analysis via a local OpenCode instance through a dedicated provider configuration. 4 releases · 1 other source · first seen Sep 2026

Also counts toward: Command-line interface

release

  • The Codex CLI analysis provider is disabled; any workflow relying on it must switch to another supported provider. v2.13.0 · Oct 2026 · source · release history
  • The Codex CLI analysis provider is disabled; scans configured to use it must be switched to another supported provider. v2.13.0 · Oct 2026 · source · release history
  • Adds SKILLSPECTOR_PROVIDER=opencode_cli to run semantic analysis through a local OpenCode login, requiring exactly OpenCode 1.18.31 and failing closed on auth, version, policy, or empty-output failures. v2.12.0 · Sep 2026 · source · release history
  • SKILLSPECTOR_PROVIDER=opencode_cli runs semantic analysis through a local OpenCode instance via the /skillspector command and skillspector_scan tool v2.12.0 · Sep 2026 · source · release history

example

  • Run semantic analysis using a local OpenCode instance for stricter policy enforcement SKILLSPECTOR_PROVIDER=opencode_cli skillspector scan ./skill-with-code-fences v2.12.0 · Sep 2026 · source
Static analysis performance tuning shipped Configures the time allowance per artifact for static pattern and YARA scanning to prevent timeouts on large inputs. 3 releases · 2 other sources · first seen Sep 2026

release

  • SKILLSPECTOR_MAX_STATIC_ANALYSIS_SECONDS_PER_ARTIFACT configures the static pattern and YARA time allowance per artifact (default 30→300s) v2.12.0 · Sep 2026 · source · release history
  • Adds SKILLSPECTOR_MAX_STATIC_ANALYSIS_SECONDS_PER_ARTIFACT environment variable to configure static-pattern and YARA time allowance per artifact; default raised from 30 to 300 seconds. v2.12.0 · Sep 2026 · source · release history
  • Adds SKILLSPECTOR_MAX_STATIC_ANALYSIS_SECONDS_PER_ARTIFACT to configure the per-artifact static-pattern and YARA time allowance; default raised from 30 to 300 seconds. v2.12.0 · Sep 2026 · source · release history

example

  • Set a persistent custom deadline in a Docker env-file so all container-based scans share the same budget. SKILLSPECTOR_PROVIDER=anthropic ANTHROPIC_API_KEY=sk-ant-... SKILLSPECTOR_MAX_WORKFLOW_SECONDS=1200 v2.11.1 · Sep 2026 · source
  • Override the default 600-second deadline when scanning a large recursive skill tree that needs more time. SKILLSPECTOR_MAX_WORKFLOW_SECONDS=1800 skillspector scan ./my-large-skill/ v2.11.1 · Sep 2026 · source
bounded_nested_inspection shipped Inspects hidden files and nested ZIP-compatible artifacts (DOCX, XLSX, PPTX) without extraction to identify concealed executables. 4 releases · first seen Aug 2026

release

  • Inspect npx commands in JSON MCP configurations and now recognize additional Claude, Cline, and Roo Code credential and configuration filenames. v2.13.3 · Nov 2026 · source · release history
  • Adds bounded local inspection of hidden files and ZIP-compatible nested artifacts (ZIP, DOCX, XLSX, PPTX) without extracting or executing members, raising HIGH SC9 findings for concealed executables. v2.10.0 · Aug 2026 · source · release history
  • Enables bounded local inspection of hidden and nested ZIP, DOCX, XLSX, and PPTX content without extracting or executing members. v2.10.0 · Aug 2026 · source · release history
  • Adds bounded local inspection of hidden files and ZIP-compatible nested artifacts (DOCX, XLSX, PPTX) without extracting or executing members, raising HIGH SC9 findings for concealed executables. v2.10.0 · Aug 2026 · source · release history
MCP registry posture scanning shipped The cyber tool can scan the security posture of Model Context Protocol registries to identify misconfigurations and risks. 3 releases · 1 other source · first seen Aug 2026

Also counts toward: Command-line interface

release

  • Rejects scan --mcp-registry combined with --use-shipped-baseline, --transitive, --transitive-depth, --transitive-allow-prefix, or --transitive-deny-prefix with exit code 2 before the registry is read or a report is written. v2.13.1 · Oct 2026 · source · release history
  • scan --mcp-registry now rejects --use-shipped-baseline, --transitive, --transitive-depth, --transitive-allow-prefix, and --transitive-deny-prefix with exit code 2; previously these options were silently ignored. v2.13.1 · Oct 2026 · source · release history
  • MCP registry posture scanning is now available to scan the posture of Model Context Protocol registries. v2.5.2 · Aug 2026 · source · release history

example

  • Confirm that unsupported flag combinations with --mcp-registry are caught before any registry traffic or report is written. skillspector scan registry.json --mcp-registry --transitive && echo 'should not reach here' v2.13.1 · Oct 2026 · source
Comprehensive input scanning shipped Provides capabilities to scan local skill directories and remote Git repositories for security vulnerabilities. 2 releases · 2 other sources · first seen Oct 2026

release

  • If a real directory path ending in ! collides with an archive-member path, that directory must be renamed to allow both files to be fully inspected. v2.13.0 · Oct 2026 · source · release history
  • If a real directory ending in ! collides with an archive-member path, that directory must be renamed to allow both files to be fully inspected. v2.13.0 · Oct 2026 · source · release history

example

  • Scan a local skill directory skillspector scan ./my-skill/
  • Scan a remote Git repository skillspector scan https://github.com/user/my-skill
LLM provider metadata provenance shipped Records model identity, configured versus effective providers, and build revision metadata in JSON report outputs. 4 releases · first seen Sep 2026

Also counts toward: JSON data export

release

  • Adds SKILLSPECTOR_BUILD_REVISION environment variable to supply source revision metadata for metadata.llm_provenance when unavailable from the installed package. v2.12.0 · Sep 2026 · source · release history
  • Adds metadata.llm_provenance (schema version 1) to JSON reports, recording sanitized model/package/source identity, configured vs. effective providers, and sampling/reasoning controls; SKILLSPECTOR_BUILD_REVISION can supply source revision metadata. v2.12.0 · Sep 2026 · source · release history
  • JSON reports add metadata.llm_provenance to record bounded, sanitized model/package/source identity v2.12.0 · Sep 2026 · source · release history
  • Adds metadata.llm_provenance (schema version 1) to JSON reports, recording sanitized, bounded model/package/source identity and distinguishing configured, resolved, and effective providers without endpoint URLs or credentials. v2.12.0 · Sep 2026 · source · release history
Atomic and safe report file writing shipped Writes report files and baselines atomically through a pre-opened parent directory, refusing symlinked or special-file destinations to prevent race conditions and symlink-based path traversal. 3 releases · first seen Oct 2026

release

  • Baseline and recursive report destinations that would overwrite the primary input or a discovered child skill's input, including file aliases, are now rejected — existing scripts that write reports to the same path as the input will fail. v2.13.3 · Nov 2026 · source · release history
  • SkillSpector now rejects baseline and recursive report destinations that would overwrite the primary input or a discovered child skill's input, including file aliases. v2.13.3 · Nov 2026 · source · release history
  • Writes report files (scan, scan --recursive, scan --mcp-registry, and the batch scanner's --output) and baselines atomically through an already-opened, no-follow parent directory, refusing symlinked or special-file destinations. v2.13.1 · Oct 2026 · source · release history
Batch scan limits configuration shipped Exposes configurable caps on batch size and scan duration so large skill collection scans can run without hitting default limits. 1 release · 2 other sources · first seen Nov 2026

release

  • Control the tool-description comparison batch limit with SKILLSPECTOR_TP4_MAX_BATCHES (default 256) and the workflow deadline with SKILLSPECTOR_MAX_WORKFLOW_SECONDS (default 1,080 seconds), alongside the existing SKILLSPECTOR_MAX_LLM_CONCURRENCY for bounded parallel batch execution.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v2.13.3 · Nov 2026 · source · release history

example

  • Run a large LLM-assisted scan that would previously time out under the default 18-minute deadline, raising the ceiling for big skills. SKILLSPECTOR_TP4_MAX_BATCHES=512 SKILLSPECTOR_MAX_WORKFLOW_SECONDS=3600 SKILLSPECTOR_MAX_LLM_CONCURRENCY=8 skillspector scan ./large-skill/ v2.13.3 · Nov 2026 · source
  • Run a large skill collection scan without hitting the default 256-batch or 18-minute limits by raising both caps for a provider with high throughput. SKILLSPECTOR_TP4_MAX_BATCHES=512 SKILLSPECTOR_MAX_WORKFLOW_SECONDS=3600 SKILLSPECTOR_MAX_LLM_CONCURRENCY=8 skillspector scan ./my-large-skill/ v2.13.3 · Nov 2026 · source
Baseline acceptance and validation shipped Allows accepting current findings into a baseline file for future comparison to filter out known issues. 1 release · 2 other sources · first seen Jul 2026

release

  • Baseline files now use version 2 format, binding accepted findings to scanner version and source content. v2.5.0 · Jul 2026 · source · release history

example

  • Export an existing baseline to stdout for piping into another tool or auditing without creating a file. skillspector baseline ./my-skill/.skillspector-baseline.json -o - v2.13.1 · Oct 2026 · source
  • Accept current findings into a baseline skillspector baseline ./my-skill/ -o .skillspector-baseline.yaml
MCP installation reference distinction shipped Distinguishes between missing local file references and ambiguous unresolved references during MCP skill installation decisions. 3 releases · first seen Sep 2026

release

  • Distinguishes reference_missing from reference_unresolved in MCP installation decisions, allowing scans whose only caveats are missing references to proceed when all discovered files were inspected. v2.12.0 · Sep 2026 · source · release history
  • Distinguishes reference_missing (missing local references) from reference_unresolved (ambiguous matches) in MCP skill-scan installation decisions. v2.12.0 · Sep 2026 · source · release history
  • The reference_missing code replaces what was previously reported as reference_unresolved for missing local file references; tooling that matches on the reference_unresolved string must be updated to handle both values. v2.12.0 · Sep 2026 · source · release history
Prompt label compression shipped Enables unpadded LLM prompt line labels to reduce token usage in scanning inputs. 3 releases · first seen Sep 2026

release

  • Adds SKILLSPECTOR_COMPACT_PROMPTS=1 (also true or yes) to enable unpadded LLM prompt line labels such as L1: instead of L01:. v2.12.0 · Sep 2026 · source · release history
  • Adds SKILLSPECTOR_COMPACT_PROMPTS=1 (also true / yes) to enable shorter unpadded LLM prompt line labels such as L1: instead of L01:. v2.12.0 · Sep 2026 · source · release history
  • SKILLSPECTOR_COMPACT_PROMPTS=1 enables unpadded LLM prompt line labels (e.g. L1:) v2.12.0 · Sep 2026 · source · release history
Semantic analysis fence extension shipped Extends semantic analysis capabilities to non-empty, closed Markdown and text fences with recognized executable-language labels. 3 releases · first seen Sep 2026

release

  • Extends TP4 semantic analysis to non-empty, closed Markdown/text fences with recognized executable-language labels. v2.12.0 · Sep 2026 · source · release history
  • Extends TP4 semantic analysis to non-empty, closed Markdown and text fences with recognized executable-language labels. v2.12.0 · Sep 2026 · source · release history
  • TP4 semantic analysis now includes executable Markdown fences with recognized language labels v2.12.0 · Sep 2026 · source · release history
accurate_source_mapping shipped Maps YARA matches to source lines using byte offsets to ensure accurate reporting of non-ASCII content locations. 3 releases · first seen Aug 2026

release

  • Uses byte offsets when mapping YARA matches back to source lines so non-ASCII content in scanned files is reported at accurate locations. v2.9.5 · Aug 2026 · source · release history
  • Uses byte offsets when mapping YARA matches back to source lines so non-ASCII content is reported accurately. v2.9.5 · Aug 2026 · source · release history
  • Switches YARA match-to-source-line mapping to byte offsets so non-ASCII content is reported at accurate locations. v2.9.5 · Aug 2026 · source · release history
deterministic_rule_scoping shipped Scopes the destructive-autonomy YARA post-filter to built-in rule names and preserves deterministic precedence to prevent custom rule interference. 3 releases · first seen Aug 2026

release

  • Scopes the destructive-autonomy YARA post-filter to SkillSpector's built-in rule namespace and preserves deterministic built-in rule precedence, preventing custom YARA rules that reuse a built-in rule name from being incorrectly filtered. v2.9.5 · Aug 2026 · source · release history
  • Scopes the destructive-autonomy YARA post-filter to SkillSpector's built-in rule namespace and preserves deterministic built-in rule precedence, preventing custom YARA rules that reuse a built-in rule name from being incorrectly post-filtered. v2.9.5 · Aug 2026 · source · release history
  • Scopes the destructive-autonomy YARA post-filter to SkillSpector's built-in rule namespace, preventing custom YARA rules that reuse a built-in rule name from being incorrectly post-filtered. v2.9.5 · Aug 2026 · source · release history
Agent-memory write detection shipped Detects writes to known agent-memory files and directories from automatically run test carriers, including raw Windows paths. 2 releases · first seen Nov 2026

release

  • Detect writes to known agent-memory files and directories from automatically run test carriers, including raw Windows paths. v2.13.3 · Nov 2026 · source · release history
  • SkillSpector now detects writes to known agent-memory files and directories from automatically run test carriers, including raw Windows paths. v2.13.3 · Nov 2026 · source · release history
Ransomware-pattern detection shipped Emits a bounded YARA signal when nearby code lines combine directory walking, encryption, and binary writes, surfacing potential ransomware-like behavior in scanned skills. 2 releases · first seen Nov 2026

release

  • SkillSpector adds a bounded YARA signal for nearby directory walking, encryption, and binary writes across lines to surface potential ransomware-like behavior alongside existing stronger rules. v2.13.3 · Nov 2026 · source · release history
  • Add a bounded, lower-confidence YARA signal for nearby directory walking, encryption, and binary writes across lines to surface ransomware-like patterns alongside existing stronger ransomware rules. v2.13.3 · Nov 2026 · source · release history
Interactive scan progress streaming shipped Streams execution progress, completed rules, and discovered file trees to standard error during non-verbose terminal scans. 2 releases · first seen Sep 2026

release

  • Non-verbose interactive terminal scans now stream graph execution progress, completed analyzer rules, and a discovered-file tree to standard error without affecting machine-readable standard output. v2.12.0 · Sep 2026 · source · release history
  • Streams bounded live scan progress, completed analyzer rules, and a discovered-file tree to standard error during non-verbose interactive terminal scans. v2.12.0 · Sep 2026 · source · release history
LLM documentation and discovery shipped Documents all supported LLM providers and their authentication paths in the CLI help output. 2 releases · first seen Aug 2026

Also counts toward: Command-line interface

release

  • Expands skillspector scan --help to list all supported hosted, local, compatible, and CLI-backed LLM providers with their authentication paths. v2.11.0 · Aug 2026 · source · release history
  • Expands skillspector scan --help to list all supported hosted, local, compatible, and CLI-backed LLM providers together with their authentication paths. v2.11.0 · Aug 2026 · source · release history
structured_skill_summaries shipped Generates structured summaries for valid AISOP/AISP bundles in terminal, Markdown, JSON, and SARIF outputs. 1 release · 1 other source · first seen Aug 2026

Also counts toward: CI/CD pipeline integration, JSON data export

release

  • Adds structured skill summaries for valid AISOP/AISP bundles across terminal, Markdown, JSON, and SARIF output formats. v2.10.0 · Aug 2026 · source · release history

example

  • Output SARIF for CI/CD integration skillspector scan ./my-skill/ --format sarif --output report.sarif
Credential taint tracking into network sinks shipped Follows credential reads nested inside urllib request headers through to network sinks, extending taint-tracking coverage for credential-leakage paths. 1 release · first seen Nov 2026

release

  • Follow credential reads nested in urllib request headers into network sinks for taint tracking. v2.13.3 · Nov 2026 · source · release history
Dynamic analysis integration shipped The cyber tool discovers registered dynamic analyzers and validates risk-score inputs against the available analyzer set. 1 release · first seen Aug 2026

release

  • Adds dynamic analyzer discovery and validates risk-score inputs against the registered analyzer set. v2.10.0 · Aug 2026 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for SkillSpector, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail SkillSpector puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Commercials

pricing & packaging history · NVIDIA vendor page

6 readings of NVIDIA's pricing page since Jun 2026, with 1 relaunch of its plan lineup and 2 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.

Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.

See plans →

Website history

nvidia.com, every change

NVIDIA's home page and 40 more pages as they looked each month from September 2021 to October 2026: 54 renders, 10 changes of tagline or palette. Step through them, play them, or put any two months side by side.

Website history is included with Researcher and Business.

See plans →

Coverage

Missing something? Tell us

What SkillSpector connects to, runs on and detects, read from its release notes and docs. So far: 2 updated detections, 1 new detection.

Show

3 changes, tracked since Oct 23, 2026.

  • Oct 232026

    updated P2 hidden-instruction detection scope correction

    #452 keeps each P2 hidden-instruction match inside one HTML comment, including the `--!>`, `<!-->` and `<!--->` closers. Keywords match at word and identifier boundaries, so visible text and words such as `target` or `POSTGRES` are not reported as hidden instructions. Run-together directives such as `PLEASEIGNOREPREVIOUSINSTRUCTIONS` remain detected.

    v2.13.1 Source ↗

  • Oct 232026

    new HIGH MP3 finding for state/memory adoption instructions

    #837 stops MP3 from reporting descriptions of a clocked hardware or state-machine 'reset state' as memory manipulation, while keeping direct agent-reset instructions. It adds a HIGH MP3 finding for an explicit instruction to treat or adopt (linked) state as the agent's memory or conversation state, unless that instruction is directly prohibited.

    v2.13.1 Source ↗

  • Oct 232026

    updated TM1 repeated Python assignment handling

    #820 makes TM1 use the final value of a repeated Python assignment target. A flag that was set true and then reassigned with `enabled, enabled = True, False` no longer makes a later `shell=enabled` call a HIGH finding.

    v2.13.1 Source ↗

How we count

Read from 1 of 12 release notes and docs updates we hold for SkillSpector. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through SkillSpector's life, so an old integration can show a recent first-seen date.

Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.

Releases

Show
Coverage in all entries

12 entries

  1. November 20261
  2. October 20262
  3. September 20262
  4. August 20265
  5. July 20262
    Show
    Coverage in all entries

    12 entries

    Project health

    Issue, contributor and maintainer activity in NVIDIA/SkillSpector, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 86 +86 vs prior 12 months
    2. Maintainers 12 +13 joined · −1 left, last 12 months
    3. Bus factor 5 committers behind half the commits
    4. Community-filed 97% of issues opened, last 12 months
    5. Median time to close 11 days first maintainer reply 5.4 days
    6. Open backlog 57 of 201 issues ever filed
    1. Issues opened / month 18 · 1 communitymaintainers
    2. Open backlog 57
    3. Contributors / month 24
    4. Commits / month 94
    5. Stars 17,239
    Issue themes, last 12 months
    • other 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →