developer-tools Static interface comparison

Hyperiux Vault

0.2.0 0.2.1

PASSAutomated static analysis

No policy-significant interface change 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.

Tools3 → 3
Added0
Removed0
Schema changes0
Input schema changes0
Output schema changes0
Unclassified schema changes0
Description changes1
New write authority0
New destructive authority0
New unknown authority0
AnalysisPASS

INTERFACE DIFF

What changed, tool by tool

Classification from the recorded findings · definitions from the published snapshots

1 tool with recorded changes

  1. hyperiux_get_effectModifiedDescriptionINFO

    What changed

    • hyperiux_get_effect: description changed.

    Why it could matter

    • Models choose and call tools partly from their descriptions.

    What to verify

    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousGet full details for one Hyperiux Vault effect by its exact slug - description, tier (free/pro), npm dependencies, version, changelog, and install instructions. Optionally includes full source code. Args: - name (string): exact effect slug - include_source (boolean, default false): also return component source. Free effects: always available. Pro effects: only if authenticated (see below). Returns JSON: { name, title, description, tier, version, dependencies, changelog, install_command, preview_url, import_path, target, main, import_statement, files: [{ path, content? }] } - changelog: array of { version, date, summary, breaking }, newest first - files[].content is omitted unless include_source=true AND the effect is accessible (free, or Pro with a valid token) - import_statement is the exact import line to use after installing (e.g. `import { DottedGrid } from "@/components/effects/dotted-grid";`), built from exportKind/exportName/import_path the same way the CLI's own `hyperiux add` output does - omitted if the registry entry has no import_path Pro effects without a token: the response still includes metadata (description, dependencies, changelog) but files have no content, and a note explains the effect requires a Hyperiux Pro account - don't treat this as an error, it's expected for unauthenticated Pro lookups. Examples: - "What does the dotted-grid effect need?" -> name="dotted-grid" (dependencies field) - "Show me the code for circle-text-reveal" -> name="circle-text-reveal", include_source=true - Don't use when: you don't have an exact slug yet - use hyperiux_list_effects first. Error Handling: - Returns "Effect '<name>' not found" if the slug doesn't exist - check hyperiux_list_effects for the correct spelling.
    CurrentGet full details for one Hyperiux Vault effect by its exact slug - description, tier (free/pro), npm dependencies, version, changelog, and install instructions. Optionally includes full source code. Args: - name (string): exact effect slug - include_source (boolean, default false): also return component source. Free effects: always available. Pro effects: only if authenticated (see below). Returns JSON: { name, title, description, tier, version, dependencies, changelog, install_command, preview_url, import_path, target, main, import_statement, files: [{ path, content? }] } - changelog: array of { version, date, summary, breaking }, newest first - files[].content is omitted unless include_source=true AND the effect is accessible (free, or Pro with a valid token) - import_statement is the exact import line to use after installing (e.g. `import { DottedGrid } from "@/components/effects/dotted-grid";`), built from exportKind/exportName/import_path the same way the CLI's own `hyperiux add` output does - omitted if the registry entry has no import_path - install_limit/install_remaining: present on a normal (non-rate-limited) lookup, telling you how many more distinct effects this identity can fetch today - mention this to the user when remaining is low, same as the website's copy toast and the CLI's own "N of M daily installs left" line Pro effects without a token: the response still includes metadata (description, dependencies, changelog) but files have no content, and a note explains the effect requires a Hyperiux Pro account - don't treat this as an error, it's expected for unauthenticated Pro lookups. Free effects past the caller's daily install cap: the response still includes metadata but files have no content, and rate_limited/rate_limit_reason explain the daily limit and when to retry - also not an error, it's expected once the cap is hit. Examples: - "What does the dotted-grid effect need?" -> name="dotted-grid" (dependencies field) - "Show me the code for circle-text-reveal" -> name="circle-text-reveal", include_source=true - Don't use when: you don't have an exact slug yet - use hyperiux_list_effects first. Error Handling: - Returns "Effect '<name>' not found" if the slug doesn't exist - check hyperiux_list_effects for the correct spelling.

    Input schema

    Input schema unchanged.

    3 unchanged entries
    • (schema root)
    • include_source
    • name

    No output schema is recorded for this tool in either release.

    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 tools with no recorded change
  • hyperiux_list_categories
  • hyperiux_list_effects

Evidence and provenance

Static findings
PASS from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
Human review
Automated static analysis. 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
hyperiux-immersion-labs-hyperiux-mcp-server/0.2.0~0.2.1The published comparison identifier.
Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 17, 2026, 12:39 AM UTC.
Distribution
npm
Previous release
hyperiux-mcp-server@0.2.03 tools · published by the registry Sep 21, 2026, 7:19 AM UTCArtifact integritysha512-YauDVQRw99MyUwsPtTXeV0weZW0xXmeYMXna1DXCK0eYuuP15F2CQsgZNeWlAxBFf2DmfR2DilbhY9VLWup1tw==Interface fingerprintsha256:6b1d7c9b74db11d8b6f17fddb3b91f2bf003d71404932718c3b2ad2012420419Exact interface snapshot (JSON)
Current release
hyperiux-mcp-server@0.2.13 tools · published by the registry Sep 21, 2026, 9:12 AM UTCArtifact integritysha512-U9zvC136AJJ55EomqcfZTLxukReTWU8TaGP7RhmyLJOVXIrkEiEP85pdScR500eS5cRr+u6/BuIcSAmbAig1ZQ==Interface fingerprintsha256:4b4f13e9c72a32cdb7b659b0439e30a9c52b6c6916202d89c5723684a68980daExact 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 17, 2026

Informational

1 finding
  • hyperiux_get_effectINFOChanged

    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 Hyperiux Vault release history