infrastructure Static interface comparison

EchelonGraph CVE & Exposure

3.2.4 3.2.5

REVIEWPending human review

4 schema changes require review.No new authority detected.

View the upgrade review as Markdown

A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.

Tools16 → 16
Added0
Removed0
Schema changes4
Input schema changes0
Output schema changes4
Unclassified schema changes0
Description changes4
New write authority0
New destructive authority0
New unknown authority0
AnalysisREVIEW

INTERFACE DIFF

What changed, tool by tool

Classification from the recorded findings · definitions from the published snapshots

4 tools with recorded changes

  1. cve_remediationModifiedSchemaDescriptionREVIEWINFO

    What changed

    • cve_remediation — Output schema: schema keywords changed: oneOf [{"additionalProper… → [{"additionalProper….
    • cve_remediation: description changed.

    Why it could matter

    • Code or prompts that read this tool’s results may receive a different shape.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Check consumers of this tool’s output against the new schema.
    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousHow one CVE is fixed, as its sources state it, in one answer. Every text is relayed as stated by its source; EchelonGraph has not tested it. An empty list or a remediation_state of none_in_source or not_parsed is not a finding that no fix exists. Returns fix_status (the API's fix-status rule: state and basis), cisa (for a KEV-listed CVE CISA's required_action, due_date, short_description and notes_urls, verbatim; CISA's required_action is directed at US federal civilian agencies (under BOD 26-04, which replaced BOD 22-01 on 10 June 2026) and is not EchelonGraph's advice.), fixed_branches (each affected package with fixed_branches: every affected range, introduced and fixed or last_affected, and fixed_version, one range's fix), vendor_remediations (each vendor advisory naming the CVE, with remediation_state, remediation_kinds and items, each with kind, source_category, text and url), fix_references (references NVD or the CNA tagged Patch or Mitigation), patches, coverage and failed_sections. kind is the vendor's own category (vendor_fix, workaround, mitigation, no_fix_planned, none_available or other), or may be no_fix_planned if Cisco's summary says none will be released. remediation_state is parsed, none_in_source (none listed for this CVE), not_parsed (that vendor's remediation is not read) or withdrawn. ecosystem, package and version (all three or none, sent in request headers, never in the URL) add installed, the verdict at that version, and fixed_in, the lowest unaffected version above it, or null with fixed_in_reason. A section the API could not read is named in failed_sections, not relayed as empty. A REJECTED CVE answers not_assessed. Past 30,000 characters of JSON, the first text block holds data cut to fit, and the note says what the cut leaves out and where to read it (TEXT CUT); so is structured data (DATA CUT), unless full: true. Cut, vendor texts are shortened first; kinds, states and URLs are kept.
    CurrentHow one CVE is fixed, as its sources state it, in one answer. Every text is relayed as stated by its source; EchelonGraph has not tested it. An empty list or a remediation_state of none_in_source or not_parsed is not a finding that no fix exists. Returns fix_status (the API's fix-status rule: state and basis), cisa (for a KEV-listed CVE CISA's required_action, due_date, short_description and notes_urls, verbatim; CISA's required_action is directed at US federal civilian agencies (under BOD 26-04, which replaced BOD 22-01 on 10 June 2026) and is not EchelonGraph's advice.), fixed_branches (each affected package with fixed_branches: every affected range, introduced and fixed or last_affected, and fixed_version, one range's fix), vendor_remediations (each advisory naming the CVE, with remediation_state, remediation_kinds and items, each with kind, source_category, text and url), fix_references (references NVD or the CNA tagged Patch or Mitigation), patches, coverage and failed_sections. kind is the vendor's own category (vendor_fix, workaround, mitigation, no_fix_planned, none_available or other), or may be no_fix_planned if Cisco's summary says none will be released. remediation_state is parsed, none_in_source (none listed for this CVE), not_parsed (that vendor's remediation is not read) or withdrawn. ecosystem, package and version (all three or none, sent in request headers, never in the URL) add installed, the verdict at that version, and fixed_in, the lowest unaffected version above it, or null with fixed_in_reason. A section the API could not read is named in failed_sections, not relayed as empty. A REJECTED CVE answers not_assessed. Past 30,000 characters of JSON, the first text block holds data cut to fit, and the note says what the cut leaves out and where to read it (TEXT CUT); so is structured data (DATA CUT), unless full: true. Cut, vendor texts are shortened first; kinds, states and URLs are kept.

    Input schema

    Input schema unchanged.

    6 unchanged entries
    • (schema root)
    • cve_id
    • ecosystem
    • full
    • package
    • version

    Output schema

    PropertyPrevious (3.2.4)Current (3.2.5)Change
    (schema root)object, oneOf (2)object, oneOf (2)
    • Changed: oneOf

    oneOf: [{"additionalProperties":{},"properties":{"coverage":{"anyOf":[{"additionalProperties":{},"properties":{"installed_asked":{"anyOf":[{"additionalProperties":{},"properties":{"ecosystem":{"type":"string"},"package":{"type":"string"},"version"… → [{"additionalProperties":{},"properties":{"coverage":{"anyOf":[{"additionalProperties":{},"properties":{"installed_asked":{"anyOf":[{"additionalProperties":{},"properties":{"ecosystem":{"type":"string"},"package":{"type":"string"},"version"… (truncated: full value in the exact JSON)

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  2. get_vendor_advisoryModifiedSchemaDescriptionREVIEWINFO

    What changed

    • get_vendor_advisory — Output schema: schema keywords changed: oneOf [{"additionalProper… → [{"additionalProper….
    • get_vendor_advisory: description changed.

    Why it could matter

    • Code or prompts that read this tool’s results may receive a different shape.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Check consumers of this tool’s output against the new schema.
    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousOne vendor advisory in full, by vendor and advisory ID (the vendor and vendor_advisory_id of a vendor advisory row, never its advisory_id): title, description, severity, cvss_v3_score, cve_ids and known_cve_ids (in EchelonGraph's CVE feed), affected_products, remediation, references, vendor_modified_at, and withdrawn_at and withdrawn_reason when the vendor withdrew it. remediations: each the vendor lists, with kind (vendor_fix, workaround, mitigation, no_fix_planned, none_available or other: the vendor's category, or may be no_fix_planned if Cisco's summary says none will be released), source_category, text, url, cve_ids and product_ids; each text is the vendor's, verbatim, untested by EchelonGraph. remediation_state none_in_source or not_parsed is not a finding that no fix exists. Each advisory carries vendor_published_at (the vendor's date), our_first_seen_at (when EchelonGraph first recorded it) and withdrawn (true: the vendor rescinded it). Each advisory also carries rejected_cve_ids: the CVE IDs it names whose CVE record was rejected (withdrawn) by its numbering authority, which are not active vulnerabilities. coverage.vendor_window is what EchelonGraph holds of that vendor: earliest_vendor_published_at, latest_vendor_published_at, held_since (where that window begins), history_backfill (in_progress or not_started: older advisories not all held yet), history_scope and feed_held_since; null if unreadable or empty. measured_at is our_first_seen_at. freshness is null; vendor_window.last_success_at is the last successful poll. Past 30,000 characters of JSON, the first text block holds data cut to fit, and the note says what the cut leaves out and where to read it (TEXT CUT); so is structured data (DATA CUT), unless full: true. vendor_text_withheld true (Microsoft): title is EchelonGraph's; description, remediation and item texts are empty; cve_records: its first CVEs, each with its CVE-record description or null.
    CurrentOne advisory in full, by vendor and advisory ID (the vendor and vendor_advisory_id of a vendor advisory row, never its advisory_id): title, description, severity, cvss_v3_score, cve_ids and known_cve_ids (in EchelonGraph's CVE feed), affected_products, remediation, references, vendor_modified_at, and withdrawn_at and withdrawn_reason when the vendor withdrew it. remediations: each the vendor lists, with kind (vendor_fix, workaround, mitigation, no_fix_planned, none_available or other: the vendor's category, or may be no_fix_planned if Cisco's summary says none will be released), source_category, text, url, cve_ids and product_ids; each text is the vendor's, verbatim, untested by EchelonGraph. remediation_state none_in_source or not_parsed is not a finding that no fix exists. Each advisory carries vendor_published_at (the vendor's date), our_first_seen_at (when EchelonGraph first recorded it) and withdrawn (true: the vendor rescinded it). Each advisory also carries rejected_cve_ids: the CVE IDs it names whose CVE record was rejected (withdrawn) by its numbering authority, which are not active vulnerabilities. coverage.vendor_window is what EchelonGraph holds of that vendor: earliest_vendor_published_at, latest_vendor_published_at, held_since (where that window begins), history_backfill (in_progress or not_started: older advisories not all held yet), history_scope and feed_held_since; null if unreadable or empty. measured_at is our_first_seen_at. freshness is null; vendor_window.last_success_at is the last successful poll. Past 30,000 characters of JSON, the first text block holds data cut to fit, and the note says what the cut leaves out and where to read it (TEXT CUT); so is structured data (DATA CUT), unless full: true. vendor_text_withheld true (Microsoft): title is EchelonGraph's; description, remediation and item texts are empty; cve_records: its first CVEs, each with its CVE-record description or null.

    Input schema

    Input schema unchanged.

    4 unchanged entries
    • (schema root)
    • advisory_id
    • full
    • vendor

    Output schema

    PropertyPrevious (3.2.4)Current (3.2.5)Change
    (schema root)object, oneOf (2)object, oneOf (2)
    • Changed: oneOf

    oneOf: [{"additionalProperties":{},"properties":{"coverage":{"anyOf":[{"additionalProperties":{},"properties":{"vendor_window":{"anyOf":[{"additionalProperties":{},"description":"A vendor's window in what EchelonGraph holds: vendor, advisories (ho… → [{"additionalProperties":{},"properties":{"coverage":{"anyOf":[{"additionalProperties":{},"properties":{"vendor_window":{"anyOf":[{"additionalProperties":{},"description":"A vendor's window in what EchelonGraph holds: vendor, advisories (ho… (truncated: full value in the exact JSON)

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  3. search_vendor_advisoriesModifiedSchemaDescriptionREVIEWINFO

    What changed

    • search_vendor_advisories — Output schema: schema keywords changed: oneOf [{"additionalProper… → [{"additionalProper….
    • search_vendor_advisories: description changed.

    Why it could matter

    • Code or prompts that read this tool’s results may receive a different shape.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Check consumers of this tool’s output against the new schema.
    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousSearch or list vendor-published advisories, newest first. A query of 3 or more characters is matched case-insensitively as a substring of each advisory's title, description, vendor name, IDs and affected_products (search_match substring). A query of 1 or 2 characters matches whole words only (search_match word). Filter by vendor (slug), severity band and whether the advisory names any CVE ID. Advisories their vendor withdrew are left out. Returns advisories, each with vendor, vendor_advisory_id, title, severity, cvss_v3_score, cve_ids, summary and affected_products where present, and total, total_capped, limit, offset, search_applied and search_match. A search counts at most 1,000 matches: past that, total is 1000 and total_capped is true, which means 1,000 or more (the note writes 1,000+), never exactly 1,000. Each advisory also carries rejected_cve_ids: the CVE IDs it names whose CVE record was rejected (withdrawn) by its numbering authority, which are not active vulnerabilities. The query is sent in a request header, never in the URL. coverage repeats those beside returned, and gives vendor_windows, each vendor's window in what EchelonGraph holds: vendor, advisories, earliest_vendor_published_at, latest_vendor_published_at, held_since (where that window begins), history_backfill (in_progress or not_started: older advisories not all held yet), history_scope and feed_held_since. An advisory published before its vendor's held_since may not be held, so no advisory from a vendor is not a finding that it published none. Past 30,000 characters of JSON, the first text block holds data cut to fit, and the note says what the cut leaves out and where to read it (TEXT CUT); so is structured data (DATA CUT), unless full: true. Cut, each row keeps vendor, vendor_advisory_id, title, severity and cve_ids at least, its strings and lists shortened, or rows are left out and the note gives the offset to call next.
    CurrentSearch or list advisories, newest first. A query of 3 or more characters is matched case-insensitively as a substring of each advisory's title, description, vendor name, IDs and affected_products (search_match substring). A query of 1 or 2 characters matches whole words only (search_match word). Filter by vendor (slug), severity band and whether the advisory names any CVE ID. Advisories their vendor withdrew are left out. Returns advisories, each with vendor, vendor_advisory_id, title, severity, cvss_v3_score, cve_ids, summary and affected_products where present, and total, total_capped, limit, offset, search_applied and search_match. A search counts at most 1,000 matches: past that, total is 1000 and total_capped is true, which means 1,000 or more (the note writes 1,000+), never exactly 1,000. Each advisory also carries rejected_cve_ids: the CVE IDs it names whose CVE record was rejected (withdrawn) by its numbering authority, which are not active vulnerabilities. The query is sent in a request header, never in the URL. coverage repeats those beside returned, and gives vendor_windows, each vendor's window in what EchelonGraph holds: vendor, advisories, earliest_vendor_published_at, latest_vendor_published_at, held_since (where that window begins), history_backfill (in_progress or not_started: older advisories not all held yet), history_scope and feed_held_since. An advisory published before its vendor's held_since may not be held, so no advisory from a vendor is not a finding that it published none. Past 30,000 characters of JSON, the first text block holds data cut to fit, and the note says what the cut leaves out and where to read it (TEXT CUT); so is structured data (DATA CUT), unless full: true. Cut, each row keeps vendor, vendor_advisory_id, title, severity and cve_ids at least, its strings and lists shortened, or rows are left out and the note gives the offset to call next.

    Input schema

    Input schema unchanged.

    8 unchanged entries
    • (schema root)
    • full
    • has_cve
    • limit
    • offset
    • query
    • severity
    • vendor

    Output schema

    PropertyPrevious (3.2.4)Current (3.2.5)Change
    (schema root)object, oneOf (2)object, oneOf (2)
    • Changed: oneOf

    oneOf: [{"additionalProperties":{},"properties":{"coverage":{"anyOf":[{"additionalProperties":{},"properties":{"limit":{"type":["number","null"]},"offset":{"type":["number","null"]},"returned":{"type":["number","null"]},"search_applied":{"type":["… → [{"additionalProperties":{},"properties":{"coverage":{"anyOf":[{"additionalProperties":{},"properties":{"limit":{"type":["number","null"]},"offset":{"type":["number","null"]},"returned":{"type":["number","null"]},"search_applied":{"type":["… (truncated: full value in the exact JSON)

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
  4. vendor_advisories_for_cveModifiedSchemaDescriptionREVIEWINFO

    What changed

    • vendor_advisories_for_cve — Output schema: schema keywords changed: oneOf [{"additionalProper… → [{"additionalProper….
    • vendor_advisories_for_cve: description changed.

    Why it could matter

    • Code or prompts that read this tool’s results may receive a different shape.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Check consumers of this tool’s output against the new schema.
    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousThe vendor-published advisories that name one CVE, newest first, at most 20: for each, vendor, vendor_advisory_id, title, severity and cvss_v3_score where given. Covers the vendor feeds EchelonGraph polls, for example Microsoft MSRC, Red Hat, Cisco, Palo Alto Networks and GitHub GHSA; an empty answer means none of the advisories EchelonGraph holds names the CVE, not that no vendor published one. Each advisory carries vendor_published_at (the vendor's date), our_first_seen_at (when EchelonGraph first recorded it) and withdrawn (true: the vendor rescinded it). Each advisory also carries rejected_cve_ids: the CVE IDs it names whose CVE record was rejected (withdrawn) by its numbering authority, which are not active vulnerabilities. The answer's cve_rejected is true when the CVE record of the CVE asked for was rejected. Each row has remediation_kinds and remediation_state (not_parsed is not none). coverage gives returned, cap, at_cap (true: may be more) and cve_year; vendor_windows, each vendor's window: vendor, advisories, earliest_vendor_published_at, latest_vendor_published_at, held_since (where that window begins) and history_backfill (in_progress or not_started: older advisories not all held yet); and vendors_not_fully_held, the vendors absent from the answer of which EchelonGraph holds none, whose held_since is after 1 January of cve_year or not known (outside history_scope, feed_held_since), or whose history is still being read or collection_state is not ok. An advisory published before its vendor's held_since may not be held, so no advisory from a vendor is not a finding that it published none. Past 30,000 characters of JSON, the first text block holds data cut to fit, and the note says what the cut leaves out and where to read it (TEXT CUT); so is structured data (DATA CUT), unless full: true. Cut, each row keeps vendor, vendor_advisory_id, title, severity and cve_ids at least, its strings and lists shortened.
    CurrentThe advisories that name one CVE, newest first, at most 20: for each, vendor, vendor_advisory_id, title, severity and cvss_v3_score where given. Covers the vendor feeds EchelonGraph polls, for example Microsoft MSRC, Red Hat, Cisco, Palo Alto Networks and GitHub GHSA; an empty answer means none of the advisories EchelonGraph holds names the CVE, not that no vendor published one. Each advisory carries vendor_published_at (the vendor's date), our_first_seen_at (when EchelonGraph first recorded it) and withdrawn (true: the vendor rescinded it). Each advisory also carries rejected_cve_ids: the CVE IDs it names whose CVE record was rejected (withdrawn) by its numbering authority, which are not active vulnerabilities. The answer's cve_rejected is true when the CVE record of the CVE asked for was rejected. Each row has remediation_kinds and remediation_state (not_parsed is not none). coverage gives returned, cap, at_cap (true: may be more) and cve_year; vendor_windows, each vendor's window: vendor, advisories, earliest_vendor_published_at, latest_vendor_published_at, held_since (where that window begins) and history_backfill (in_progress or not_started: older advisories not all held yet); and vendors_not_fully_held, the vendors absent from the answer of which EchelonGraph holds none, whose held_since is after 1 January of cve_year or not known (outside history_scope, feed_held_since), or whose history is still being read or collection_state is not ok. An advisory published before its vendor's held_since may not be held, so no advisory from a vendor is not a finding that it published none. Past 30,000 characters of JSON, the first text block holds data cut to fit, and the note says what the cut leaves out and where to read it (TEXT CUT); so is structured data (DATA CUT), unless full: true. Cut, each row keeps vendor, vendor_advisory_id, title, severity and cve_ids at least, its strings and lists shortened.

    Input schema

    Input schema unchanged.

    3 unchanged entries
    • (schema root)
    • cve_id
    • full

    Output schema

    PropertyPrevious (3.2.4)Current (3.2.5)Change
    (schema root)object, oneOf (2)object, oneOf (2)
    • Changed: oneOf

    oneOf: [{"additionalProperties":{},"properties":{"coverage":{"anyOf":[{"additionalProperties":{},"properties":{"at_cap":{"description":"true: the answer is full, so the vendor feeds may hold more advisories for this CVE than it lists.","type":["bo… → [{"additionalProperties":{},"properties":{"coverage":{"anyOf":[{"additionalProperties":{},"properties":{"at_cap":{"description":"true: the answer is full, so the vendor feeds may hold more advisories for this CVE than it lists.","type":["bo… (truncated: full value in the exact JSON)

    Exact JSON from the published snapshots

    Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.

    Link to this tool
12 tools with no recorded change
  • check_affected
  • check_sbom
  • cve_exposure
  • cve_intel
  • cve_summary
  • epss_history
  • exposure_radar
  • get_cve
  • get_cwe
  • kev_recent
  • scan_manifest
  • search_cves

Evidence and provenance

Static findings
REVIEW from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
Human review
Pending human review. No reviewer decision is recorded for this comparison.
Published evidence
Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
Comparison
echelongraph-mcp/3.2.4~3.2.5The published comparison identifier.
Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 16, 2026, 9:36 PM UTC.
Distribution
npm
Previous release
echelongraph-mcp@3.2.416 tools · published by the registry Nov 12, 2026, 3:16 PM UTCArtifact integritysha512-H9GmrNOjyXIYZF64FMi1CTrXM1IVWWnBWTfjeoJWCRnHgl1iJqmHq3ZuN8kMRF1F2UugxtuaotXHKeQHFlLvrw==Interface fingerprintsha256:2ca204011fcd7ea89bf00cd4af7dfbf1052bf76e2844ce189b7bdb00ee27ef6dExact interface snapshot (JSON)
Current release
echelongraph-mcp@3.2.516 tools · published by the registry Nov 15, 2026, 1:28 AM UTCArtifact integritysha512-K+BEaSztAPZbBVijOExULJjSgH8R8QH0kWdxcSSrAVttUOk20opt9QGBDPmV315kQpFC/bslZR1Gnb9RZaOt7w==Interface fingerprintsha256:736d3b6a985361c1b6529a6a26a48439207009cecf86085276bda246328f1bc0Exact interface snapshot (JSON)

The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.

MODELARA ANALYSIS OUTPUT

Interface findings

Analyzed with Modelara v0.1.8 · Nov 16, 2026

Requires review

4 findings
  • cve_remediationREVIEWChanged

    Output schema changed

    Show details
    • output schema keywords changed: oneOf [{"additionalProper… → [{"additionalProper…
    Authority
    READREAD
    Authority unchanged
  • get_vendor_advisoryREVIEWChanged

    Output schema changed

    Show details
    • output schema keywords changed: oneOf [{"additionalProper… → [{"additionalProper…
    Authority
    READREAD
    Authority unchanged
  • search_vendor_advisoriesREVIEWChanged

    Output schema changed

    Show details
    • output schema keywords changed: oneOf [{"additionalProper… → [{"additionalProper…
    Authority
    READREAD
    Authority unchanged
  • vendor_advisories_for_cveREVIEWChanged

    Output schema changed

    Show details
    • output schema keywords changed: oneOf [{"additionalProper… → [{"additionalProper…
    Authority
    READREAD
    Authority unchanged

Informational

4 findings
  • cve_remediationINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • get_vendor_advisoryINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • search_vendor_advisoriesINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • vendor_advisories_for_cveINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
What do these results mean?
PASS
No policy-significant interface change detected.
REVIEW
Interface changes require inspection.
FAIL
A policy-significant change was detected.
INVALID
The comparison could not be evaluated reliably.
← Back to EchelonGraph CVE & Exposure release history