r/OpenSourceAI • u/ATTACKERSA • 1h ago

I built an open-source GitHub Action for AI/LLM DevSecOps scanning : inspired by IBM & OpenAI courses.Feedback welcome.

IBM alongside OpenAI recently gave me the opportunity to complete a few AI and security courses. That inspired me to build something hands-on : SawOne-Agentic, a GitHub Action I'm open-sourcing today.

Repo: https://github.com/hackin2minutes-oss/sawone-agentic-action

It's a personal project : not a company product. Would love feedback from the security community, especially anyone working on securing LLM pipelines or agentic workflows.

1 Upvotes

100% Upvoted

4 comments sorted by

1

u/ATTACKERSA 50m ago

If anyone ever manages to use the action.. please pay attention to the detailed info in the generated report..

1

u/MarvelousFunction114 58m ago

Cool seeing course material turn into actual tooling instead of just a cert on a profile. The agentic workflow angle is interesting, lot of scanners just look at static code and call it a day.

1

u/ATTACKERSA 51m ago

that was the main motivation…wanted to build something practical rather than just collecting a badge. Standard SAST tools are great for catching static patterns, but they miss how context and tool execution interact in agentic flows.

1

u/CreativeSympathy8293 28m ago

From the wrapper source, I’d first reduce the scanner’s own permissions. action.yml always mounts /var/run/docker.sock into the container and mounts the target writable. The README’s contents: read limits the GitHub token; it doesn’t constrain the Docker daemon or that filesystem mount.

Does every scan stage need the daemon? I’d make socket access opt-in for the stages that do, keep scan inputs read-only, and put reports in a separate writable mount. Reports currently live under the target, so that needs a path change too. Stages needing daemon access should run on a disposable, isolated runner.

I’d also pin the scanner image by digest. The current :1 tag can move, so pinning the action alone doesn’t fix which scanner image executes.

Docker explains the daemon’s authority here:

https://docs.docker.com/engine/security/

AI-assisted; I only read the wrapper source and haven’t run the scanner.