developer-tools Static interface comparison

CodeBurn

0.9.27 0.9.28

REVIEWPending human review

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.

Tools2 → 2
Added0
Removed0
Schema changes2
Input schema changes1
Output schema changes1
Unclassified schema changes0
Description changes0
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

2 tools with recorded changes

  1. get_savingsModifiedSchemaREVIEW

    What changed

    • get_savings — Schema change: input schema keywords changed: -additionalProperties.

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    Declared effect
    read → read

    Input schema

    PropertyPrevious (0.9.27)Current (0.9.28)Change
    (schema root)object, additionalProperties=falseobject
    • Constraint: additionalProperties

    additionalProperties: false → —

    2 unchanged entries
    • include_project_names
    • period

    Output schema

    Output schema unchanged.

    12 unchanged entries
    • (schema root)
    • optimize
    • optimize › findingCount
    • optimize › savingsUSD
    • optimize › topFindings
    • optimize › topFindings › [items]
    • optimize › topFindings › [items] › impact
    • optimize › topFindings › [items] › savingsUSD
    • optimize › topFindings › [items] › title
    • period
    • retryTaxUSD
    • routingWasteUSD
    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_usageModifiedSchemaREVIEW

    What changed

    • get_usage — Schema change: input schema keywords changed: -additionalProperties.
    • get_usage — Output schema: property totals changed: properties {"cacheHitPercent":… → {"cacheHitPercent":….

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.
    • Code or prompts that read this tool’s results may receive a different shape.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Check consumers of this tool’s output against the new schema.
    Declared effect
    read → read

    Input schema

    PropertyPrevious (0.9.27)Current (0.9.28)Change
    (schema root)object, additionalProperties=falseobject
    • Constraint: additionalProperties

    additionalProperties: false → —

    4 unchanged entries
    • by
    • include_project_names
    • limit
    • period

    Output schema

    PropertyPrevious (0.9.27)Current (0.9.28)Change
    totals › costBasisnot presentobject, additionalProperties=falseoptional
    • Added
    totals › costBasis › calculatednot presentnumberoptional
    • Added
    totals › costBasis › estimatednot presentnumberoptional
    • Added
    totals › costBasis › recordednot presentnumberoptional
    • Added
    11 unchanged entries
    • (schema root)
    • breakdown
    • empty
    • period
    • totals
    • totals › cacheHitPercent
    • totals › calls
    • totals › costUSD
    • totals › estimatedCostUSD
    • totals › oneShotRate
    • totals › sessions
    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

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
getagentseal-codeburn/0.9.27~0.9.28The published comparison identifier.
Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 16, 2026, 9:40 PM UTC.
Distribution
npm
Previous release
codeburn@0.9.272 tools · published by the registry Oct 11, 2026, 7:42 AM UTCArtifact integritysha512-dNCy09sYCdvrijcoOun+ZVyTbp/GYGmdBbBTe8uTSLRO8rSWqS4IEOzQdRoPRhbt7twCuSqVBjTNNl+CdTNrKQ==Interface fingerprintsha256:a5beb4fe013dea116664a08d05f7d352051fceec3b2fe22639b0dbb2a9319309Exact interface snapshot (JSON)
Current release
codeburn@0.9.282 tools · published by the registry Nov 8, 2026, 1:37 AM UTCArtifact integritysha512-fl9u2m2n8n+cY6FheIY/jthw4GeuUtM38NfX3KR3Ljj2X7GFcUCfCGeRrnIaaM+aqmMLOw70Uy2BGnzoQgQlPQ==Interface fingerprintsha256:b5753d9f2d7a04a733aa034f03fbe3e206dc27e992ea9ad24eacb67df65f475dExact 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

2 findings
  • get_savingsREVIEWChanged

    Input schema changed

    Show details
    • input schema keywords changed: -additionalProperties
    Authority
    READREAD
    Authority unchanged
  • get_usageREVIEWChanged

    Input and output schema changed

    Show details
    • input schema keywords changed: -additionalProperties
    • output property totals changed: properties {"cacheHitPercent":… → {"cacheHitPercent":…
    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 CodeBurn release history