chore(snapshot): update canonical snapshot

[github-actions]

User description

Automated update of canonical snapshot generated from Linguist. Please review and merge.

---

PR Type

Other

---

Description

• Updates canonical snapshot.json with latest Linguist data

• Automated snapshot generation and synchronization

---

Diagram Walkthrough

flowchart LR
  Linguist["Linguist Data"] -- "generate snapshot" --> SnapshotFile["canonical/snapshot.json"]

Loading

File Walkthrough

	Relevant files
Configuration changes	snapshot.json Update canonical snapshot data                                                      canonical/snapshot.json Complete snapshot file update with latest Linguist canonical data Automated generation from upstream Linguist repository +14104/-0

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Diff Not Provided: The added/updated snapshot content was not included in the provided diff, so it cannot be verified whether any new critical actions require audit logging changes. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Diff Not Provided: The snapshot file contents were not included in the diff, so naming/structure compliance of any newly introduced fields cannot be reviewed. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Diff Not Provided: Without the actual added snapshot content and any associated generator changes, it cannot be verified whether edge cases and failures are handled appropriately. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Diff Not Provided: The diff does not include the snapshot content or any runtime error messages, so it cannot be assessed whether sensitive internal details might be exposed. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Snapshot Data Review: The snapshot file content was not available to confirm it does not contain sensitive information that could later be logged or otherwise exposed. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Diff Not Provided: The PR diff omitted the snapshot contents and any generator code, so it cannot be verified whether external inputs used to generate the snapshot are validated/sanitized and whether sensitive data is handled correctly. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Remove ambiguous TypeScript extensions from XML Remove the .ts and .tsx extensions from the XML language definition to prevent misclassifying TypeScript and TSX files as XML. canonical/snapshot.json [13112-13238] { "id": "xml", "name": "XML", "extensions": [ "xml", "adml", "admx", "ant", "axaml", "axml", "builds", "ccproj", "ccxml", "clixml", "cproject", "cscfg", "csdef", "csl", "csproj", "ct", "depproj", "dita", "ditamap", "ditaval", "dll.config", "dotsettings", "filters", "fsproj", "fxml", "glade", "gml", "gmx", "gpx", "grxml", "gst", "hzp", "iml", "ivy", "jelly", "jsproj", "kml", "launch", "mdpolicy", "mjml", "mm", "mod", "mojo", "mxml", "natvis", "ncl", "ndproj", "nproj", "nuspec", "odd", "osm", "pkgproj", "pluginspec", "proj", "props", "ps1xml", "psc1", "pt", "qhelp", "rdf", "res", "resx", "rs", "rss", "sch", "scxml", "sfproj", "shproj", "slnx", "srdf", "storyboard", "sublime-snippet", "sw", "targets", "tml", - "ts", - "tsx", "typ", "ui", "urdf", "ux", "vbproj", "vcxproj", "vsixmanifest", "vssettings", "vstemplate", "vxml", "wixproj", "workflow", "wsdl", "wsf", "wxi", "wxl", "wxs", "x3d", "xacro", "xaml", "xib", "xlf", "xliff", "xmi", "xml.dist", "xmp", "xproj", "xsd", "xspec", "xul", "zcml" ], "aliases": [ "rss", "xsd", "wsdl" ], "tree_sitter_language": null, "rca_supported": false, "ast_grep_supported": true, "mime_types": [], "family": null, "is_compiled": false, "language_type": "programming", "pattern_signatures": null } Apply / Chat Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies that associating .ts and .tsx extensions with XML would cause significant misclassification of TypeScript files, and removing them is the right approach to ensure correct language detection.	Medium
	Remove generic .txt extension Remove the generic .txt extension from the Adblock Filter List language definition to avoid misclassifying plain text files. canonical/snapshot.json [335-355] { "id": "adblock filter list", "name": "Adblock Filter List", - "extensions": [ - "txt" - ], + "extensions": [], "aliases": [ "ad block filters", "ad block", "adb", "adblock" ], "tree_sitter_language": null, "rca_supported": false, "ast_grep_supported": true, "mime_types": [], "family": null, "is_compiled": false, "language_type": "programming", "pattern_signatures": null } Apply / Chat Suggestion importance[1-10]: 8 __ Why: The suggestion correctly points out that using the generic .txt extension for Adblock Filter List would lead to widespread misclassification of plain text files, and removing it improves the accuracy of language detection.	Medium
	Remove ambiguous extension from deprecated language Remove the .cairo extension from the deprecated Cairo Zero language definition to resolve ambiguity with the current Cairo language. canonical/snapshot.json [1673-1688] { "id": "cairo zero", "name": "Cairo Zero", - "extensions": [ - "cairo" - ], + "extensions": [], "aliases": [], "tree_sitter_language": null, "rca_supported": false, "ast_grep_supported": true, "mime_types": [], "family": null, "is_compiled": false, "language_type": "programming", "pattern_signatures": null } Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies an ambiguity where both Cairo and the deprecated Cairo Zero claim the .cairo extension, and rightly proposes to remove it from the older version to improve classification accuracy.	Medium
High-level	Avoid committing large auto-generated files Avoid committing large, auto-generated files like snapshot.json to prevent repository bloat. Instead, generate this file during the build process and treat it as a build artifact. Examples: canonical/snapshot.json [1-14104] [ { "id": "1c enterprise", "name": "1C Enterprise", "extensions": [ "bsl", "os" ], "aliases": [], "tree_sitter_language": null, ... (clipped 14094 lines) Solution Walkthrough: Before: // PR adds a large, auto-generated file to version control. // File: 'canonical/snapshot.json' [ { "id": "1c enterprise", "name": "1C Enterprise", ... }, { "id": "2-dimensional array", "name": "2-Dimensional Array", ... }, ... (14000+ more lines) ] After: // The 'canonical/snapshot.json' file is not committed to the repository. // Instead, it is added to '.gitignore'. // .gitignore /canonical/snapshot.json // The build process is updated to generate this file. // build-script.sh ... echo "Generating canonical snapshot..." ./scripts/generate-snapshot > canonical/snapshot.json echo "Snapshot generated as a build artifact." ... Suggestion importance[1-10]: 5 __ Why: The suggestion raises a valid concern about repository hygiene by questioning the inclusion of a large, auto-generated file, but it's a process-level change, not a functional bug, and may conflict with the project's established workflow.	Low
More

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Diff not provided: The PR diff for canonical/snapshot.json was not available in the provided context, so it cannot be verified whether any critical actions or related metadata were introduced/changed without appropriate audit logging. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Diff not provided: The PR diff content for canonical/snapshot.json was not provided, so it cannot be verified whether any newly introduced identifiers/keys or structures are meaningfully named and self-documenting. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Diff not provided: The PR diff was not available, so it cannot be verified whether any code paths interacting with the updated snapshot include robust error handling for parsing, schema mismatches, or missing/invalid data. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Diff not provided: The PR diff content was not provided, so it cannot be verified whether any consumer of the snapshot now surfaces internal details via user-facing errors when snapshot loading/validation fails. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Diff not provided: The PR diff content was not provided, so it cannot be verified whether any new/changed logging around snapshot generation/consumption remains structured and avoids logging sensitive data contained in the snapshot. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Diff not provided: The PR diff content for canonical/snapshot.json was not provided, so it cannot be verified whether schema/format validation exists for this external data input or whether sensitive fields are handled securely by downstream consumers. Referred Code [ { Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Correct the language type for non-programming languages Correct the language_type for non-programming languages. The value is currently "programming" for all entries, but should be "data" or "markup" for languages like JSON, YAML, and HTML. canonical/snapshot.json [16] -"language_type": "programming" +"language_type": "data" Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies that the language_type is incorrectly set to "programming" for all entries, including non-programming languages like markup or data formats, which is a significant data quality issue in this generated snapshot file.	Medium
	Set ast_grep_supported based on actual support Correct the ast_grep_supported field. It is set to true for all languages, but should be false for languages not supported by ast-grep. canonical/snapshot.json [12] -"ast_grep_supported": true +"ast_grep_supported": false Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly points out that ast_grep_supported is likely wrong to be true for all languages, as ast-grep has limited language support. This is a significant data quality issue that could cause failures in dependent tools.	Medium
More