Skip to content
SlashClone

Docs

How SlashClone checks what people share

What the automatic check reads in every kit, how project pictures and live demos are handled, how your sign-in is protected, and how to report something.

People share kits, projects, pictures, and links here. This page says what we check before anyone else sees them, and where those checks stop. Use it with the kit page itself: Reading a kit page shows where each kit's results appear.

What the check reads in a kit

Every version of every kit is checked before anyone can add it. The check reads every file in the kit, not only the instructions:

  • code, scripts, settings, and every text file
  • the words inside Word, Excel, and PowerPoint files, including notes, comments, and the names of linked files
  • text tucked inside pictures and fonts, such as a picture's comments or camera details, and in any other file it cannot open

In all of them it looks for keys and passwords left in the files, commands that download and run code or send your files away, hidden instructions written to turn Claude against what you asked, and anything the kit does that is not on its list. A Word, Excel, or PowerPoint file with macros fails, because macros run code when the file is opened. An Office file the check cannot read fails too. A PDF is not read yet: a kit with a PDF publishes with a warning that the file could not be checked, so open it yourself before you trust it.

A kit that fails is not published. A kit with warnings is published with a warning mark, and its Safety tab lists each finding.

The check matches patterns. It is not a person reading the kit, and it cannot promise what a kit will do. A command pieced together from parts, or instructions in another language, can slip past it. Read What it can access on the kit page before you add a kit.

Signed, and never changed after

Once a version passes, its files are fingerprinted and signed. The slashclone command line tool checks that signature when it installs a kit, so you get exactly the files that were checked. A published version never changes; a fix is always a new version.

Pictures, demos, and links on project pages

  • Pictures and GIFs. Each file's type and size are read from the file itself, never its name, and the text inside it goes through the same check as kits. Pictures from new accounts wait for a person on our team before anyone but their makers sees them.
  • Files people upload are shown in a sealed space: they cannot run scripts or read your sign-in on SlashClone.
  • Live demos open inside a sealed frame. The demo runs apart from SlashClone, in a frame built so it cannot see your account or act as you. A demo can only show its own site, and the link to the frame expires after a few minutes.
  • Demo and video links must use https, point to a public address at every step, and answer when we check them. A site that refuses to be shown inside another page gets a card that opens it in its own tab instead.

Your sign-in

  • An email sign-in link works once, for 15 minutes. Opening it shows a Continue button, so a mail scanner that opens links first cannot use it up. Each address and each network can ask for only a few links an hour.
  • When you connect Claude, ChatGPT, or another app, you approve exactly what it may do on the screen that asks, and it gets only that.
  • A token from Settings, Tokens, or a login from the command line tool, stops working after 180 days unused. Each use starts the count again. You can delete any of them there at any time.

Report something

  • A kit: use Report this at the bottom of its Safety label, signed in. A person on our team reads every report. A kit confirmed as harmful is pulled, and everyone who installed it is told.
  • A comment or a project's devlog entry: use Report under it. Reporting opens once your account has been here a while and taken part.
  • Copyright or a trademark: use the takedown form.
  • A security problem in SlashClone itself: email the address on the security page, and do not make it public until it is fixed.

Your cookie choices

We use cookies you can say no to for analytics, ad measurement, and embedded videos. Signing in works either way. You can change this any time from Cookie settings at the bottom of every page. What we use

Cookies that keep you signed in and remember these choices are always on. Everything else is off until you turn it on.