Contribute to Aigent.ly
The catalog, pipeline, and MCP server are fully open source. Help make AI-generated code safer for everyone — no permission needed, just a PR.
Open on GitHubAdd a stack
Add a new tech stack to the registry. We need Go, Django, Rails, iOS, and Android fully guardrailed — each needs CVE coverage, rule patterns, and synthesized guardrails.
View stack registry →Improve CVE patterns
Sharpen the ALWAYS/NEVER patterns for existing CVEs. Edit mustLines, ruleContext, or alwaysPin in seed-master.json to make rules more precise and actionable.
Read contributing guide →Improve the MCP server
The MCP server is how your IDE consumes the catalog. Better tool descriptions, smarter stack detection, or new tools — PRs welcome.
Browse mcp-server source →Report a bad rule
If an ALWAYS/NEVER directive is wrong, too generic, or contradicts another rule — open an issue. Rule quality is the product.
Open an issue →For teams
Need help rolling out Aigent.ly across an engineering team, or want custom rules for your internal stack? Reach out directly.
hello@aigent.lyWant to understand the threat model first? Read the security guide →