Skip to content

RugSnare 1.2.0 - Drift gradation, constraint keys, rename inference, kill-switch detection

Choose a tag to compare

@Paraphern Paraphern released this 11 Oct 20:53
· 158 commits to main since this release

Four rounds of drift-gradation improvements from the KyttoMCP dialogue (P3-P6, all from @heyitsjakub's feedback), plus scanner robustness from field scans of 10+ npm MCP servers.

Four rounds of drift-gradation improvements from the KyttoMCP dialogue
(P3-P6, all from @heyitsjakub's feedback), plus scanner robustness.

Drift gradation (P3-P6: BREAKING / LOOSENED / EXPANDED / NOTATION)

  • Direction-aware grading (P3+P4): schema drift now grades by direction.
    BREAKING = tighten (new required params, narrowed types, added constraints -
    agent must send more, new data channels are exfil-risk). LOOSENED = loosen
    (constraints dropped, types widened, parameters removed - validation
    weakened, still exit 1 but a distinct failure mode). NOTATION = semantically
    empty (dialect switch only). Mixed tighten+loosen = BREAKING (conservative).
    Validated on chrome-devtools-mcp 1.8.0-1.10.1: 30 former BREAKING findings
    now read 30 NOTATION + 0 BREAKING (the MCP SDK v2 migration wave was pure
    notation).
  • EXPANDED direction (P5): a new optional parameter labels EXPANDED
    instead of riding under tighten - backwards-compatible for callers but
    attack surface widened (a new context param is a classic exfil vector).
    Same exit 1, same severity slot as BREAKING; the label just stops
    semver-literate reviewers from reading "breaking" on a non-breaking change.
  • Guard-parameter warnings (P5+P6): when a schema removes, defangs, or
    flips the default of a guard parameter (dry_run, confirm, force,
    safe_mode...), the diff adds a context-specific warning. Conditional on
    additionalProperties (AP:false = loud failure, no silent-ignore warning).
  • Constraint keys (R3, from MongoDB field scans): schemaDiff now detects
    minItems, maxItems, minimum, maximum, minLength, maxLength, pattern,
    multipleOf, uniqueItems, exclusiveMinimum/Maximum, and number-integer
    transitions. Previously invisible (NOTATION on real constraint changes).
  • Default value tracking (P6): schemaDiff compares default values for
    all parameters (previously invisible - schemaHash changed but schemaDiff
    returned [], grade=NOTATION).

Scanner robustness

  • Publish-time version ordering (R10, playwright bug): history now
    sorts versions by npm publish timestamp, not semver. Packages with two
    versioning epochs (1.52.0-alpha from 2025 semver-older than 0.0.x from
    2026) no longer produce phantom cross-epoch pairs.
  • Rename inference (R11, azure-devops flagship): GONE+NEW tool pairs
    with identical schema+prose hashes collapse into RENAMED a -> b -
    the azure case goes from 104 scattered lines to readable
    "renamed: N, really-gone: M, new: K".
  • Kill-switch classification (R12, bybit case): unreachable versions
    now carry a cause (KILLSWITCH / GATED / GIT_DEPS / CRASH / TIMEOUT)
    based on stderr pattern matching - a remote kill-switch is visible as
    a systematic finding, not a generic "exited early".
  • --server-args flag for rugsnare history: per-package launch
    arguments (e.g. LaunchDarkly needs start --transport stdio). Passed
    as a fixed array after the entry point - no shell, no interpolation.
  • --stub-env flag for rugsnare history: injects presence-only dummy
    values for common credential env vars - servers that only check key
    presence at boot now enumerate their tools/list.
  • Version stamp in output: rugsnare diff and rugsnare history print
    the running rugsnare version in the footer (prevents stale-binary
    debugging sessions when comparing outputs).
  • Pins-version mismatch warning (R1/R9): rugsnare scan records the
    package version it scanned against; rugsnare diff warns when the pins
    were taken against a different version than what's currently installed
    ("if you just upgraded: re-scan first").
  • openai-mcp added to --chameleon rotation (R6): Netlify officially
    serves 21 granular tools to openai-mcp vs 9 routers to other clients.

Corpus and docs

  • Corpus 05: key-reorder fixture (corpus/05-key-reorder/): two
    servers with semantically identical schemas in different key order;
    rugsnare diff reports clean (canonicalization proof). Requested by
    @heyitsjakub as a fixture for KyttoMCP#12.
  • Open Pin Format specification drafted at docs/PIN-SPEC.md (internal;
    publication gated on ecosystem timing).
  • Em-dash cleanup: all long dashes replaced with short hyphens across
    source files and documentation (575 replacements).

On-chain: artifact sha256 68d08748... pinned to Base Mainnet (tx 0x5c35...4b13); verify locally with npx rugsnare verify rugsnare-1.2.0.tgz --version 1.2.0 --chain base.

Web: the Runtime scan at rugsnare.com/#history runs rugsnare history in an ephemeral GitHub Actions sandbox - every result links to its public run log. The archive lives at rugsnare.com/scans.

Native launcher (Go, 7 MB, no Node.js needed): unchanged from 1.1.0 - download from v1.1.0 Releases.