Skip to content
HARDEX

Guide

How to check if your Replit app is secure

Replit can turn a prompt into a running app and publish it in a few clicks. What it publishes is real software that real visitors can reach, so it is worth a look from the outside before you share it.

This is a short checklist for apps built on Replit: four things to check on what is actually live, each with a way to check it yourself and what to do. You do not need to be a developer.

1Keys belong in Secrets, not in files

Replit has a Secrets tool, and its documentation says the values you keep there reach your code as environment variables, so they never have to be typed into a file. A key typed into a code file is part of the code: anyone who can read the code or the published pages can read the key.

Check it yourself: Open your project's files and search for words like key, secret, token and sk-. Then look at how your code gets its keys: it should read them from the environment, not from text in a file.

What to do: Move each key into Secrets and change the code to read it from the environment. Then create a new key and delete the old one, because anyone who saw the old one can still use it.

2A static site cannot keep a secret

Replit's documentation says a static deployment serves only HTML, CSS and JavaScript files, and that Secrets are not available for it. Everything in those files is sent to every visitor, so any key that a static page uses is a public key, whether you meant it or not.

Check it yourself: Open your live app and press F12. In Chrome, go to the Sources or Network tab and search the files for words like key, secret and token. If your app is a static one and talks to a paid service, look closely.

What to do: Use a deployment type that runs code on a server, keep the key there, and let the page ask your server instead of the service. Then replace the old key.

3Who can read your project's code

Depending on your plan and settings, a Replit project and its code can be visible to anyone with the link. If a key or a password is in the code, it is visible too.

Check it yourself: Open your project in a private window where you are signed out and see how much you can read. Check the visibility setting in your project's settings.

What to do: Make the project private where your plan allows it, and take every key out of the code either way. Replace any key that was ever in it.

4Server addresses that answer anyone

If your app has a server, its pages call addresses on it to get and save data. An address that returns data without asking who you are will return it to anyone who opens it, not only to your app.

Check it yourself: Open your live app, press F12 and go to the Network tab. Use the app, then pick the calls that load data and open their addresses in a private window where you are signed out. If you get real records back, the address is open.

What to do: Ask your AI builder: “Make every endpoint that returns or changes data require a signed-in user, and return only that user's own records.” Then check again in a private window.

What a check can and cannot tell you

Passing these checks does not prove an app is safe. It means these problems were not found. A full review also looks at how your app handles each person's data, and that takes someone who reads the code or tries to get past the sign-in.

Check them all from the outside

Hardex scans a live app the way a stranger on the internet would, with nothing to install. By default it only reads: it never changes anything in your app. It looks for the problems above where they apply to your app, and more, then reports what it found.

What each plan includes is on the plans page.

Scan your app

Hardex is an independent product made by AryonX. Replit is named here only to say what this guide is about.