An open-source code scanner to find issues in prompts and LLM calls
Code scanner to check for issues in prompts and LLM calls - kereva-dev/kereva-scanner
An open-source code scanner to find issues in prompts and LLM calls launched on April 7, 2025 with 5 votes and more than 75% of that year's launches. The site was still online in September 2026, 1 year on.
What it does
Kereva LLM Code Scanner is a static analysis tool designed to identify potential security risks, performance issues, and vulnerabilities in Python codebases that use Large Language Models (LLMs). It analyzes your code without execution to detect problems like hallucination triggers, bias potential, prompt injection vulnerabilities, and inefficient LLM usage patterns. # Clone the repository git clone https://github.com/rbitr/kereva-scanner.git cd kereva-scanner # Install dependencies pip install -r requirements.txt 📊 Usage Basic Scanning # Scan a single file python main.py path/to/file.py # Scan a Jupyter notebook python main.py path/to/notebook.ipynb # Scan an entire directory python…from github.com
Does a similar job
all alternatives →
A static scanner for LLM app code2025 · github.com · ▲6Code scanner to check for issues in prompts and LLM calls - kereva-dev/kereva-scanner
PromptTools – open-source tools for evaluating LLMs and vector DBs2023 · github.com · ▲211Hey HN! We’re Kevin and Steve. We’re building PromptTools (https://github.com/hegelai/prompttools): open-source, self-hostable tools for experimenting with, testing, and evaluating LLMs, vector databases, and prompts. Evaluating prompts, LLMs, and vector databases is a painful, time-consuming but necessary part of the product engineering process. Our tools allow engineers to do this in a lot less time. By “evaluating” we mean checking the quality of a model's response for a given use case, which is a combination of testing and benchmarking. As examples: - For generated…
- PIPrompt Inspector – A browser-like inspect tool for prompts2025 · inspectmyprompt.com · ▲23
I was working on a project that involved indexing GitHub repos that used really long prompts. Iterating over each section and figuring out which parts of the prompt led to which parts of the output was a quite painful. As a frontend dev, I kept thinking it would be nice if I could just 'inspect element' on particular sections of the prompt. So I built this prompt debugger with visual mapping that shows exactly which parts generate which outputs. Now that context windows are getting huge, working with massive prompts should not be as difficult. Planning to open source this soon, but I'd love…
More ai this month
the category →
Paintings by AI models: programs run through a simulation of oil paint.
AI · 21d ago · stillwet.art
PixVerse R2▲381A real-time world model you can explore and change
AI · 30d ago · world.pixverse.video
Source: Show HN post ↗
Launched alongside, April 2025
the whole month →
Hi everyone, I built PyXL — a hardware processor that executes a custom assembly generated from Python programs, without using a traditional interpreter or virtual machine. It compiles Python -> CPython Bytecode -> Instruction set designed for direct hardware execution. I’m sharing an early benchmark: a GPIO test where PyXL achieves a 480ns round-trip toggle — compared to 14-25 micro seconds on a MicroPython Pyboard - even though PyXL runs at a lower clock (100MHz vs. 168MHz). The design is stack-based, fully pipelined, and preserves Python's dynamic typing without static type restrictions.…
Dev tools · 2025 · runpyxl.com
The Unsure Calculator is an online tool that lets you calculate with numbers you’re not sure about.
Life & fun · 2025 · filiph.github.io
https://the-pocket.github.io/Tutorial-Codebase-Knowledge/
AI · 2025 · github.com
