DEDUPEDRemote script. Scripts downloaded from unknown sources should be audited before execution, and this tool only flags candidates; it does not prove a script is safe.
Who it is forA DevOps engineer or security-minded reviewer inheriting shell scripts from an unknown source, who needs to see what they do to the host.
The problemA script's effects on the machine, such as running downloaded code or installing persistence, are often invisible to its reader.
The outcomeA ranked list of shell findings with scores, to guide a manual security read of the flagged lines.
What you need first
- Node 24 or newer with npx
- A TYPESAFE_API_KEY from https://typesafe.ai, set in the environment (the code being judged is sent to the API)
- A repository with code to lint, such as a TypeScript src folder
Steps
npx -y jev-lint check examplesnpx jev-lint check scripts --dry-run(inferred, check the README)npx jev-lint check scripts(inferred, check the README)npx jev-lint run shell/<rule-id> scripts(inferred, check the README)
Prompt for your agent
In the repository <repo-path>, with TYPESAFE_API_KEY set, run `npx jev-lint check scripts --dry-run` to confirm what would be sent, then `npx jev-lint check scripts`. List findings on .sh, .bash or .zsh files with their rule ids, and flag any that a human should read before running the script.
Caveat. The shell rules are calibrated to the same bar as the rest but not promised as first tier, so treat their findings as leads for review.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page