io.github.asume21/webear
NPM · WEBEAR · SCANNED AUG 3
Give your AI coding assistant ears — capture, analyze, and describe live audio.
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 Security42
- Malware check failed: a supply-chain vendor flagged a high-severity malware risk. See how to fix → Fail
- Only part of the dependency tree could be resolved (95 of 99), 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 (95 of 99), 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 32 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 247 tokens (~61/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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 · webear
claude mcp add asume21-webear -- npx -y webear
codex mcp add asume21-webear -- npx -y webear
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"asume21-webear": {
"type": "local",
"command": [
"npx",
"-y",
"webear"
],
"enabled": true
}
}
} openclaw mcp add asume21-webear --command npx --arg -y --arg webear
mcp_servers:
asume21-webear:
command: "npx"
args: ["-y", "webear"] {
"mcpServers": {
"asume21-webear": {
"command": "npx",
"args": [
"-y",
"webear"
]
}
}
} 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.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +31
- Malware scan: unverified → fail ▼ security
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 1 Aug 26 −7
- 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 −2
- Malware scan: fail → unverified ▼ security
- Malware indicator gptMalware:QQH-VokUc-IAQ8mLv_JNF-K_OKCEmXDV7-2jWLT3XMVY cleared ▲ security
- 27 Jul 26 30
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 none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 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.
analyze_audio ~55
Run signal analysis on a captured audio clip. Returns RMS, peak dB, clipping, spectral centroid, frequency band energy, estimated BPM, and timing jitter.
| Name | Type | Req | Description |
|---|---|---|---|
| capture_id | string | yes | The capture ID returned by capture_audio |
No output schema declared.
No examples provided.
capture_audio ~60
Record a short clip of what the running web app is currently outputting. Returns a capture ID you can pass to analyze_audio or describe_audio.
| Name | Type | Req | Description |
|---|---|---|---|
| duration_ms | number | — | How many milliseconds to record (default 3000, max 30000) |
No output schema declared.
No examples provided.
describe_audio ~60
Send a captured audio clip to Gemini or GPT-4o to get a plain-English description of what it sounds like — useful when something sounds wrong but you cannot describe it.
| Name | Type | Req | Description |
|---|---|---|---|
| capture_id | string | yes | The capture ID returned by capture_audio to describe |
No output schema declared.
No examples provided.
diff_audio ~72
Compare two audio captures and flag what changed — loudness, tone, timing, clipping. Use this before and after a code change to verify the audio impact.
| Name | Type | Req | Description |
|---|---|---|---|
| capture_id_a | string | yes | First capture ID (the "before") |
| capture_id_b | string | yes | Second capture ID (the "after") |
No output schema declared.
No examples provided.