← Back to AI Insights
Gemini Executive Synthesis

Graphify's language support expansion to include COBOL.

Technical Positioning
An AI coding assistant that turns code into a queryable knowledge graph.
SaaS Insight & Market Implications
This feature request for COBOL language support in Graphify targets a significant, underserved market segment: legacy enterprise systems. The motivation clearly articulates the pain points of understanding and modernizing large COBOL codebases in banking, insurance, and government. Graphify's ability to visualize dependencies and call relationships would be highly valuable for these organizations. The detailed proposed approach, leveraging `tree-sitter` and mapping COBOL constructs to a graph model, demonstrates a clear path to implementation. For B2B SaaS, expanding language support to include COBOL represents a strategic move to capture a high-value, enterprise market with deep modernization needs. This could differentiate Graphify from competitors focused solely on modern languages, providing a unique value proposition for organizations grappling with technical debt and digital transformation.
Proprietary Technical Taxonomy
COBOL source code legacy enterprise systems program dependencies call relationships copybook usage modernization and migration efforts tree-sitter COBOL Parser

Raw Developer Origin & Technical Request

Source Icon GitHub Issue Apr 7, 2026
Repo: safishamsi/graphify
Add COBOL Language Support

It would be very valuable to add support for COBOL source code to Graphify, enabling analysis and graph generation for legacy enterprise systems.

Motivation:
COBOL is still widely used in banking, insurance, and government systems. Many organizations are actively trying to understand and modernize large COBOL codebases, and Graphify could be a powerful tool for:
- Visualizing program dependencies
- Understanding call relationships ("CALL", "PERFORM")
- Mapping copybook usage ("COPY")
- Supporting modernization and migration efforts

Proposed Approach:
Graphify already has a clean architecture for adding new languages via tree-sitter, so COBOL support could follow the same pattern:

1.Add COBOL Parser
- Integrate a tree-sitter grammar such as "tree-sitter-cobol"
- Ensure compatibility with COBOL85 (initially?)

2.Add File Extensions
Update detection and watch logic to include:
- ".cob"
- ".cbl"
- ".cpy" (copybooks)
- optionally ".cobol"

3.Implement LanguageConfig
Define a COBOL-specific "LanguageConfig" in "extract.py", including:
- node types for programs, sections, paragraphs
- call expressions
- copy/include handling

4.Map COBOL Constructs to Graph Model
Suggested mappings:
- "PROGRAM-ID" / "FUNCTION-ID" → top-level nodes
- "SECTION" / "PARAGRAPH" → callable units
- "CALL "program"" → "calls" edges
- "PERFORM paragraph" → internal call edges
- "COPY copybook" → "imports" / "includes" edges

5.Handle COBOL-Specific Nuances
- Fixed vs free format source
- Copybooks ("COPY"...

Developer Debate & Comments

No active discussions extracted for this entry yet.

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from safishamsi/graphify.

Extracted Positioning
Graphify's query mechanism, evolving from keyword-based BFS to embedding-based semantic search.
An AI coding assistant skill that turns code/docs into a queryable knowledge graph.
Extracted Positioning
Graphify's worked examples and their completeness, specifically the `graph.html` output.
An AI coding assistant skill that turns code/docs into a queryable knowledge graph.
Extracted Positioning
Graphify's semantic similarity feature, specifically adding local embeddings via quantized models (Gemma 4).
An AI coding assistant skill that turns code/docs into a queryable knowledge graph.
Extracted Positioning
Graphify's user onboarding and visualization of its output.
An AI coding assistant skill that turns code/docs into a queryable knowledge graph.
Extracted Positioning
Security vulnerabilities in Graphify's `_fetch_tweet` function (SSRF) and Neo4j Cypher export (injection).
An AI coding assistant skill that turns code/docs into a queryable knowledge graph.

Engagement Signals

0
Replies
open
Issue Status

Cross-Market Term Frequency

Quantifies the cross-market adoption of foundational terms like COBOL source code and legacy enterprise systems by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.