infrastructure Static interface comparison
EchelonGraph CVE & Exposure
3.2.3 3.2.4
2 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.
INTERFACE DIFF
What changed, tool by tool
- 0Added tools
- 0Removed tools
- 2Modified tools
- 0Input-schema changes
- 2Output-schema changes
- 0Declared authority changes
2 tools with recorded changes
cve_exposureModifiedWhat changed
- cve_exposure — Output schema: schema keywords changed: oneOf [{"additionalProper… → [{"additionalProper….
- cve_exposure: 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
- PreviousInternet-exposure footprint for one CVE from EchelonGraph's KEV-exposure radar: how many internet-facing services (distinct ip:port, returned as exposed_hosts; a machine answering on two ports counts twice) the radar has on record running a version its CVE matcher maps to this CVE, with a country/product breakdown and a ransomware flag. Aggregate and host-redacted; free and keyless. Method: exposure counts are derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). Every 12 h, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service whose row has not been written or refreshed for 21 days is dropped. The radar only looks for its tracked set of CVEs: for a CVE outside that set the note says NOT ASSESSED (exposure_state not_assessed), and its 0 is not a measurement. last_seen is when EchelonGraph last wrote or refreshed a service's row, not when the service was observed: a port still listed by Shodan InternetDB refreshes it without re-reading the banner, so a patched service can stay counted while its port stays open. A count is therefore a banner-version inference over a sample, not an exploit test and not an internet-wide census. Its structured result's state is not_assessed with measured_at null, since the answer dates no observation; the count is still relayed, labelled, as what the radar holds on record. exposure_state says what the count is: exposed, measured_zero, not_assessed or tracking_unknown; coverage.in_scope is the API's tracked verdict; freshness is null; data is the API's JSON. 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.
- CurrentInternet-exposure footprint for one CVE from EchelonGraph's KEV-exposure radar: how many internet-facing services (distinct ip:port, as exposed_hosts; a machine answering on two ports counts twice) the radar has on record running a version that maps to this CVE, with a breakdown by product and by hosting country (Shodan's IP geolocation, not necessarily the operator's location) and a ransomware flag. Aggregate, host-redacted, free, keyless. Method: exposure counts are derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). Every 12 h, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service whose banner version matches a CISA-KEV or high-EPSS CVE; a row not written or refreshed for 21 days is dropped. The radar only looks for its tracked set of CVEs: for a CVE outside that set the note says NOT ASSESSED (exposure_state not_assessed), and its 0 is not a measurement. last_seen is when EchelonGraph last wrote or refreshed a service's row, not when the service was observed: a port still listed by Shodan InternetDB refreshes it without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census. Its structured result's state is not_assessed with measured_at null, since the answer dates no observation; the count is still relayed, labelled, as what the radar holds on record. exposure_state says what the count is: exposed, measured_zero, not_assessed or tracking_unknown; coverage.in_scope is the API's tracked verdict; freshness is null; data is the API's JSON. 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.
Input schema
Input schema unchanged.
3 unchanged entries
(schema root)cve_idfull
Output schema
Property Previous (3.2.3) Current (3.2.4) Change (schema root)object, oneOf (2) object, oneOf (2) - Changed: oneOf
oneOf: [{"additionalProperties":{},"properties":{"coverage":{"anyOf":[{"additionalProperties":{},"properties":{"in_scope":{"description":"The API's tracked verdict: whether the CVE is in the radar's tracked set; null when the answer does not say."… → [{"additionalProperties":{},"properties":{"coverage":{"anyOf":[{"additionalProperties":{},"properties":{"in_scope":{"description":"The API's tracked verdict: whether the CVE is in the radar's tracked set; null when the answer does not say."… (truncated: full value in the exact JSON)Link to this toolExact 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.
exposure_radarModifiedWhat changed
- exposure_radar — Output schema: schema keywords changed: oneOf [{"additionalProper… → [{"additionalProper….
Why it could matter
- Code or prompts that read this tool’s results may receive a different shape.
What to verify
- Check consumers of this tool’s output against the new schema.
- Declared effect
- read → read
Input schema
Input schema unchanged.
2 unchanged entries
(schema root)full
Output schema
Property Previous (3.2.3) Current (3.2.4) Change (schema root)object, oneOf (2) object, oneOf (2) - Changed: oneOf
oneOf: [{"additionalProperties":{},"properties":{"coverage":{"anyOf":[{"additionalProperties":{},"properties":{"answered":{"description":"The radars that answered. On a failure their answers are withheld.","items":{"type":"string"},"type":"array"}… → [{"additionalProperties":{},"properties":{"coverage":{"anyOf":[{"additionalProperties":{},"properties":{"answered":{"description":"The radars that answered. On a failure their answers are withheld.","items":{"type":"string"},"type":"array"}… (truncated: full value in the exact JSON)Link to this toolExact 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.
No tools match these filters.
14 tools with no recorded change
check_affectedcheck_sbomcve_intelcve_remediationcve_summaryepss_historyget_cveget_cweget_vendor_advisorykev_recentscan_manifestsearch_cvessearch_vendor_advisoriesvendor_advisories_for_cve
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.3~3.2.4The 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.316 tools · published by the registry Nov 11, 2026, 4:45 PM UTCArtifact integritysha512-IL1JvhPkEzxO2PIQGejBfPWHVkSCjBHnX7OKWdBPRVZGvU5n2T0iOqlHuxze/WPmPTvYHEsagrCJfeGoDOWEsw==Interface fingerprintsha256:6a418fa291d98d2912d0a9e57f30f407dd149a8cf7209eada787afd0a9c998e1Exact interface snapshot (JSON)- Current 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)- Comparison record
- Exact comparison record (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
Requires review
2 findingscve_exposureREVIEWChangedShow details
output schema keywords changed: oneOf [{"additionalProper… → [{"additionalProper…
exposure_radarREVIEWChangedShow details
output schema keywords changed: oneOf [{"additionalProper… → [{"additionalProper…
Informational
1 findingcve_exposureINFOChanged
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.