{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"vscode-bitlang-cobol","slug":"cobol","name":"COBOL","type":"extension","url":"https://marketplace.visualstudio.com/items?itemName=bitlang.cobol","page_url":"https://unfragile.ai/cobol","categories":["code-editors"],"tags":["__ext_asm","__ext_assemble","__ext_bib","__ext_bms","__ext_cbl","__ext_cblcpy","__ext_cblle","__ext_cblproj","__ext_cblsrce","__ext_cntl","__ext_cob","__ext_cobcopy","__ext_cobol","__ext_copybook","__ext_cpy","__ext_dds","__ext_def","__ext_dir","__ext_eco","__ext_evt","__ext_fd","__ext_hla","__ext_hlasm","__ext_inc","__ext_include","__ext_jcl","__ext_job","__ext_lks","__ext_mac","__ext_mfs","__ext_mfu","__ext_mlc","__ext_mnu","__ext_pc","__ext_pcb","__ext_pci","__ext_pco","__ext_pcx","__ext_pdv","__ext_pl1","__ext_pli","__ext_plinc","__ext_prc","__ext_prd","__ext_prep","__ext_proc","__ext_rex","__ext_rexx","__ext_scb","__ext_scbl","__ext_sel","__ext_sl","__ext_spb","__ext_sqlcblle","__ext_src","__ext_ss","__ext_wks","__ext_wrk","__web_extension","ACUCOBOL","acucobol-gt","BITLANG-COBOL","bms","bmsmap","cics","cobol","COBOL_ACU_LISTFILE","COBOL_MF_LISTFILE","COBOL_MF_PREP","COBOL_PCOB_LISTFILE","cobolit","cobol-it","copilot","dir","directivesmf","dirfile","hlasm","ibmi","ilecobol","ims","jcl","keybindings","markdown-acucobol-injection","markdown-cobol-injection","markdown-cobolit-injection","markdown-hlasm-injection","markdown-jcl-injection","markdown-pli-injection","mfcobol","mfu","mfunit","mfupp_dir","multi-root ready","ocds","OpenESQL","opentext","pl/i","plaintext","pli","rexx","RMCOBOL","rocket cobol","snippet","UnitTestReport","utreport","visual cobol","xml"],"pricing":{"model":"freemium","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"vscode-bitlang-cobol__cap_0","uri":"capability://code.generation.editing.multi.dialect.cobol.syntax.highlighting.with.fixed.format.margin.support","name":"multi-dialect cobol syntax highlighting with fixed-format margin support","description":"Provides tokenization-based syntax colorization for 5+ COBOL dialects (Rocket COBOL, ACUCOBOL-GT, COBOL-IT, RMCOBOL, ILECOBOL) and related languages (JCL, PL/I, HLASM, REXX) with awareness of COBOL's fixed-format column structure (columns 1-6 sequence area, 7 indicator area, 8-11 area A, 12-72 area B). Uses dialect-specific keyword and reserved word definitions to apply context-aware colorization inline within the VS Code editor without requiring external compilation or language server.","intents":["I need to read legacy COBOL code with proper syntax highlighting across multiple enterprise COBOL variants","I want to distinguish between COBOL fixed-format structural columns and actual code content visually","I need to work with mixed-language mainframe projects (COBOL + JCL + PL/I) in a single editor"],"best_for":["Enterprise developers maintaining legacy COBOL systems on IBM mainframes or midrange systems","Teams migrating between COBOL dialects (Rocket to COBOL-IT, ACUCOBOL to RMCOBOL)","Mainframe DevOps engineers reviewing JCL and COBOL source in version control"],"limitations":["Syntax highlighting is static and dialect-specific — switching dialects requires manual file association or configuration change","Fixed-format margin support is visual only; does not enforce or validate column boundaries during editing","Partial support for RMCOBOL and ILECOBOL (colorization only, no IntelliSense or advanced features)","No semantic understanding of COBOL structure — highlights based on keyword matching, not AST parsing"],"requires":["Visual Studio Code 1.0+ (specific minimum version unknown)","File extension or workspace setting to associate .cbl, .cobol, .cob files with COBOL dialect"],"input_types":["COBOL source files (.cbl, .cobol, .cob, .cblle, .sqlcblle)","Copybook files (.cpy, .cblcopy, .cobcopy, .inc, .include)","JCL files (.jcl, .job)","PL/I files (.pli, .pl1, .plinc)","HLASM files (.asm, .hlasm, .assemble)","REXX files (.rex, .rexx)"],"output_types":["Colorized source code in VS Code editor","Syntax-highlighted text for copy/paste or export"],"categories":["code-generation-editing","syntax-highlighting"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-bitlang-cobol__cap_1","uri":"capability://code.generation.editing.context.aware.intellisense.keyword.completion.with.case.variant.suggestions","name":"context-aware intellisense keyword completion with case-variant suggestions","description":"Provides real-time code completion for COBOL keywords, intrinsic functions, and copybook names triggered via VS Code's standard IntelliSense UI (Ctrl+Space). Generates completion suggestions in three case variants (lowercase, UPPERCASE, CamelCase) based on dialect-specific keyword definitions and current editor context. Completion is triggered on partial keyword input and filters suggestions by prefix matching without requiring external language server or network calls.","intents":["I want to autocomplete COBOL keywords without memorizing exact spelling or case conventions","I need to insert copybook names and intrinsic functions with intelligent suggestions","I want to switch between coding style conventions (lowercase vs UPPERCASE) without manual refactoring"],"best_for":["COBOL developers new to a specific dialect or coding standard","Teams enforcing mixed case conventions across legacy and modern COBOL code","Developers working in environments with strict keyword capitalization rules"],"limitations":["Completion is keyword-based only — does not suggest variable names, paragraph names, or semantic context","Case variants are static suggestions, not learned from project conventions","No parameter hints or function signature completion for intrinsic functions","Copybook completion requires manual file discovery; no automatic include path resolution"],"requires":["Visual Studio Code 1.0+","IntelliSense enabled in VS Code settings (default: true)","COBOL file open in active editor"],"input_types":["Partial keyword text in COBOL source","Copybook file names in COPY statements"],"output_types":["Filtered list of keyword completions with case variants","Inserted keyword or copybook name into editor"],"categories":["code-generation-editing","code-completion"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-bitlang-cobol__cap_10","uri":"capability://code.generation.editing.optional.xedit.style.keybindings.for.mainframe.editor.familiarity","name":"optional xedit-style keybindings for mainframe editor familiarity","description":"Offers optional keybinding configuration that emulates xedit (IBM mainframe editor) keyboard shortcuts, allowing developers familiar with mainframe editing environments to use familiar key combinations in VS Code. Keybindings are optional and can be enabled/disabled via extension settings, providing a bridge for mainframe developers transitioning to modern IDEs.","intents":["I want to use xedit keybindings in VS Code because I'm familiar with mainframe editors","I need to reduce context-switching when working across mainframe and modern development tools","I want to maintain muscle memory for keyboard shortcuts from my mainframe development experience"],"best_for":["Mainframe developers transitioning from xedit or other mainframe editors to VS Code","Teams with mixed mainframe and modern development backgrounds","Organizations standardizing on VS Code for legacy COBOL development"],"limitations":["xedit keybindings are optional and must be explicitly enabled in settings","Specific keybinding mappings are undocumented — unclear which xedit commands are supported","Keybindings may conflict with other VS Code extensions or user-defined keybindings","No xedit command emulation beyond keybindings — VS Code behavior differs from xedit"],"requires":["Visual Studio Code 1.0+","Extension setting to enable xedit keybindings (specific setting name unknown)"],"input_types":["Keyboard input"],"output_types":["VS Code editor commands executed based on xedit-style keybindings"],"categories":["code-generation-editing","keybindings"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-bitlang-cobol__cap_11","uri":"capability://code.generation.editing.cobol.tab.key.support.with.fixed.format.column.awareness","name":"cobol tab key support with fixed-format column awareness","description":"Implements configurable tab key behavior that respects COBOL's fixed-format column structure (columns 1-6 sequence area, 7 indicator area, 8-11 area A, 12-72 area B). Tab key can be configured to jump to the next COBOL column boundary (e.g., from column 7 to column 8, or from column 11 to column 12) rather than inserting spaces, enabling rapid navigation within fixed-format constraints. Reduces manual spacing and improves editing efficiency in fixed-format COBOL.","intents":["I want to navigate between COBOL fixed-format column areas (indicator area, area A, area B) using the tab key","I need to quickly position the cursor at the correct column for COBOL statements","I want to reduce manual spacing when editing fixed-format COBOL code"],"best_for":["Developers working with legacy fixed-format COBOL code","Teams enforcing strict COBOL column structure compliance","Mainframe developers familiar with fixed-format editing constraints"],"limitations":["Tab key behavior is configurable but mechanism is undocumented — unclear how to customize column boundaries","Tab behavior may conflict with VS Code's default tab settings or other extensions","Does not validate that code respects COBOL column boundaries — only aids navigation","Fixed-format column awareness is editor-only — does not affect compilation or code execution"],"requires":["Visual Studio Code 1.0+","COBOL file open in active editor","Tab key support enabled in extension settings (specific setting name unknown)"],"input_types":["Tab key press in editor"],"output_types":["Cursor movement to next COBOL column boundary"],"categories":["code-generation-editing","editor-behavior"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-bitlang-cobol__cap_12","uri":"capability://code.generation.editing.development.container.integration.for.visual.cobol.and.mainframe.environments","name":"development container integration for visual cobol and mainframe environments","description":"Supports development container workflows (VS Code Dev Containers) that include COBOL compilation and debugging tools (Visual COBOL, Rocket COBOL). Enables developers to use the extension within containerized development environments that provide COBOL compiler, debugger, and mainframe connectivity without requiring local installation. Integrates with VS Code's Dev Containers extension to provide seamless COBOL development in isolated, reproducible environments.","intents":["I want to develop COBOL in a containerized environment without installing COBOL tools locally","I need to ensure my team uses consistent COBOL compiler versions and configurations","I want to integrate COBOL development with CI/CD pipelines using containers"],"best_for":["Teams using VS Code Dev Containers for standardized development environments","Organizations with strict tool version management or licensing requirements","DevOps engineers building containerized COBOL development pipelines"],"limitations":["Dev Container integration requires VS Code Dev Containers extension and Docker/Podman","Container configuration is user-defined — extension does not provide pre-built COBOL containers","Debugging requires compatible COBOL debugger in container (e.g., Visual COBOL debugger)","Performance may degrade compared to native development due to container overhead","File synchronization between host and container may cause latency"],"requires":["Visual Studio Code 1.0+","VS Code Dev Containers extension","Docker or Podman installed and running","Dev container configuration (.devcontainer/devcontainer.json) with COBOL tools"],"input_types":["COBOL source files in container workspace"],"output_types":["Syntax highlighting, IntelliSense, and navigation within containerized environment"],"categories":["code-generation-editing","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-bitlang-cobol__cap_2","uri":"capability://code.generation.editing.structural.code.navigation.with.division.section.and.paragraph.shortcuts","name":"structural code navigation with division, section, and paragraph shortcuts","description":"Enables rapid navigation within COBOL programs by parsing program structure (IDENTIFICATION DIVISION, ENVIRONMENT DIVISION, DATA DIVISION, PROCEDURE DIVISION, sections, paragraphs) and exposing navigation shortcuts via VS Code's command palette and breadcrumb UI. Implements outline/breadcrumb generation that reflects COBOL's hierarchical structure, allowing developers to jump to specific divisions, sections, or paragraphs without scrolling through large files. Uses static parsing of COBOL keywords to identify structural boundaries.","intents":["I need to quickly jump to a specific section or paragraph in a 5000+ line COBOL program","I want to see the program structure (divisions and sections) in the outline panel","I need to navigate between PROCEDURE DIVISION paragraphs without manual searching"],"best_for":["Developers working with large legacy COBOL programs (>2000 lines)","Teams performing code reviews and needing to locate specific sections quickly","Mainframe developers familiar with COBOL's division-based structure"],"limitations":["Navigation is text-based keyword matching — does not validate COBOL syntax or handle malformed programs gracefully","Outline generation may be slow or incomplete for very large files (>50K lines) or files with non-standard formatting","Does not support nested paragraph structures or PERFORM VARYING scope analysis","Breadcrumb navigation does not show variable scope or data structure hierarchy"],"requires":["Visual Studio Code 1.0+","COBOL file with standard division/section/paragraph structure","Outline view enabled in VS Code"],"input_types":["COBOL source file with IDENTIFICATION, ENVIRONMENT, DATA, PROCEDURE divisions"],"output_types":["Outline tree in VS Code outline panel","Breadcrumb navigation in editor header","Jump-to-location command results"],"categories":["code-generation-editing","code-navigation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-bitlang-cobol__cap_3","uri":"capability://code.generation.editing.copybook.drag.and.drop.insertion.with.automatic.copy.statement.generation","name":"copybook drag-and-drop insertion with automatic copy statement generation","description":"Allows developers to drag copybook files (.cpy, .cblcopy, .cobcopy) from the file explorer and drop them into COBOL source code, automatically generating a COPY statement with the copybook name. Integrates with VS Code's drag-and-drop API to detect copybook file types and insert the appropriate COBOL COPY syntax without manual typing. Reduces friction in including external data structures and common code segments.","intents":["I want to include a copybook in my COBOL program without manually typing the COPY statement","I need to quickly reference a copybook file from the project structure","I want to avoid typos in copybook names when adding COPY statements"],"best_for":["Developers working with large copybook libraries (>50 copybooks)","Teams enforcing strict copybook naming conventions","Mainframe developers familiar with drag-and-drop workflows"],"limitations":["Drag-and-drop only works for copybook files with recognized extensions (.cpy, .cblcopy, .cobcopy, .inc, .include)","Does not resolve copybook include paths or validate copybook existence at insertion time","Generated COPY statement uses only the filename — does not support COPY ... IN ... syntax for library paths","No automatic indentation or placement validation — inserted COPY statement may violate COBOL fixed-format column rules"],"requires":["Visual Studio Code 1.0+","Copybook file visible in VS Code file explorer","COBOL source file open in active editor","Drag-and-drop enabled in VS Code (default: true)"],"input_types":["Copybook file (.cpy, .cblcopy, .cobcopy, .inc, .include) from file explorer"],"output_types":["COPY statement inserted into COBOL source at drop location"],"categories":["code-generation-editing","code-insertion"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-bitlang-cobol__cap_4","uri":"capability://code.generation.editing.minimap.section.boundary.visualization.with.customizable.color.coding","name":"minimap section boundary visualization with customizable color coding","description":"Renders visual markers on VS Code's minimap and overview ruler to highlight COBOL program structure boundaries (divisions, sections, paragraphs) with customizable colors for each structural level. Implements VS Code's decoration API to overlay colored regions on the minimap, allowing developers to quickly identify program structure at a glance without reading code. Colors are configurable per structural level (division, section, paragraph) with separate light and dark theme variants and alpha transparency control.","intents":["I want to see the overall structure of a large COBOL program at a glance on the minimap","I need to quickly identify where sections and paragraphs are located in a 10000+ line file","I want to customize minimap colors to match my team's coding standards or accessibility needs"],"best_for":["Developers working with very large COBOL programs (>5000 lines)","Teams with accessibility requirements (high-contrast color schemes)","Mainframe developers familiar with visual code structure indicators"],"limitations":["Minimap rendering performance may degrade for very large files (>50K lines) with many structural boundaries","Color customization is global — cannot be set per-file or per-project without manual configuration","Minimap markers are visual only — do not provide clickable navigation or hover information","Boundary detection is text-based keyword matching — may produce false positives in comments or string literals"],"requires":["Visual Studio Code 1.0+","Minimap enabled in VS Code settings (default: true)","COBOL file with standard division/section/paragraph structure","Configuration settings: coboleditor.enable_minimap_section_boundaries (boolean)"],"input_types":["COBOL source file with divisions, sections, paragraphs"],"output_types":["Colored regions on VS Code minimap and overview ruler"],"categories":["code-generation-editing","visualization"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-bitlang-cobol__cap_5","uri":"capability://code.generation.editing.rule.based.source.code.linting.for.internal.cobol.standards","name":"rule-based source code linting for internal cobol standards","description":"Implements a configurable linter that validates COBOL source code against user-defined or built-in rules for internal coding standards (naming conventions, indentation, comment placement, keyword capitalization). Uses pattern matching and static analysis to identify violations without compilation or external services. Violations are reported inline in the VS Code editor with diagnostic messages, allowing developers to fix issues before committing code.","intents":["I want to enforce consistent coding standards across my COBOL codebase","I need to catch common style violations (incorrect indentation, missing comments) before code review","I want to validate that variable names follow my team's naming conventions"],"best_for":["Teams with strict COBOL coding standards or style guides","Large enterprises maintaining legacy COBOL systems with multiple developers","Organizations migrating COBOL code and needing to enforce new standards"],"limitations":["Linting rules are text-based pattern matching — cannot enforce semantic rules (e.g., variable usage, data type consistency)","Rule definition mechanism is undocumented — unclear how to create custom rules or modify built-in rules","No built-in rules provided — linter requires manual configuration before use","Linting performance may degrade for very large files (>50K lines) with complex rule sets","No integration with CI/CD pipelines or pre-commit hooks (requires manual VS Code execution)"],"requires":["Visual Studio Code 1.0+","COBOL file open in active editor","Linter rules configured in extension settings (configuration mechanism unknown)"],"input_types":["COBOL source code"],"output_types":["Inline diagnostic messages in VS Code editor","Linting violation list in Problems panel"],"categories":["code-generation-editing","linting"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-bitlang-cobol__cap_6","uri":"capability://code.generation.editing.text.based.find.all.references.for.cobol.variables.paragraphs.and.sections","name":"text-based find-all-references for cobol variables, paragraphs, and sections","description":"Implements a find-all-references feature that locates all occurrences of a selected COBOL identifier (variable name, paragraph name, section name) within the current file and workspace using text-based pattern matching. Results are displayed in VS Code's Find Results panel with file location and line number, enabling developers to understand identifier usage and impact of potential refactoring. Uses case-sensitive or case-insensitive matching based on COBOL dialect conventions.","intents":["I need to find all uses of a variable before refactoring or renaming it","I want to understand the scope and impact of a paragraph or section","I need to identify dead code (paragraphs or variables with no references)"],"best_for":["Developers performing code refactoring or maintenance on legacy COBOL systems","Teams analyzing code impact before making changes","Mainframe developers understanding complex program dependencies"],"limitations":["Text-based matching produces false positives — matches partial names and identifiers in comments/strings","No semantic understanding of scope — cannot distinguish between local and global variables or shadowed names","Does not follow COBOL's PERFORM or CALL semantics — may miss indirect references","Case sensitivity depends on dialect configuration — may miss references with different capitalization","Performance degrades for very common identifiers (e.g., 'I', 'X') in large codebases"],"requires":["Visual Studio Code 1.0+","COBOL file open in active editor","Identifier (variable, paragraph, section) selected in editor"],"input_types":["Selected text in COBOL source (identifier name)"],"output_types":["Find Results panel with all matching locations","File references with line numbers and context"],"categories":["code-generation-editing","code-navigation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-bitlang-cobol__cap_7","uri":"capability://code.generation.editing.text.based.identifier.renaming.with.case.preserving.substitution","name":"text-based identifier renaming with case-preserving substitution","description":"Enables renaming of COBOL identifiers (variable names, paragraph names, section names) across a file or workspace using text-based find-and-replace with case-preserving substitution. Renames all occurrences of the selected identifier while attempting to preserve the original case pattern (e.g., 'myVar' → 'newVar', 'MY-VAR' → 'NEW-VAR'). Integrated with VS Code's rename refactoring UI (F2 key).","intents":["I want to rename a variable or paragraph throughout my program without manual find-and-replace","I need to refactor code while preserving COBOL naming conventions (uppercase, hyphenated names)","I want to update identifier names across multiple files in my project"],"best_for":["Developers refactoring COBOL code with strict naming conventions","Teams standardizing variable names across legacy systems","Mainframe developers improving code readability through renaming"],"limitations":["Text-based renaming produces false positives — renames partial matches and identifiers in comments/strings","No semantic understanding of scope — renames all occurrences regardless of scope or shadowing","Case-preserving substitution is heuristic-based — may fail for unusual naming patterns","Does not update copybook references or external file dependencies","Renaming across workspace may be slow for large projects (>10K files)"],"requires":["Visual Studio Code 1.0+","COBOL file open in active editor","Identifier (variable, paragraph, section) selected in editor"],"input_types":["Selected identifier name in COBOL source","New identifier name (user input)"],"output_types":["Updated COBOL source with all occurrences renamed","Refactoring preview showing all changes"],"categories":["code-generation-editing","refactoring"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-bitlang-cobol__cap_8","uri":"capability://code.generation.editing.automated.code.formatting.utilities.column.removal.comment.stripping.case.conversion","name":"automated code formatting utilities (column removal, comment stripping, case conversion)","description":"Provides a suite of automated code formatting utilities accessible via command palette to standardize COBOL source code: (1) column number removal — strips sequence numbers from columns 73-80 in fixed-format COBOL; (2) program identification area removal — removes columns 1-6 (sequence area) and column 7 (indicator area); (3) comment removal — strips all comment lines (lines with '*' in column 7); (4) keyword/field case conversion — converts keywords and identifiers to uppercase, lowercase, or mixed case; (5) column number resequencing — regenerates sequence numbers in columns 73-80; (6) storage item alignment — aligns data structure definitions for readability. Each utility operates on the current file or selection.","intents":["I need to remove sequence numbers from legacy COBOL code before migrating to free-format","I want to standardize keyword capitalization across my codebase","I need to strip comments from COBOL code for analysis or obfuscation","I want to reformat data definitions for better readability"],"best_for":["Teams migrating COBOL from fixed-format to free-format","Developers standardizing legacy COBOL code before refactoring","Mainframe engineers preparing code for analysis or archival"],"limitations":["Formatting utilities are destructive — no built-in undo beyond VS Code's undo stack","Column removal assumes standard COBOL fixed-format layout — may fail for non-standard or malformed code","Comment removal is text-based — removes all lines with '*' in column 7, including valid code with '*' in that position","Case conversion is global — cannot selectively convert keywords vs identifiers","Storage item alignment is heuristic-based — may produce incorrect results for complex data structures","No preview or dry-run mode — changes are applied immediately"],"requires":["Visual Studio Code 1.0+","COBOL file open in active editor","Fixed-format COBOL code for column-based utilities"],"input_types":["COBOL source code (full file or selection)"],"output_types":["Reformatted COBOL source code"],"categories":["code-generation-editing","code-formatting"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-bitlang-cobol__cap_9","uri":"capability://code.generation.editing.text.to.hex.literal.conversion.for.cobol.string.constants","name":"text-to-hex literal conversion for cobol string constants","description":"Provides a utility to convert COBOL string literals (text in quotes) to hexadecimal representation for use in COBOL MOVE or VALUE statements. Converts selected text to hex format (e.g., 'ABC' → 'X'414243') and inserts the result into the editor. Useful for handling non-printable characters, binary data, or EBCDIC-encoded strings in mainframe COBOL.","intents":["I need to represent non-printable characters or binary data in COBOL string literals","I want to convert text to hex format for EBCDIC-encoded mainframe data","I need to work with COBOL MOVE statements that require hex literals"],"best_for":["Mainframe COBOL developers working with binary or EBCDIC data","Teams handling low-level data manipulation or protocol parsing","Developers integrating COBOL with external systems requiring hex-encoded data"],"limitations":["Conversion assumes ASCII or UTF-8 input — does not handle EBCDIC or other mainframe encodings","No validation of hex output — does not verify that resulting hex literal is valid COBOL syntax","No reverse conversion (hex to text) provided","Does not handle escape sequences or special characters in input text"],"requires":["Visual Studio Code 1.0+","COBOL file open in active editor","Text selected in editor"],"input_types":["Text string (selected in editor)"],"output_types":["Hexadecimal literal in COBOL format (X'...')"],"categories":["code-generation-editing","data-conversion"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":45,"verified":false,"data_access_risk":"high","permissions":["Visual Studio Code 1.0+ (specific minimum version unknown)","File extension or workspace setting to associate .cbl, .cobol, .cob files with COBOL dialect","Visual Studio Code 1.0+","IntelliSense enabled in VS Code settings (default: true)","COBOL file open in active editor","Extension setting to enable xedit keybindings (specific setting name unknown)","Tab key support enabled in extension settings (specific setting name unknown)","VS Code Dev Containers extension","Docker or Podman installed and running","Dev container configuration (.devcontainer/devcontainer.json) with COBOL tools"],"failure_modes":["Syntax highlighting is static and dialect-specific — switching dialects requires manual file association or configuration change","Fixed-format margin support is visual only; does not enforce or validate column boundaries during editing","Partial support for RMCOBOL and ILECOBOL (colorization only, no IntelliSense or advanced features)","No semantic understanding of COBOL structure — highlights based on keyword matching, not AST parsing","Completion is keyword-based only — does not suggest variable names, paragraph names, or semantic context","Case variants are static suggestions, not learned from project conventions","No parameter hints or function signature completion for intrinsic functions","Copybook completion requires manual file discovery; no automatic include path resolution","xedit keybindings are optional and must be explicitly enabled in settings","Specific keybinding mappings are undocumented — unclear which xedit commands are supported","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.65,"quality":0.35,"ecosystem":0.35000000000000003,"match_graph":0.25,"freshness":0.75,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:34.118Z","last_scraped_at":"2026-05-03T15:20:32.168Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=cobol","compare_url":"https://unfragile.ai/compare?artifact=cobol"}},"signature":"1XzB67qJ0A3r2cakWMeodjoatJdEQW9+8tLJ5TJ0vjnAMyqYLN/NkqcRbHpFHtiRco2EzNcbgBTg4IJq0oCYCw==","signedAt":"2026-06-22T09:14:58.953Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/cobol","artifact":"https://unfragile.ai/cobol","verify":"https://unfragile.ai/api/v1/verify?slug=cobol","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}