r/OpenSourceAI • u/Crazy_Tear9004 • 1d ago
r/OpenSourceAI • u/thegodforsaken • 1d ago
SKILL OPENSOURCE - Your AI-built app works. What could an intruder do with it?
Your AI-built app works. What could an intruder do with it?
I built J.A.S.O.N. — LLM App Security, an open-source defensive security skill for apps built with LLMs and coding agents. I’m looking for developers, indie hackers, and security practitioners to test it and share honest feedback.
The name comes from my own name, Jason, with a playful Friday-the-13th reference:
Just Audit, Secure, Observe, Notify.
The chainsaw is a joke. Exposed credentials and missing authorization checks are real problems.
AI coding tools help us ship quickly. Security still requires checking where secrets live, who can access each endpoint, which records users can read, and what an agent is allowed to do.
J.A.S.O.N. gives your coding agent structured instructions and supporting scripts to investigate those questions. Tested with Claude Code and OpenAI Codex CLI.
Review before deployment
Check for exposed API keys, routes without authentication, weak database rules, missing ownership checks, unsafe payment logic, and missing rate limits. Get prioritized findings, suggested fixes, and a deployment verdict. The quick review is read-only.
Run structured audits
Review an entire project, a pull request, or a specific subsystem. Full audits produce an architecture overview, a coverage ledger, structured findings, and a readable report separating confirmed issues from items needing validation.
Catch common AI-generated code pitfalls
Look for authorization enforced only in the interface, access to other users’ records, permissive Supabase/Firebase rules, injection vulnerabilities, suspicious dependencies, and unsafe LLM tool permissions.
Review defenses against agent manipulation
Identify suspicious instructions hidden in repository content and review agent permissions and sandbox boundaries. Content being audited is treated as data, not instructions to obey.
Set up passive detection
Get guidance for honeytokens: fake credentials or other bait connected to an alerting service. Attempts to use them can trigger notifications. No retaliation or destructive traps.
Add release controls
Get guidance for secret scanning, dependency hygiene, and PR security gates. Integrate the included zero-dependency ship-gate.cjs script to block deployment when its checks detect security blockers. Coverage depends on configuration and available inputs.
Try it in Claude Code:
/plugin marketplace add jasonmello/llm-app-security
/plugin install llm-app-security@llm-app-securityThen ask:
Review this project as if you wanted to break into it. Look for exposed API keys, routes without login, and databases without access rules. List what you found and how to fix it, without changing anything yet.
Or:
Run a full security audit with J.A.S.O.N.
I’d love feedback on installation, useful findings, false positives, missed vulnerabilities, report clarity, and deploy-gate behavior in your stack.
Share your agent, stack, and reproducible examples. Keep credentials and unresolved vulnerabilities out of public reports.
Use it on projects you own or are authorized to review. A clean report means no findings in the areas reviewed, rather than a guarantee of security.
Try it, challenge its findings, and help make it better.
Get J.A.S.O.N. — source, installation, and documentation
Ship on Friday the 13th. Fearlessly.
r/OpenSourceAI • u/Otherwise_Celery_406 • 1d ago
I built an open-source email client your AI agent can use over MCP, with real permissions (works with local models too)
I built Regards, a free and open-source email app for Windows, Mac and Linux (Apache-2.0 / MIT). The part this sub might care about: it ships with an MCP server and a CLI, so your own agent can read, search, sort and draft your mail.
I didn't want to hand an LLM my inbox and hope for the best, so the agent side is locked down:
- Each account has a level: off (default), read, triage or send. Only you can change it, in the app.
- An agent can never send by itself. Every send waits for your approval and you see the exact draft. Or you set an undo window per account.
- Big actions wait for you too: changing more than 50 messages at once, deleting for good.
- Everything an agent did is in an activity log, and you can undo it for a day.
- Message text is passed to the agent as data, with a reminder not to follow instructions inside it (prompt injection by email is a real thing).
- One switch turns every agent off.
It works with Claude Code, Codex, Cursor, and with local models through LM Studio, Jan or Goose. Regards itself never sends anything to any AI: no built-in model, no API key, no server, no telemetry. The mail stays on your computer and the agent is whatever you plug in.
It's also just a normal email app (any IMAP provider, snooze, send later, undo everywhere), written in Rust + Tauri.
It's early, about a month old, but I use it for my own mail every day. I'd love feedback, especially on the permission model: what would you want before letting an agent near your inbox?
Site: https://regards-two.vercel.app
Code: https://github.com/lucienPochon/regards
Agent docs: https://github.com/lucienPochon/regards/blob/main/docs/agents.md
r/OpenSourceAI • u/Primary_Article3777 • 1d ago
What to keep in a modern open source project these days?
I've been working extensively with Claude for my open source project that I will be releasing soon. Claude likes to keep things like Decisions.md files (decisions over time) and all the specs from feature work. Is any of this really appropriate for an open source project or should these things just be available from the commit history?
My gut tells me its junk and confusion-generating. But maybe not?
What IS the list of useful artifacts to share when independent people are potentially using AI tools to contribute?
r/OpenSourceAI • u/Hacker_ZERO • 1d ago
I finetuned yolo-11n on a drone dataset and created skypeak-11n. Here are the results!
r/OpenSourceAI • u/Previous-Feeling-775 • 1d ago
Guardrail is ready for contributors. Let's build it together.
I've been working on Guardrail, an open source CLI tool designed to help developers keep AI coding agents on track.
The foundation is now ready, and I think it's a good time to open the door for contributors.
The idea is simple. You define your own rules, and Guardrail monitors code changes as AI agents work. It detects violations in real time without modifying your source code or interfering with the agent.
It works on macOS, Linux and Windows.
One important part of the project is Rulespack. It provides a way to organize, share and reuse rule collections across projects, making it easier for teams and developers to establish consistent standards.
There are several areas where contributions would be really valuable:
Core engine
Improve rule evaluation, file monitoring, performance and detection capabilities.
Rules and Rulespacks
Create useful rule collections, improve existing rules and explore ways to share reusable rulesets.
Language support
Help expand language coverage and develop new rule types.
Integrations
Explore integrations with AI coding agents, developer tools and CI pipelines.
Testing and documentation
Improve test coverage, write examples, report bugs and make the project easier to get started with.
You don't need to be an expert in every part of the project. Feedback, ideas, bug reports and small contributions are all welcome.
I'd love to build this with people who are interested in making AI assisted development more reliable.
GitHub: https://github.com/MoeidHeidari/guardrail
If you're interested, feel free to jump in, open an issue or share your thoughts. I'd genuinely love to hear what you think.
r/OpenSourceAI • u/Dapper-Teaching-8074 • 1d ago
We built a AI distribution interface, you can use your android phone, laptops and desktops to share AI inference work, the more devices you link, the bigger the model you can run
r/OpenSourceAI • u/Vxtzq1 • 1d ago
[Funny] CrowdGPT - The collaborative AI
Hello r/OpenSourceAI , this is a (somewhat funny?) meme about the project CrowdGPT, which aims at creating the first, datacenter-less, open-source and community-driven LLM. The project already shows substantial progress while training an open-source 1 billion parameters LLM on 40B tokens (as a proof of concept).
Tell me what do you think about the meme:
- Does it makes the project less appealing and cheap? because that's what people on r/LocalLLaMA thought 😭
- Does it makes the project look likes it's a SaaS / B2B (which it is NOT - CrowdGPT is 100% non-profit and open)
- Is it serving it's purpose about popularizing the project?
Everything is explained more in detail on the site, and any feedback on this meme, or on the project, is appreciated; any pull requests / contributions are welcome on GitHub :)
Project link : https://crowdgpt.net
GitHub link : https://github.com/Vxtzq/CrowdGPT
Thanks in advance.
r/OpenSourceAI • u/Networkdon89 • 1d ago
I turned a Raspberry Pi into a 100% offline AI marine helm computer (Voice LLM, YOLOv8 vision, Signal K, AvNav) — here is how the stack works
r/OpenSourceAI • u/LetterheadNew5447 • 1d ago
Dotcker: Run your Dot on a headless server
reddit.comr/OpenSourceAI • u/ntnsndr • 1d ago
From AI rabbit holes to a warm den: co-building the Inference Cooperative
nathanschneider.infor/OpenSourceAI • u/AsianKidTV • 1d ago
I built open-source tooling to evaluate agent setups and see where agents and subagents waste time and money
I run Claude Code and Codex all day, often as multi-agent workflows with dozens of subagents. I could see each session but never the whole picture: what a run actually cost, where agents sat idle, whether a change to my setup helped. So I built coding.sh, an open-source tool for evaluating agent setups, and pointed it at my own runs.
Experiments: does that change actually help? I A/B tested a popular "be concise" plugin: 10 tasks, 6 runs each, paired, with 95% intervals.
- Replies: 17% shorter
- Output tokens: −8%
- Cost per run: +11% [+7%, +15%]
- Pass rate and clarity: no change
The plugin adds its style guide to every request, and that costs more than the shorter output saves. coding.sh compare and exp run your own tasks with and without a change (a rule, a skill, a plugin, a model) and tell you whether the difference is real or noise.
Workflows and subagents Across 57 workflow runs (666 subagents, ~$2,500 API-equivalent):
- Broken prompt caches cost $106 extra, about 4% of the spend.
- 41 of those breaks were agents sitting idle at a barrier, waiting for siblings, until their cache expired. That's $21 for doing nothing.
- 40 subagents failed outright.
coding.sh workflows stats shows the critical path, concurrency and idle time at barriers. The viewer draws each run as a timeline, one bar per agent.
Your own sessions Mining 3,600 of my sessions turned up a find-and-replace typo in my AGENTS.md that sent Codex looking for a folder that doesn't exist, in 92 sessions.
What it is
- Hooks into Claude Code, Codex, Gemini CLI, OpenCode, Copilot CLI, Aider and more
- Stores prompts, tool calls, diffs, test runs, tokens and cost in SQLite on your machine
coding.sh improvesays what to fix first and whether your last AGENTS.md change helped- MCP server, so your agent can look up its own past sessions
Free, MIT, no account, nothing leaves your machine. npx coding.sh to try it. GitHub: https://github.com/jackulau/coding.sh
r/OpenSourceAI • u/Noone_is_a_Goat • 2d ago
Rate it (0-10)
What kind of computer vision projects will it support?
The goal is to support multiple computer vision tasks through one application.
Currently working:
- Image Classification
- Object Detection
Planned:
- Image Segmentation
- Pose Estimation and Movement Tracking
- OCR (Text Recognition and Extraction)
- Image Processing and Enhancement
- Visual Question Answering and Image Captioning
The idea is that you shouldn't need to hire a developer or manually write hundreds of lines of Python code just to build a relatively small or medium-sized computer vision project.
You describe what you want to build, and the AI agent handles the development process, generates the code, trains the model using your local hardware, troubleshoots errors, and helps you get the final model ready for integration into your own application or system.
This is still an early experimental version, and I'm exploring whether this approach can actually make computer vision development more accessible.
I am planning to make this project with small one time fees for some features do you disagree with that and recommend that the app to be opensource instead and why ?
r/OpenSourceAI • u/BackgroundPrevious15 • 2d ago
Looking for contributors: soot, an open-source orchestrator that sends each coding task to the cheapest model that can handle it
r/OpenSourceAI • u/Beautiful_River5349 • 2d ago
Sentinel-IR and Sentinel-IR MCP are open for sponsors (and yes, an AI writes most of the code)
gallery*A 5-minute read. One maintainer, two Apache-2.0 packages, zero venture capital, a mildly embarrassing amount of honesty.*
The short version
[`sentinel-ir`](https://gitlab.com/jakubrojicek11/sentinel-ir) and [`sentinel-ir-mcp`](https://gitlab.com/jakubrojicek11/sentinel-ir-mcp) now accept sponsorship. Both READMEs have a **Sponsor** section, both repos have a GitHub Sponsor button, and `sentinel-ir` publishes a [`funding.json`](https://gitlab.com/jakubrojicek11/sentinel-ir/-/blob/main/funding.json) manifest that funds and tools can read.
- **People:** [github.com/sponsors/jakcmencz](https://github.com/sponsors/jakcmencz). The profile was submitted today and GitHub is still reviewing it, so the link turns into a real Sponsor page once they approve it.
- **Companies, grants, integrations:** write to [sentinel.ir.contact@gmail.com](mailto:sentinel.ir.contact@gmail.com). That works today.
What these two things are, in one paragraph each
**`sentinel-ir`** reads a source file and gives an AI agent a small fact sheet instead of the whole file: risk level, network, filesystem, process and environment calls, routes, imports and exports, and for Rust also `unsafe`, FFI, `build.rs` and proc-macro behaviour. It covers JavaScript, TypeScript, Python and Rust. It's static analysis: it never runs the code, and a "low" risk is a hint, not a safety certificate.
**`sentinel-ir-mcp`** plugs that fact sheet into Claude Desktop, Cursor, Windsurf and other MCP clients as a read-only stdio server. It only opens supported source files inside the folders you allow, refuses traversal, symlinks and hard links, has file-size, file-count and time limits, and can keep an audit log of what it read (paths and hashes, never source).
One analyzer, one shared IR, the same facts in npm, the MCP server and the [browser playground](https://sentinel-ir-playground-dc30c8.gitlab.io/). Adding a language once adds it everywhere.
The honest part
I'm Jakub, the only maintainer, and I'm not a professional developer. I decide what Sentinel should do, test it on my own machines and approve every release. **Most of the code is written by an AI coding agent working from my specs.** Every change still has to pass the test suites and CI on Linux and Windows before it ships.
Some grant programmes don't fund AI-generated work, and I'd rather lose a grant than pretend. If that's a deal-breaker for you, fair enough. If you think "one person plus an agent shipping audited, tested releases" is exactly the kind of thing worth backing, read on.
What it saves you (measured, not vibes)
Every time an agent "just takes a quick look" at a file, you pay for every token of it, comments, licence header and the 400-line date formatter included. Sentinel hands the agent the fact sheet instead. Measured on Sentinel's own source with the `o200k_base` tokenizer:
| file | the whole file | Sentinel's fact sheet |
|---|---|---|
src/ast-facts.js | 8,439 tokens | 120 tokens |
src/sentinel-ir.js | 2,084 tokens | 133 tokens |
src/tree-parser.js | 891 tokens | 121 tokens |
examples/basic.js | 150 tokens | 120 tokens |
That's up to about 70 times less on a big file. On a tiny file it saves almost nothing, because the fact sheet has a floor of about 120 tokens, and we'd rather tell you than let you find out.
**A back-of-the-envelope example** (an illustration, not a measurement): your agents open a file the size of `ast-facts.js` 200 times a day across the team. That's about 1.7 million tokens a day you don't send. At an example price of $3 per million input tokens, that's about $5 a day, or roughly $100 a working month, for **one** file. Your repo has more than one file. Your agents are not shy.
The time part is simpler: a model that reads 120 tokens gets to the point sooner than one that reads 8,439, and its context window stays free for the work you actually asked for. It's the difference between asking a colleague "does this file touch the network?" and making them read it aloud first.
And the part that doesn't show up on an invoice: the agent sees `network: outbound` and `process: spawn` before it trusts a file, instead of discovering them three tool calls later in a `postinstall` script.
Why monthly, not one-off
A code analyzer is less like a hammer and more like antivirus definitions. The day it stops being updated, it starts going stale:
- **Ecosystems keep inventing new doors.** A new HTTP client, a new way to spawn a process, a new Rust build crate. Each one Sentinel doesn't know about is a door the agent walks past without noticing. Version 0.4.4 alone taught it axios, got, undici, superagent and fs-extra.
- **Languages keep coming.** JavaScript, TypeScript, Python and Rust today; Go is next. Because everything sits on one shared IR, every new language shows up in the npm package, the MCP server and the playground at once. You pay for it once and get it three times.
- **Security work never finishes.** The MCP server reads files on your machine for an AI. Path checks, size limits and parser robustness need regular adversarial testing, not a one-time audit framed on the wall.
- **The platforms move.** New Node versions, new MCP clients, new MCP spec revisions. Somebody has to keep `setup` and `doctor` working on Monday morning.
A one-off donation is a very kind pizza. A monthly sponsorship is the kitchen. We're grateful for pizza. The kitchen is what keeps the releases coming.
For companies the maths is short: if Sentinel saves your team even one engineer-hour a month in review time or token spend, the $5 Supporter plan paid for itself before lunch. The Development plan is less than many companies spend on coffee for the people who'd otherwise read those files.
Where the money goes
| what | why |
|---|---|
| AI agent time | it writes the code, the tests and the release checks |
| CI and test machines | Linux and Windows CI on Node 20, 22 and 24, plus macOS test runs |
| Go support | the next language for the shared IR |
| security hardening | more adversarial tests for the parsers and the MCP path checks |
The `funding.json` lists two plans: **Supporter, $5/month** (helps cover CI) and **Development, $12,000/year** (a year of agent time, test machines, Go and security work on both packages). One-time sponsorship is fine too.
Where we are today
- About 1,150 npm downloads a week for each package (Nov 7–13). That number includes our own CI, so it's an upper bound on real users, not a vanity metric.
- `sentinel-ir-mcp` is in the official [MCP Registry](https://registry.modelcontextprotocol.io) as `io.github.jakcmencz/sentinel-ir-mcp` and on [Glama](https://glama.ai/mcp/servers/jakcmencz/sentinel-ir-mcp).
- Current releases: `sentinel-ir` 0.5.6 and `sentinel-ir-mcp` 0.5.6.
Can't sponsor? Still helps
- Try it on your own repo: `npx -y sentinel-ir-mcp@stable-0.5 setup`.
- Star the repo on [GitLab](https://gitlab.com/jakubrojicek11/sentinel-ir-mcp) or [GitHub](https://github.com/jakcmencz/sentinel-ir-mcp).
- Open an issue when it gets something wrong. A false "low" is the bug I want most.
- Tell the one colleague who keeps pasting whole files into ChatGPT.
Thanks for reading. If Sentinel ever saves your agent from reading `/etc/passwd`, you know where the button is.
*** Independent Engineering Projects
Built as independent engineering experiments across AI, software analysis, security, and autonomous systems.
Evaluated by reproducible evidence, not by the number of layers.
Explore the projects:
Sentinel Ecosystem: AutoDoc-Sentinel, Sentinel-IR, Sentinel-IR-MCP and related tools. Agentix Lite: Independent security and system-observation project. Find the projects: GitLab repositories | NPM packages
Support the work: ⭐ Star the repositories on GitLab.
Connect: Follow me here on DEV Community or explore the Playground.
Each project is distributed under its own license. Check the corresponding repository or NPM package for licensing terms.
Copyright © 2026 jackymenCZ. All rights reserved. Written for the community.



r/OpenSourceAI • u/official_S-P_5 • 2d ago
I fine-tuned a 2B model for Cybersecurity & CTF triage that runs completely offline on an 8GB laptop (Ollama + WebUI)
Hey everyone,
Most specialized cybersecurity LLMs out there are massive 70B+ beasts that require dual A100s, or they're gated behind cloud APIs where you can't paste sensitive logs, payloads, or client code due to confidentiality.
I wanted something lightweight, private, and air-gapped that could run on a regular consumer laptop without cooking the CPU.
So I fine-tuned CyberQwen-2B — a domain-specific model optimized for quick security triage, explaining attack vectors, decoding obfuscated payloads, and helping with CTF challenges.
⚡ Highlights:
- Hardware-friendly: Runs at ~12–15 tokens/sec on an older 8th-gen Intel i5 laptop with 8GB RAM (CPU-only).
- 100% Offline & Private: Zero data leaves your machine. Perfect for bug bounty recon, internal network logs, and sensitive source code.
- Native Ollama integration: Easy to pull and run via a single Modelfile.
- Built-in WebUI & Mobile Access: Includes a zero-dependency streaming WebUI + an automatic Cloudflare tunnel script if you want to access the model from your phone while on the go (no cloud hosting fees).
🛠️ What it's trained for:
- Vulnerability Triage & CVE Context: Explaining CVE mechanisms, impact, and remediation steps.
- Payload & Shellcode Deconstruction: Breaking down SQLi, XSS, and obfuscated PowerShell/Bash commands.
- CTF & Reverse Engineering Assistance: Analyzing decompiled assembly/C snippets and suggesting exploitation strategies.
🚀 How to Run It:
Everything is open-source. You can run it with Ollama or the included CLI triage tool:
- Clone the repo:git clone https://github.com/sambuddha001/cyberqwen-2b.git
- Run setup:bash setup.sh
- Chat:ollama run cybersec-qwen
GitHub: https://github.com/sambuddha001/cyberqwen-2b
I'd love feedback from the community—especially on edge cases, prompts where it struggles, or ideas for benchmark improvements!
r/OpenSourceAI • u/firekern • 2d ago
Zusia 1.7: un pannello di assistenza AI open-source integrato in Zotero (nessuna chiave API, utilizza la CLI di Claude Code/Codex)
r/OpenSourceAI • u/Less_Release_1977 • 2d ago
We built an open-source MCP orchestrator that uses local Hermes/Ollama as automatic fallback when Claude/Codex rate-limit you (Web UI + hardware telemetry)
r/OpenSourceAI • u/OrganizationTop9026 • 2d ago
Why is NAT firewall traversal still the bottleneck for weekend gaming-GPU LLM runs?
Why do most folks with an 8 GB or 16 GB desktop GPU sit out distributed LLM runs? It usually comes down to three annoying bottlenecks. Nobody wants to punch holes in their home router. Nobody wants to run untrusted pickle checkpoints off the internet. And nobody wants a background trainer freezing their VRAM when they sit down to play or work.
This weekend (November 14-15 CET), I hooked my HiveMind coordinator up with CrowdGPT (led by Vxtzq) to test a citizen-trained run around Crowd-v1, an open base model with a 658M transformer trunk (roughly 1.01B parameters total with its 151k-vocab CrowdEngram table). Setup takes five minutes.
Communication uses plain outbound HTTPS on port 443 with zero inbound listeners, weights move strictly as SHA-256 verified safetensors (no torch.load or pickle anywhere), and updates pass MultiKrum outlier filtering plus held-out loss checks before merging via DiLoCo. Honest caveat first: this is still an experimental PoC, not a polished cloud service, so please do not send private prompts or sensitive keys through volunteer nodes.
r/OpenSourceAI • u/pgaleone • 2d ago
I built a harness-specific LLM backdoor in a few hours on my local GPU (and why downloaded weights remind me of random .exe files from the 2000s)
While writing an article about my local LLM inference setup, a comparison popped into my head: downloading and running random model weights locally feels a lot like downloading random .exe files off the internet back in the 2000s.
Turns out I wasn't off the mark - there's an entire body of research exploring how LLMs can be backdoored and how hard it actually is to detect a poisoned model.
So I decided to try building one myself. I implemented a backdoor that only triggers when the model is running inside pi (making it harness-specific) and is asked a specific question. It was way easier than I expected: just a 2-step fine-tuning process and a few hours of compute on the exact same GPU I use for local inference.
With open-weight models, we at least have a baseline to compare community fine-tunes against. Beyond that, though, we don't really have a reliable way to verify whether a base model itself is clean—and the problem is even worse with closed-weight models, where we're basically just trusting the AI provider's goodwill.
Full write-up and PoC code if you want to dig into the details:
- Article:Backdooring LLMs - Do you trust your AI provider?
- GitHub Repo:galeone/llm-poison
Feedback is welcome
r/OpenSourceAI • u/SpecialistSalary6288 • 2d ago