developer-tools Static interface comparison

Hyperiux Vault

0.2.1 0.3.0

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.

Tools3 → 3
Added0
Removed0
Schema changes2
Input schema changes2
Output schema changes0
Unclassified schema changes0
Description changes2
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. hyperiux_get_effectModifiedSchemaDescriptionREVIEWINFO

    What changed

    • hyperiux_get_effect — Schema change: input property include_source changed: description "Include full compo… → "Include full compo….
    • hyperiux_get_effect — Schema change: input property name changed: description "Exact effect slug,… → "Exact effect slug,….
    • hyperiux_get_effect: description changed.

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • 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 - 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.
    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. Needs a signed-in account for every effect (see below) and counts as one of the day's installs; details-only lookups (false) don't. 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 caller is signed in (and on Pro, for a Pro effect) - 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 No token (or an invalid one) with include_source=true: the response still includes metadata, but files have no content and sign_in_required/sign_in_required_reason tell the user to run `npx hyperiux login` - every install needs a free account. Don't retry; ask the user to sign in. Pro effects without a Pro subscription: metadata only, and source_locked explains the effect needs Hyperiux Pro - expected, not an error. 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 dotted-grid" -> name="dotted-grid", 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

    PropertyPrevious (0.2.1)Current (0.3.0)Change
    include_sourceboolean, default=falseoptionalboolean, default=falseoptional
    • Description changed
    namestring, minLength=1requiredstring, minLength=1required
    • Description changed
    1 unchanged entry
    • (schema root)

    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. hyperiux_list_effectsModifiedSchemaDescriptionREVIEWINFO

    What changed

    • hyperiux_list_effects — Schema change: input property category changed: description "Filter to one cate… → "Filter to one cate….
    • hyperiux_list_effects: description changed.

    Why it could matter

    • Calls or consumers built for the earlier schema may need to change.
    • Models choose and call tools partly from their descriptions.

    What to verify

    • Validate representative existing tool calls against the new argument schema.
    • Spot-check that agents still select this tool as intended.
    Declared effect
    read → read
    Description
    PreviousBrowse or search the Hyperiux Vault catalog of React/Next.js interaction effects (scroll systems, cursor trails, WebGL scenes, animated buttons, page transitions, etc). Does NOT return which effects are Pro vs Free - the catalog index this reads from doesn't carry that field today. Use hyperiux_get_effect on a specific slug to check its tier before assuming it's installable without a Hyperiux Pro account. Args: - query (string, optional): substring match against effect name - category (string, optional): filter to one category slug - limit (number, default 30, max 100) - offset (number, default 0) Returns JSON: { total, count, offset, effects: [{ name, category, categories, dependencies, version }], has_more, next_offset? } Examples: - "What cursor effects are available?" -> category="cursor" - "Is there anything with 'particles' in the name?" -> query="particles" - Don't use when: you need one effect's full description/props/tier - use hyperiux_get_effect instead.
    CurrentBrowse or search the Hyperiux Vault catalog of React/Next.js interaction effects (scroll systems, cursor trails, WebGL scenes, animated buttons, page transitions, etc). Each result includes tier ("free" or "pro") - use this to answer "how many free/pro effects are there" or "which of these are free" directly from one call, by filtering/counting the returned list yourself. Don't estimate or guess these counts, and don't call hyperiux_get_effect per-item just to total them up - it's unnecessary here. hyperiux_get_effect is still the right call for one specific effect's full description/props/changelog. Args: - query (string, optional): substring match against effect name - category (string, optional): filter to one category slug - limit (number, default 30, max 100) - offset (number, default 0) Returns JSON: { total, count, offset, effects: [{ name, category, categories, dependencies, version, tier }], has_more, next_offset? } Examples: - "What cursor effects are available?" -> category="cursor" - "Is there anything with 'particles' in the name?" -> query="particles" - "How many free effects are there?" -> call with a limit high enough to cover total (check total/has_more first), then count tier === "free" yourself. - Don't use when: you need one effect's full description/props/changelog - use hyperiux_get_effect instead.

    Input schema

    PropertyPrevious (0.2.1)Current (0.3.0)Change
    categorystringoptionalstringoptional
    • Description changed
    4 unchanged entries
    • (schema root)
    • limit
    • offset
    • query

    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
1 tool with no recorded change
  • hyperiux_list_categories

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
hyperiux-immersion-labs-hyperiux-mcp-server/0.2.1~0.3.0The 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.13 tools · published by the registry Sep 21, 2026, 9:12 AM UTCArtifact integritysha512-U9zvC136AJJ55EomqcfZTLxukReTWU8TaGP7RhmyLJOVXIrkEiEP85pdScR500eS5cRr+u6/BuIcSAmbAig1ZQ==Interface fingerprintsha256:4b4f13e9c72a32cdb7b659b0439e30a9c52b6c6916202d89c5723684a68980daExact interface snapshot (JSON)
Current release
hyperiux-mcp-server@0.3.03 tools · published by the registry Oct 19, 2026, 12:43 PM UTCArtifact integritysha512-8ux6N3Jat79Dla+IcEHOk7MUC5s9cLhm+XUXcv0Zfbq7BWXDcenp0q/HnXztfJu+gzFL/8gZG4nwJ4F/6qW5Xg==Interface fingerprintsha256:7a35236c81de388023ef0a8f90ed77a57ba85dc5708d64b53e429060dba41f99Exact 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

Requires review

2 findings
  • hyperiux_get_effectREVIEWChanged

    Input schema changed

    Show details
    • input property include_source changed: description "Include full compo… → "Include full compo…
    • input property name changed: description "Exact effect slug,… → "Exact effect slug,…
    Authority
    READREAD
    Authority unchanged
  • hyperiux_list_effectsREVIEWChanged

    Input schema changed

    Show details
    • input property category changed: description "Filter to one cate… → "Filter to one cate…
    Authority
    READREAD
    Authority unchanged

Informational

2 findings
  • hyperiux_get_effectINFOChanged

    Description changed

    Authority
    READREAD
    Authority unchanged
  • hyperiux_list_effectsINFOChanged

    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