io.github.uxloom-dev/uxloom
NPM · UXLOOM · SCANNED AUG 3
Agent-native UI/UX design validation: journey completeness, state coverage, and WCAG checks.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (97 of 101), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to uxloom-dev/uxloom). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 704 tokens (~58/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · uxloom
claude mcp add uxloom-dev-uxloom -- npx -y uxloom
codex mcp add uxloom-dev-uxloom -- npx -y uxloom
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"uxloom-dev-uxloom": {
"type": "local",
"command": [
"npx",
"-y",
"uxloom"
],
"enabled": true
}
}
} openclaw mcp add uxloom-dev-uxloom --command npx --arg -y --arg uxloom
mcp_servers:
uxloom-dev-uxloom:
command: "npx"
args: ["-y", "uxloom"] {
"mcpServers": {
"uxloom-dev-uxloom": {
"command": "npx",
"args": [
"-y",
"uxloom"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +69
- Install scripts: unverified → pass ▲ security
- Provenance: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- The attested source repository moved: uxloom-dev/uxloom security
- Schema quality: unverified → good ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
- 1 Aug 26 −23
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed npm/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- Source repo:
- uxloom-dev/uxloom
- Certificate issuer:
- https://token.actions.githubusercontent.com
- Certificate SAN:
- https://github.com/uxloom-dev/uxloom/.github/workflows/release.yml@refs/tags/v0.5.0
- Rekor log index:
- 2194865534
- Predicate type:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:e5cf2b539e8f65514ad9922a9ae453b397aae8ec3ccd030c20ac0101d011ca162f44ad6df7ec7e817d919ccf750e435d43a21660b94275aad86adff99
- Discovery method:
- attestation_endpoint
Dependencies 97 packages
97 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
brief_answer ~63
Submit brief answers. Unanswered fields take researched defaults and are recorded in the assumption ledger (auditable, reversible).
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | Question id → answer. Omit what you could not answer. |
| prompt | string | yes | Same prompt passed to brief_start |
No output schema declared.
No examples provided.
brief_start ~105
Start a design brief. Returns a structured questionnaire. Answer every question you can yourself — from the provided context document (PRD, spec) first, then conversation context; only relay questions marked askHuman:true to the user. Then call brief_answer.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | — | Existing product context if any: PRD, spec, or design doc contents. When provided, extract answers from it instead of asking. |
| prompt | string | yes | The product/design request, verbatim |
No output schema declared.
No examples provided.
coverage_report ~32
The demo number: screens delivered vs. states the journeys actually need. Returns per-screen coverage and the missing-state list.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
journey_define ~51
Add or replace a journey (a state machine: states reference screens, events move between states). Screens referenced here must be registered via screen_register before project_validate passes.
| Name | Type | Req | Description |
|---|---|---|---|
| journey | object | yes | The journey definition |
No output schema declared.
No examples provided.
palette_check ~73
Check a design system's color pairs against WCAG 2.2 AA (4.5:1) before any screens exist. Reports each pair's exact ratio, pass/fail, and thin-margin passes (under 5.0:1) that one shade lighter would break.
| Name | Type | Req | Description |
|---|---|---|---|
| pairs | array | yes | — |
No output schema declared.
No examples provided.
project_audit ~111
Audit the implementation against the design contract (drift detection). Static tiers: the uxloom.map.json screen registry and data-ux-screen/data-ux-state markers in source. Returns per-state verdicts (implemented with file:line evidence / unimplemented / unproven) and findings with fixes. When implementing screens from the contract, emit data-ux-state markers so the code stays self-auditing.
| Name | Type | Req | Description |
|---|---|---|---|
| root | string | — | Implementation root directory to scan (default: the project file's directory) |
No output schema declared.
No examples provided.
project_export ~27
Return the complete current project document (for inspection, backup, or transformation before a project_import).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
project_import ~63
Replace the whole project in one call: journeys and screens together. Prefer this over many journey_define/screen_register calls when registering a complete or large design. Validates the full document; unknown fields are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| project | object | yes | The complete JourneyGraph project document |
No output schema declared.
No examples provided.
project_init ~45
Create a new UXLoom project file (uxloom.project.json). Run once per product.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Product name |
| platforms | array | yes | Target platforms |
No output schema declared.
No examples provided.
project_validate ~51
Run every critic: journey completeness (unreachable states, dead ends, broken transitions), state coverage, WCAG contrast, touch targets, text expansion. Returns all findings with fixes. Iterate until errors = 0.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
screen_critique ~32
Findings scoped to a single screen. Use during iteration on one screen.
| Name | Type | Req | Description |
|---|---|---|---|
| screenId | string | yes | — |
No output schema declared.
No examples provided.
screen_register ~51
Add or replace a screen: its intent, requiredStates (the contract), designedStates (progress), and components with colors/labels/target sizes for the critics.
| Name | Type | Req | Description |
|---|---|---|---|
| screen | object | yes | The screen definition |
No output schema declared.
No examples provided.