How review works
What a reviewer checks, what you see, and what happens after.
Every new component and every new version is looked at by a person before it goes live. Review keeps the catalog safe to install from and worth browsing.
What a reviewer checks
- It renders on its own in the preview and does what it says.
- The code is yours to share, under the licence you picked, with credit kept for anything it builds on.
- Nothing harmful: no tracking, hidden network calls, miners, ads or obfuscated code.
- It isn't a copy of a component already on Layro, and its name and description say what it is.
- For an update: the changes, shown as a diff against what's live.
What you see
- While it waits, your studio shows it as in review. The CLI's
statusand the MCPsubmission_statustool say the same. - Approved: it goes live (an update replaces the previous version), and a short video is recorded for its tile.
- Needs changes: you get the reviewer's reason. The previous version, if there is one, stays live. Fix it and send a new version.
- Either way you get an email, unless you turned review emails off in Settings.
How long it takes
Layro is run by one person, so review usually takes a day or two. One version per component can wait at a time; sending another replaces nothing until the first is decided.
After it's live
Anyone signed in can report a component that's broken, has a licence problem, is malicious or is spam. If a report holds, the component is taken down and you're emailed why. Reply to that email to fix or dispute it. The full process is on the licences page; questions go to hello@layro.dev.