ArangoDB Migration Check
No liveness check has reached it yet; it is registered on the VS Code Marketplace and has been in the index since 13 Oct 2026. How this is checked
A VS Code extension that scans compose files, Dockerfiles, Helm charts, package manifests, and environment files for Neo4j images, licenses, drivers, and Bolt URIs. It dates detected dependencies against Neo4j end-of-life information and provides migration guidance for development teams.
Inferred · not functionally tested
Overview
6 featuresPurpose: Identifies Neo4j dependencies and outdated components across project files so teams can plan migration before end-of-life deadlines.
Inferred · not functionally tested
Audience: developers and platform engineers maintaining graph database applications
Inferred · not functionally tested
Functions: data_extraction, monitoring
Inferred · not functionally tested
Interfaces: API: unknown · MCP: unknown · CLI: unknown · Self-hosting: unknown
Recorded constraints: pricing: free · license: Proprietary · platforms: WEB · deployment: browser, windows, macos, linux
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: unknown.
ArangoDB Migration Check is a Static analysis & linters project. Inferred · not functionally tested: It identifies Neo4j dependencies and outdated components across project files so teams can plan migration before end-of-life deadlines. Inferred · not functionally tested: It is built as a B2B product for developers and platform engineers maintaining graph database applications. Basis unknown · not verified: It is available for free. Basis unknown · not verified: ArangoDB Migration Check is available on the web, Windows, macOS, and Linux.
Behind ArangoDB Migration Check is ReadyStack, and it first shipped in 2026. Inferred · not functionally tested: Key capabilities include dependency scanning, end-of-life dates, and dockerfile analysis.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Dependency scanning
- End-of-life dates
- Dockerfile analysis
- Compose analysis
- Helm analysis
- Package scanning
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed13 Oct · 03:16 UTCArangoDB Migration Check: Neo4j End-of-Life Map seen via VS Code MarketplaceSource: VS Code Marketplace · Open
Frequently asked questions about ArangoDB Migration Check
- What does ArangoDB Migration Check do?
- Inferred · not functionally tested: ArangoDB Migration Check identifies Neo4j dependencies and outdated components across project files so teams can plan migration before end-of-life deadlines. It is catalogued under Static analysis & linters on PulseGate.
- Who is ArangoDB Migration Check for?
- Inferred · not functionally tested: ArangoDB Migration Check is a B2B product built for developers and platform engineers maintaining graph database applications.
- Is ArangoDB Migration Check free?
- Basis unknown · not verified: Yes — ArangoDB Migration Check is free to use.
- What platforms does ArangoDB Migration Check run on?
- Basis unknown · not verified: ArangoDB Migration Check runs on the web, Windows, macOS, and Linux.
- Is ArangoDB Migration Check still maintained?
- Unverified. ArangoDB Migration Check has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
- What are alternatives to ArangoDB Migration Check?
- Similar projects tracked by PulseGate include Codeberg / GitLab.com Anonymous Fetch Lint, PortClash, and Apache ECharts Migration.Codeberg / GitLab.com Anonymous Fetch LintPortClashApache ECharts Migration
- Who develops ArangoDB Migration Check?
- ArangoDB Migration Check is developed by ReadyStack.
- When did ArangoDB Migration Check launch?
- ArangoDB Migration Check first shipped in 2026.
Also in Static analysis & linters
Same category — not a similarity match