Loading the registry…
MCP server for managing Espanso text expansion configurations
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- espanso-mcp
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
7 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.6s
v2.0.11
14 findings · 7.5s
v0.3.74
5 findings · 1.1s
v0.1.0
0 findings · 3.2s
v0.1.0
0 findings · 3.2s
v0.71.0
13 findings · 0.2s
v2.3.8
13 findings · 7.3s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 2.0s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged44 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 45 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 26 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
11 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/src/handlers/config.ts, /repo/src/handlers/documentation.ts, /repo/src/handlers/matches.ts · reported by cisco-skill-scanner
1 AAK-OAUTH-3P-001
Files: package.json · reported by agent-audit-kit
1 CVE-2025-64718
Files: package-lock.json · reported by trivy
1 CVE-2026-33750
Files: package-lock.json · reported by trivy
1 CVE-2026-53550
Files: package-lock.json · reported by trivy
1 GHSA-f886-m6hf-6m8v
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-h67p-54hq-rp68
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mh29-5h37-fv8m
Files: /repo/package-lock.json · reported by osv-scanner
1 LOW_ANALYZABILITY
Files: /repo · reported by cisco-skill-scanner
23 The model's answer could not be read.
Rules: AAK-LEGAL-001, GHSA-7r86-cg39-jmmj, GHSA-w48q-cv73-mx4w and 19 more · Files: package.json, /repo/package-lock.json, package-lock.json and 1 more · reported by agent-audit-kit, osv-scanner, trivy
3 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: AAK-SEC-MD-001, SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: SECURITY.md, /repo/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
Artifact contains multiple high-severity vulnerabilities and insecure configurations.
The artifact's installed code includes high-severity vulnerabilities in its dependencies, identified in `package-lock.json`. It also exhibits potential for DNS rebind attacks via `package.json` and uses an Anthropic SDK in `src/server.ts`, which may involve external data transmission. Additionally, multiple findings in `src/handlers/config.ts`, `src/handlers/documentation.ts`, and `src/handlers/matches.ts` indicate potential for insecure configurations or sensitive data handling.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
Showing 11 of 11; the rest are in the per-scanner reports above.