Releases: chainswarm/chain-insights
Release list
v0.24.2
What's Changed
Full Changelog: v0.24.1...v0.24.2
v0.24.1
What's Changed
Full Changelog: v0.24.0...v0.24.1
v0.24.0
What's Changed
Full Changelog: v0.23.0...v0.24.0
v0.22.3
What's Changed
Full Changelog: v0.22.2...v0.22.3
v0.22.2
What's Changed
- build(deps): bump anchore/sbom-action from 0.24.0 to 0.24.1 by @dependabot[bot] in #351
- fix: align hosted MCP tests with production by @aph5nt in #352
Full Changelog: v0.22.1...v0.22.2
v0.8.22
0.8.22
aml_address_risklabel reads are deterministic: the label subset feeding
the risk level is now ordered by recency before the LIMIT, so the reported
level no longer varies between runs for label-heavy identities.- Risk precedence hardening: labels remain the leading signal, but a
lower-severity label no longer suppresses a more severe usable ML band —
the response reports the more severe band with anml_label_divergence
driver. An AML triage verdict never fails toward "looks safe".
Since 0.8.19
- 0.8.20: removed the legacy
--remoteflag fromcia mcp aml-address-risk/aml-trace-victim-funds(the AML tools have been
client-side composed for a while; the flag was dead). - 0.8.21: removed the dead legacy
mcpEndpoint/mcpAuthTokenconfig
keys pre-datinggraphMcpEndpoint; the installer now seeds the live
endpoint. All AML/debug/test/paid flows were already ongraphMcp*and
are unaffected.
Artifact integrity
sha256(chain-insights-0.8.22.tgz) = e86169d0c5091645a9d24f50d8d05deb55ad63d08309689e9d9ac9e7dfb63906
v0.8.19
0.8.19
- The Chain Insights Graph's ML verdict now includes an explicit abstention
band:risk_level = UNSCOREDmeans the model had too little labeled graph
context to stand behind a severity. Chain Insights treats it as "no
stance", never low risk:aml_address_riskstops deriving a severity from
an abstained ML score (falls back to label/exchange-exposure signal, adds
anml_abstaineddriver andml_verdict: unscored, and reports
level: unscoredwhen no other signal exists), and trace/report graph
payloads normalizerisk_levelcasing (HIGH→high) so the graph
app's risk borders fire regardless of backend casing whileunscored
renders with the neutral border.
See CHANGELOG.md for the full history since the last GitHub Release
(v0.3.9): versions 0.3.10 – 0.8.18 shipped on main without release
artifacts; this release re-establishes the artifact + checksum chain.
Artifact integrity
sha256(chain-insights-0.8.19.tgz) = ab8f05be328c8195bfa47d481f9be9fd0277788620fce5d4459cff9625e63271
v0.3.9
Chain Insights v0.3.9
- Adds
cia update/chain-insights updatebacked by the public npmjs registry. - Prompts interactive
cia initusers when a newer npm release is available. - Publishes the current
mainpackage, including the unreleased 0.3.8 staging test-key header support and stateless ACP proxy mode.
Verification before release:
- npm run release:check
- npm ci --ignore-scripts --audit=false --fund=false
- npm run typecheck
- npm run build
- npm test
- npm pack --silent | tar -tf
- PR #63 checks passed.
v0.3.7
Chain Insights 0.3.7
Docs-only release that standardizes hosted GraphRAG MCP access wording as the daily free tier.
- Public access is described as 10 execution seconds per IP per UTC day for bounded graph_query reads.
- Wallet users receive the daily free tier first, then continue via x402 for sustained usage.
- Removes demo/trial/preview-style framing from the public docs surfaces touched in this release.
Verification before release:
- npm run release:check
- npm test -- tests/skills-contract.test.ts tests/mcp-client.test.ts tests/cli-mcp.test.ts
- GitHub PR #57 checks green: Typecheck/Test/Build/Pack, security, CodeQL, Scorecard, Socket.
chain-insights v0.3.6
Summary
- Clarifies the public GraphRAG MCP demo path: 10 execution seconds per IP per UTC day for bounded single graph_query reads.
- Documents that prepared wallet users receive the daily grant first, then x402 continues automatically.
- Records staging UAT evidence for the free quota and free-to-paid handoff.