no-slop-ui@0.7.0
CAUTION· static onlyPublisher claims: "Build or review frontend UI for clean, restrained, human-designed interfaces without generic AI visual patterns." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-12 and scored it 65/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
- Add Sonner via `npx [email protected] add sonner`, mount a single `<Toaster />` in the app root, and use its `toast()` helper for all notifications — no other toast library, no bespoke toast components.Fix: Pin versions and sources; vendor anything fetched at install time.- Scaffold with `npx [email protected] init` (Tailwind + CSS variables), then add components with `npx [email protected] add <component>` rather than hand-rolling primitives.Fix: Pin versions and sources; vendor anything fetched at install time.… system, Base UI-based, shadcn-CLI compatible) on top: init a new project with `npx [email protected] init @coss/style`, add components with `npx [email protected] add @coss/ui`. Compon…Fix: Pin versions and sources; vendor anything fetched at install time.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
15 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim leostehlik: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- 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.