Loading the registry…
Publishes HTML or Markdown as display.dev URLs with public, company, or private access. Supports signup, claiming, sharing, browsing, bounded reads, exact edits, and comment iteration. Use when the user asks to "publish this", "share this", "share with the org", "post this online", "make a private link", "share with [email]", "publish a report", "list my artifacts", "find an artifact", "publish a large file", "publish this generated HTML file", "read this artifact", "search inside this artifact", "change this passage", "make a copy of this artifact", "duplicate version", "create a display.dev account", "claim this publish", "add a company email domain", "transfer an email domain", "show my referral link", "show referral rewards", "watch comments on this artifact", "respond to comments", or "resolve this comment thread". Use whenever a request contains a display.dev artifact URL (`*.dsp.so/*`). Anonymous publishing returns a 30-day preview and browser claim URL.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
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.
1 critical finding reported by agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.
This artifact ships from 2 sources and their verdicts differ. The worst is github (Flagged). Installing from a cleaner source does not mean the others are safe — check the source you actually install from.
github: https://github.com/display-dev/skill, 351 findings
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'display-dev/skill (display-dev)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'display-dev/skill (display-dev)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 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.
v2.0.11
346 findings · 9.3s
v0.3.74
5 findings · 4.5s
v0.1.0
0 findings · 4.1s
v0.1.0
0 findings · 4.1s
v0.1.0
4 findings · 8.9s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 17, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: complete | rejected |
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.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 355 findings above stand exactly as their scanners reported them, at full severity.