developer-tools Static interface comparison
viberank
1.1.0 1.2.0
1 new unknown capability requires explicit review.
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
- 1Added tools
- 0Removed tools
- 4Modified tools
- 4Input-schema changes
- 0Output-schema changes
- 1Declared authority changes
5 tools with recorded changes
get_leaderboardModifiedWhat changed
- get_leaderboard — Schema change: input property added: tool.
- get_leaderboard — Input type change: property limit changed: description "Number of top user… → "How many top entri…, +maximum=50, +minimum=1, type "number" → "integer".
- get_leaderboard: description changed.
Why it could matter
- Calls or consumers built for the earlier schema may need to change.
- Arguments of the old type may no longer validate against the new schema.
- 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
- unknown → unknown
- Description
- PreviousGet current Viberank leaderboard rankings
- CurrentThe current viberank leaderboard, ranked by API-equivalent cost. Each entry has rank, username, totalCost (USD), totalTokens, tools, verified, underReview and profileUrl. Pass tool to rank only the users of one tool; get_stats lists the tool slugs.
Input schema
Property Previous (1.1.0) Current (1.2.0) Change limitnumber, default=10optional integer, default=10, maximum=50, minimum=1optional - Description changed
- Constraint: maximum
- Constraint: minimum
- Type changed
maximum: — → 50minimum: — → 1type: "number" → "integer"toolnot present stringoptional - Added
1 unchanged entry
(schema root)
No output schema is recorded for this tool in either release.
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.
get_profileModifiedWhat changed
- get_profile — Schema change: input property username changed: description "GitHub username to… → "The GitHub usernam….
- get_profile: 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
- unknown → unknown
- Description
- PreviousGet Viberank profile for a specific user
- CurrentOne developer's viberank profile: global rank, total cost and tokens, days tracked, tools and whether it is verified. Profiles are keyed by GitHub username. Returns found: false when there's no such profile.
Input schema
Property Previous (1.1.0) Current (1.2.0) Change usernamestringrequired stringrequired - Description changed
1 unchanged entry
(schema root)
No output schema is recorded for this tool in either release.
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.
get_statsAddedWhat changed
- New tool get_stats, declared with unknown effect.
Why it could matter
- Valyd could not determine this tool’s effect from its declared interface, so its authority is not known.
What to verify
- Read the tool’s documentation and schema before allowing agents to use it.
- Declared effect
- — → unknown
Input schema
Property Previous (1.1.0) Current (1.2.0) Change (schema root)not present object - Added
No output schema is recorded for this tool in either release.
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.
get_usageModifiedWhat changed
- get_usage — Schema change: input property force_refresh changed: description "Force refresh the … → "Re-run ccusage ins….
- get_usage: 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
- unknown → unknown
- Description
- PreviousGet current Claude Code usage statistics from ccusage
- CurrentRead the user's local AI coding usage (Claude Code, Codex, Gemini CLI, OpenCode and the other tools ccusage supports) by running ccusage@20 on this machine. Returns a summary: API-equivalent cost in USD, tokens, days tracked, date range and cost per tool. Sends nothing anywhere. Can take a minute on a long history; results are cached for 5 minutes.
Input schema
Property Previous (1.1.0) Current (1.2.0) Change force_refreshboolean, default=falseoptional boolean, default=falseoptional - Description changed
1 unchanged entry
(schema root)
No output schema is recorded for this tool in either release.
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.
submit_to_viberankModifiedWhat changed
- submit_to_viberank — Schema change: input property removed: auto_detect_username.
- submit_to_viberank — Schema change: input property github_username changed: description "GitHub username fo… → "The user's own Git….
- submit_to_viberank: 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
- unknown → unknown
- Description
- PreviousSubmit Claude Code usage statistics to Viberank leaderboard
- CurrentUpload the user's local usage to the public viberank.app leaderboard. Call it only when the user asked to submit. With a VIBERANK_TOKEN configured, the submission is verified and filed under the token's account, so leave github_username out. Without a token, github_username is required and must be the user's own GitHub handle, confirmed with them, because it becomes a public profile. Called without one, it uploads nothing and suggests a handle to confirm with the user before calling again. On success it returns rank, tier and a README badge you can offer to add.
Input schema
Property Previous (1.1.0) Current (1.2.0) Change auto_detect_usernameboolean, default=trueoptional not present - Removed
github_usernamestringoptional stringoptional - Description changed
1 unchanged entry
(schema root)
No output schema is recorded for this tool in either release.
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.
Evidence and provenance
- Static findings
- FAIL 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
sculptdotfun-viberank/1.1.0~1.2.0The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 17, 2026, 12:37 AM UTC.- Distribution
npm- Previous release
viberank-mcp@1.1.04 tools · published by the registry Sep 23, 2026, 2:08 PM UTCArtifact integritysha512-AU0pldYLVMNYik1ZNy0IPkM0/y4cYFArRSMNxaqXV/FU4iI3Ui4ce1ouZSeHongUr/emek93eAJ925Ei/7dxMw==Interface fingerprintsha256:bcfd0dedfe504074221eb9f7cafa5849542bc8d2eadbdfe5915cb49b3baa5ceaExact interface snapshot (JSON)- Current release
viberank-mcp@1.2.05 tools · published by the registry Oct 26, 2026, 10:34 AM UTCArtifact integritysha512-5RPCmOY9h5WBSMvruYK8wP+RveRkpXF4gTVuxekYjeTm0mI1VciLmiBQxCzWxqzj9fBns3CgTYPgudf5H0YSgg==Interface fingerprintsha256:7db9b6f50bd880bb9b639a4694d9faea8a2c4bd5faa9bff1654101a30d4e11bbExact 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
Policy failures
1 findingget_statsFAILAdded
Requires review
4 findingsget_leaderboardREVIEWChangedShow details
input property added: toolinput property limit changed: description "Number of top user… → "How many top entri…, +maximum=50, +minimum=1, type "number" → "integer"
get_profileREVIEWChangedShow details
input property username changed: description "GitHub username to… → "The GitHub usernam…
get_usageREVIEWChangedShow details
input property force_refresh changed: description "Force refresh the … → "Re-run ccusage ins…
submit_to_viberankREVIEWChangedShow details
input property removed: auto_detect_usernameinput property github_username changed: description "GitHub username fo… → "The user's own Git…
Informational
4 findingsget_leaderboardINFOChangedget_profileINFOChangedget_usageINFOChangedsubmit_to_viberankINFOChanged
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.