Umbra
NPM · @ELBERACASA/UMBRA · SCANNED AUG 7
Trust score for AI-generated code: scan repos, guard agent file writes, get a 0-100 score.
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
- Known CVEs were checked across the 96 of 100 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 96 of 100 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 411 tokens (~137/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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 · @elberacasa/umbra
claude mcp add elberacasa-umbra -- npx -y @elberacasa/umbra
codex mcp add elberacasa-umbra -- npx -y @elberacasa/umbra
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"elberacasa-umbra": {
"type": "local",
"command": [
"npx",
"-y",
"@elberacasa/umbra"
],
"enabled": true
}
}
} openclaw mcp add elberacasa-umbra --command npx --arg -y --arg @elberacasa/umbra
mcp_servers:
elberacasa-umbra:
command: "npx"
args: ["-y", "@elberacasa/umbra"] {
"mcpServers": {
"elberacasa-umbra": {
"command": "npx",
"args": [
"-y",
"@elberacasa/umbra"
]
}
}
} 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.
- 5 Aug 26 +30
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 4 Aug 26 35
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 7 Aug 2026 · Analysed npm/@elberacasa/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Deprecated | 96 |
| Stale | 29 |
| Tree resolution | Partial |
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.
get_score ~61
Fast static Umbra Trust Score (0-100) for a repository — SAFE and CLEAN axes only, no network, no sandbox. Use scan_repo for the full report with findings.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | (required) Path to the repository to score |
No output schema declared.
No examples provided.
guard_content ~120
Check a proposed file write against the Umbra guard engine BEFORE writing. Returns the guard verdict as JSON: decision (allow/warn/block), findings with file:line evidence, and pathViolation when a protected path (e.g. .git/hooks) is targeted. On block, do not write — fix the content and re-check.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | (required) Full proposed content — the new file content, or the replacement string for an edit |
| file_path | string | – | (required) Path of the file about to be written |
No output schema declared.
No examples provided.
scan_repo ~102
Scan a repository and return the full Umbra Trust Score report as JSON (SAFE/CLEAN static findings; deep=true also verifies RUNS and HONEST in a Docker sandbox). Call before declaring a task done — a score below 50 means the work is not done.
| Name | Type | Req | Description |
|---|---|---|---|
| deep | boolean | – | Also verify RUNS and HONEST in a Docker sandbox (slower, needs Docker) |
| path | string | – | (required) Path to the repository to scan |
No output schema declared.
No examples provided.