DEV Community

Maciej Myszkiewicz
Maciej Myszkiewicz

Posted on

How We Built Interactive Repository Memory (@altanix-bot learn) and Live CVE Reachability for GitHub PRs

Hi everyone! πŸ‘‹

We are a small engineering team building Altanix β€” a new, continuously evolving, privacy-first architectural code review and security assistant for GitHub Pull Requests and local CLI workflows.

Instead of comparing ourselves to other tools, we wanted to share two practical problems we encountered while testing on real open-source repositories (across Python, Rust, C++, and PHP) and how community feedback helped us solve them.


🧠 1. Teaching a Bot Your Repository Conventions (@altanix-bot learn)

Every engineering team and open-source project has its own intentional design decisions. What looks like an anti-pattern in a high-throughput database engine might be completely normal in a CLI helper script or a test fixture.

Early on, maintainers told us:

"When a review bot repeats the same warning on every commit, or flags something that is an intentional convention in our repo, it becomes noise."

To solve this, we built two things:

  1. In-Place Summary Updates: Instead of posting a brand-new wall of comments on every fix commit, Altanix updates its main PR summary in-place (PUT) and neatly collapses older revisions into a single <details> line.
  2. Neural Repo Memoryβ„’: Maintainers can teach the bot directly inside a GitHub PR comment:
@altanix-bot learn: Ignore allocation warnings in CLI reporting and display modules
Enter fullscreen mode Exit fullscreen mode

When you post that comment, Altanix stores the rule in your repository memory and applies it automatically on all future commits and Pull Requests.


πŸ›‘οΈ 2. Live CVE Dependency Auditing + AST Reachability (OSV.dev)

When a PR updates Cargo.lock, requirements.txt, poetry.lock, or package-lock.json, traditional scanners often flood the PR with alerts for vulnerabilities in transitive functions that your code never actually calls.

In Altanix, we combined:

  • Live queries to the OSV.dev vulnerability database for modified dependencies.
  • AST Call-Graph & Blast-Radius analysis (rendered as a visual Mermaid diagram in the PR summary) so reviewers can immediately see which modified functions and modules are affected.
  • Strict Privacy (SecretSanitizer): We never steal or expose your code. All diagnostic snippets are deterministically scrubbed of API keys, tokens, and credentials.

🀝 Supporting Open-Source Maintainers (14-Day Trial + 3 Months Free!)

Altanix is a young project and we are improving it every single day based on feedback from developers.

If you maintain an open-source project or want to try Altanix on your repositories:

  • You can start an instant 14-day free trial at https://altanix.dev (1-click GitHub App or GitHub Actions / CLI).
  • For open-source projects and early testers who share feedback with us: after your 14-day trial, we will gladly sponsor and extend your access for an additional 3 months 100% free of charge.

Feel free to drop a comment below or reach out directly at mmyszkiewicz@bwcoders.com β€” we would love to hear your suggestions and support your repositories! πŸ™

Top comments (0)