Repository navigation
skillspector 2.13.3 - #322878
Merged
Merged
skillspector 2.13.3#322878
Conversation
carlocab
approved these changes
Nov 2, 2026
botantony
force-pushed
the
bump-skillspector-2.13.3
branch
from
November 2, 2026 09:38
b77a9cf to
697e39b
Compare
daeho-ro
approved these changes
Nov 2, 2026
Contributor
|
🤖 An automated task has requested bottles to be published to this PR. Caution Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Created by
brew bumpCreated with
brew bump-formula-pr.resourceblocks have been checked for updates.release notes
comparison batch limit configurable with
SKILLSPECTOR_TP4_MAX_BATCHES, default256, and raise the default workflow deadline to 1,080 seconds (18 minutes),
configurable with
SKILLSPECTOR_MAX_WORKFLOW_SECONDS. Other file, byte, token,concurrency, and provider limits remain enforced. The release also includes the
required bounded parallel batch execution change from upstream commit
9919c159,honoring
SKILLSPECTOR_MAX_LLM_CONCURRENCYand preserving batch result order.responses actually finished and contain the required fields. Report refusals,
truncated responses, missing fields, and invalid tool results as incomplete
inspection. Permit bounded formatting recovery only when a completed response
preserves the same values and structure. Use consistent structured-response
configuration across analyzers, including the supported Opus 5 gateway route,
and run semantic discovery through the shared asynchronous path.
bounded shell syntax, Python string ownership, and generated browser-template
text without treating ordinary data as unfinished shell commands. Preserve
findings and incomplete inspection when text can reach command execution,
syntax is ambiguous, or analysis limits are exceeded.
Security and scan integrity
#938: Reject baseline and
recursive report destinations that would overwrite the primary input or a
discovered child skill's input, including file aliases.
inspection when a requested custom YARA rule directory is unavailable.
gap-fill findings in contributed batch-scan scores, recommendations, and exit
status instead of retaining a stale SAFE verdict.
Python scripts with CRLF shebangs while recording interpreter uncertainty.
coverage for SC3 obfuscation and P2 hidden-instruction checks.
boundaries across Markdown code fences during marker reconstruction, keeping
separate command lines from being combined into a misleading directive.
Long rejected backtick runs are scanned linearly within the current text bound.
nested in
urllibrequest headers into network sinks.#881: Inspect
npxcommands inJSON MCP configurations and recognize additional Claude, Cline, and Roo Code
credential/configuration filenames. The required
#683 dependency accepts version
pins only on the relevant package operand, so an unrelated later pin cannot
hide an unpinned package. JSON command findings retain correct source lines
when keys use escapes or appear more than once.
agent-memory files and directories from automatically run test carriers,
including supported raw Windows paths. A release review correction prevents
unterminated destinations from causing excessive regular-expression backtracking.
lower-confidence YARA signal for nearby directory walking, encryption, and
binary writes across lines. Existing stronger ransomware rules are retained;
the new signature does not prove which files a write replaces.
dependencies and check locked versions, preserving incomplete coverage for
malformed or unsupported dependency declarations.
lockfile pins to
anyio 4.14.2,certifi 2026.10.19,langgraph-sdk 0.4.4, andurllib3 2.8.0, without expanding the supported Python range.matcher timeouts so subsequent artifacts are still inspected and the timed-out
work remains explicitly incomplete.
Scope and upgrading
The increased limits permit larger scans; completion still depends on input
size, provider latency, and the remaining analysis limits. The Pi and OpenCode
wrappers in this maintenance release retain their 120-second process timeout;
use the CLI directly for scans needing the longer workflow deadline.
These changes do not provide general analysis of commands generated and loaded
during execution, including generated helpers and archives. Such workflows may
still report incomplete inspection. Formatting recovery does not invent missing
content or turn an unfinished AI response into a completed review.
Regenerate and review version-bound finding baselines for 2.13.3 rather than
relabeling baselines from another scanner version. The GitHub release provides a
wheel and source distribution; the publication workflow does not publish to PyPI.
View the full release notes at https://github.com/NVIDIA/SkillSpector/releases/tag/v2.13.3.