Would you run a command without knowing what it could do?

A copied installation script. An automated workflow. A shell command suggested by AI.

Convenient? Yes. Worth checking before execution? Absolutely.

That’s why I built SafeShell, an open-source tool for inspecting commands, applying security policies, and running permitted commands with sandboxing on Linux.

The goal: help developers and engineering teams work faster with more control over what they execute.

Explore the code, try it, and share your feedback: https://github.com/HamzaGhebriche/SafeShell

Building automation or CI/CD workflows that need stronger security controls? I’m available for freelance projects in DevSecOps, secure automation, and cloud security. Let’s talk through Contra.

Useful idea, especially for commands suggested by AI. In my deploy script every step is logged, but nothing checks a command before it runs. Can SafeShell also run inside CI, for example as a step in GitHub Actions?

Myth: once the site is live, the project is done.

Fact: launch is the first day the site meets real visitors. It needs care after that: updates, fixes, content and tracking.

What a monthly check covers on the sites I look after:

• Updates on staging first: core, theme, plugins or apps

• Every form tested end to end. Does the email actually arrive?

• Search Console: new errors, new 404s, pages dropped from the index

• Speed on the top pages, on mobile, not just desktop

Most problems I find in audits weren't there at launch. A plugin update broke a form, a page was renamed without a redirect, a new script slowed the homepage.

None of them are dramatic. They just pile up when nobody looks.

Who checks your site after launch, and how often?

One real site, one real tip, every day. Follow for more videos.

Follow for more videos: instagram.com/sellwrightstudio · youtube.com/@sellwrightstudio

Testing every form end to end is the check that saves clients most often. A silently broken form can cost leads for weeks before anyone notices.