~contribute

Contribute.

AgentOpsSec is MIT-licensed, local-first, and built in the open. Every tool is a separate repo with its own issues and releases — pick the one closest to what you want to fix.

house rules
· Small, focused, dependency-free.
· Local-first. No SaaS. No telemetry.
· MIT license. Node 20+.
· Plain language > jargon.
· Stable JSON output you can build on.
repositories · 8

Pick the right repo.

ways to help

Six things you can do today.

File an issue
Bug, false positive, missing risk category, doc gap. Use the per-tool repo so the right maintainer sees it.
Send a PR
Each project is dependency-free Node 20+. `npm run check` runs the test suite per package.
Submit a registry profile
Add an MCP server profile to mcp-radar so others can find it.
Review someone else's PR
Pull requests benefit from a second pair of eyes. Pick one and leave a comment.
Write a guide
Walkthroughs, war stories, "run this before X". Linked from the docs index when merged.
Pitch a new tool
Open an RFC issue on /stack. The bar: small, focused, dependency-free, no SaaS, no telemetry.
local dev

Each tool is standalone.

Every package is a dependency-free Node 20+ CLI with its own npm run check. Use npm link for one tool, or --use-local from the stack to wire all of your sibling checkouts together without global installs.

npm install -g <package>install any sub-tool standalone
npm run checktests for the package you are in
npm linkuse your local clone as the global binary
agentopssec --use-localorchestrator picks up sibling folders
contribute.sh
1# clone the workspace
2git clone https://github.com/AgentOpsSec/agentopssec
3cd agentopssec
4
5# work on a single tool — every project has its own check script
6cd mcp-doctor && npm link
7npm run check
8
9# run the orchestrator against your local checkout (no global installs)
10cd stack
11node ./bin/agentopssec.js status --use-local
12node ./bin/agentopssec.js scan --use-local