candor-ui@4.0.1
CAUTION· install onlyPublisher claims: "Build agent product UIs with Candor UI, a shadcn/ui registry of React components for agents that do real work - chat, tool calls, plans, approvals, diffs, run logs, traces, evals, admin and the app shell around them. Use when building or changing a React or Next.js interface for an AI agent, when the project's components.json lists the @candor registry, or when the user mentions Candor. Covers installing components, choosing the right one, wiring the Vercel AI SDK, Claude Agent SDK or AG-UI adapter, and the honesty rules every Candor screen follows." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-11 and scored it 77/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; HTML comment carrying imperative instructions to the agent. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
- **Updates:** `npx candor-ui update` brings installed items to the latest release and keeps local changes with aFix: Pin versions and sources; vendor anything fetched at install time.- **Pro and Premium items** need the buyer's licence key. The person runs `npx candor-ui key <key>` themselves (itFix: Pin versions and sources; vendor anything fetched at install time.goes in `.env.local`, which must stay out of git); never ask for the key in chat or put it in a file you write. InFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.npx candor-ui add thread message composerFix: Pin versions and sources; vendor anything fetched at install time.- **When something looks wrong:** `npx candor-ui doctor` checks the registry, the key, the theme import, dark mode,Fix: Pin versions and sources; vendor anything fetched at install time.npx candor-ui@latest init --yes # registry in components.json, the theme, its import; sets up shadcn if missingFix: Pin versions and sources; vendor anything fetched at install time.GENERATED by scripts/build-design.mjs from src/styles/candor.css and src/styles/candor-theme.css. Change the CSS (colours: scripts/theme.mjs), then run npm run Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
3 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim arunk3: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.