Nimbus – All-in-One Tool for Analysing & Scanning Codebases

The all-in-one developer platform for analyzing codebase architecture, static AST inspection, CVE & exploit vulnerability scanning via Google OSV.dev, Serus.ai, Snyk, supply chain security, and automated technical debt remediation.

Core Capabilities

  • Interactive System Architecture & DAG Flow Topology

    Visual mapping across UI, Services, Business Logic, and Data layers with automatic circular dependency detection.

  • Real-Time CVE & Exploit Vulnerability Scanning

    Live queries against the distributed Google OSV.dev database and hub integrations with Serus.ai, Snyk, Socket.dev, and Semgrep. Zero BYOK keys consumed for scanning.

  • Deep Static AST Inspection & Multi-LLM BYOK Intelligence

    Bring Your Own Key support for OpenRouter, OpenAI, Anthropic Claude, Azure OpenAI, and GitHub Models.

  • Technical Debt Remediation & Operational Hygiene

    Automated standards checklists and prioritized remediation queue with instant terminal commands and multi-format exports.

  • Dual Trend Engines: Nimbus Trends & GitHub Trends

    Tracking both developer exploration patterns on Nimbus and worldwide trending repositories synchronized directly with the database.

Frequently Asked Questions

What is Nimbus?
Nimbus is the all-in-one developer platform for analyzing codebase architecture, static AST inspection, CVE & exploit vulnerability scanning via Google OSV.dev and third-party security scanners, and automated technical debt remediation.
Which AI and LLM models are supported via BYOK?
Nimbus operates on a strict Bring Your Own Key (BYOK) model. We support OpenRouter, OpenAI (GPT-4o, GPT-4o-mini), Anthropic Claude (Claude 3.5 Sonnet), Azure OpenAI, and GitHub Models. Your API keys are stored strictly in your browser memory and are never transmitted to server telemetry.
Does vulnerability scanning consume LLM API keys or tokens?
No. Vulnerability scanning against Google OSV.dev, package manifest dependency resolution, and static AST verification run directly against official CVE databases with zero BYOK API keys consumed and zero AI tokens used.
How does the System Architecture flow topology work?
Nimbus automatically parses repository structures and generates an interactive Directed Acyclic Graph (DAG) visualizing dependencies across UI components, service layers, business logic, and data stores with automated circular dependency detection.
How are Nimbus Trends and GitHub Trends calculated?
Nimbus features dual trend engines synchronized with the database. Nimbus Trends ranks repositories based on actual developer exploration and visit volume tracked through the Nimbus interface, while GitHub Trends synchronizes weekly trending repositories worldwide with automated database deduplication.