{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"vscode-swark-swark","slug":"swark","name":"Swark","type":"extension","url":"https://marketplace.visualstudio.com/items?itemName=swark.swark","page_url":"https://unfragile.ai/swark","categories":["code-editors"],"tags":["keybindings"],"pricing":{"model":"freemium","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"vscode-swark-swark__cap_0","uri":"capability://code.generation.editing.llm.driven.codebase.to.architecture.diagram.generation","name":"llm-driven codebase-to-architecture diagram generation","description":"Analyzes selected folder contents by sending full source code to GitHub Copilot, which performs language-agnostic structural inference to identify architectural components, relationships, and dependencies. Outputs Mermaid.js diagram syntax representing the inferred architecture. Uses LLM reasoning rather than deterministic AST parsing, enabling support across all programming languages without language-specific parsers.","intents":["Generate architecture diagrams from existing codebases without manual documentation","Quickly understand unfamiliar repository structure during onboarding","Create visual documentation of legacy code systems for knowledge transfer","Validate architectural patterns in code review workflows"],"best_for":["Solo developers and small teams documenting existing codebases","Engineering leads onboarding new team members to complex repositories","Technical writers generating architecture documentation from source code","Teams maintaining legacy systems without existing architecture diagrams"],"limitations":["LLM-based inference is non-deterministic — same codebase may produce slightly different diagrams across runs","No control over diagram granularity or abstraction level — Copilot determines what constitutes an 'architectural component'","Requires GitHub Copilot authentication; cannot function offline or with alternative LLM providers","Performance degrades with very large codebases due to token limits in Copilot API (exact limit unknown)","No support for incremental updates — each invocation generates a new diagram from scratch"],"requires":["Visual Studio Code (version not specified, assume recent stable)","GitHub Copilot extension installed and authenticated (free tier now available)","Active network connection to GitHub Copilot API","User-selected folder with readable source code files"],"input_types":["source code files (all languages supported via LLM inference)","directory structure metadata","optional test files for coverage visualization"],"output_types":["Mermaid.js diagram syntax (markdown format)","metadata log file with timestamp and analyzed file list"],"categories":["code-generation-editing","planning-reasoning","documentation-generation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-swark-swark__cap_1","uri":"capability://automation.workflow.interactive.folder.selection.and.scoped.code.analysis","name":"interactive folder selection and scoped code analysis","description":"Provides a file picker dialog allowing users to select a specific folder within their VS Code workspace for analysis. Extension reads all files within the selected directory (excluding files outside workspace scope) and sends their full content to Copilot. Scope is strictly bounded to user-selected folder; no automatic recursive analysis of parent directories or external dependencies.","intents":["Analyze specific modules or subsystems within a monorepo without processing the entire codebase","Control which code is sent to Copilot for privacy or performance reasons","Generate separate diagrams for different architectural layers or services"],"best_for":["Developers working in monorepos who want to diagram individual services or modules","Teams with privacy concerns who want to limit code exposure to specific folders","Projects where different architectural layers need separate visualizations"],"limitations":["No recursive analysis of dependencies outside selected folder — external imports/dependencies are not automatically included","No filtering options for file types, sizes, or patterns — all files in folder are analyzed","No batch processing — one folder per invocation; analyzing multiple subsystems requires multiple command executions","File system access is read-only and limited to workspace root; cannot access files outside VS Code workspace"],"requires":["Visual Studio Code with Swark extension installed","Readable source code files in selected folder","GitHub Copilot authentication"],"input_types":["folder path (selected via dialog)","all file types within folder"],"output_types":["folder metadata (file list, directory structure)"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-swark-swark__cap_2","uri":"capability://code.generation.editing.mermaid.js.diagram.code.generation.and.editing","name":"mermaid.js diagram code generation and editing","description":"Generates Mermaid.js diagram syntax representing the inferred architecture and writes it to a markdown file in the `swark-output` folder with timestamp-based naming (`<date>__<time>__diagram.md`). Generated Mermaid code is human-readable and fully editable post-generation, allowing users to refine or customize diagrams after creation. Output is rendered in VS Code as markdown or via external Mermaid Live Editor link.","intents":["Export architecture diagrams in a version-controllable, text-based format","Manually refine AI-generated diagrams to match team standards or add missing details","Integrate generated diagrams into documentation systems that support Mermaid syntax","Preview diagrams in VS Code with optional Mermaid Markdown Preview extension"],"best_for":["Teams using Mermaid.js in documentation pipelines (e.g., Markdown-based wikis, GitHub README files)","Developers who want to version-control architecture diagrams as code","Projects where post-generation diagram customization is expected workflow"],"limitations":["Output format is Mermaid.js only — no support for PlantUML, SVG, PNG, or other diagram formats","Mermaid version targeted is unknown; compatibility with specific Mermaid features is undocumented","No built-in diagram preview in extension — requires optional Mermaid Markdown Preview extension or external Mermaid Live Editor","Diagram types are limited to architecture diagrams; sequence diagrams, class diagrams, and other Mermaid types are not mentioned as supported","Output files accumulate in `swark-output` folder with no automatic cleanup or versioning strategy"],"requires":["Visual Studio Code with Swark extension","Write access to workspace root (to create `swark-output` folder)","Optional: Mermaid Markdown Preview extension for in-editor preview","Optional: Mermaid Live Editor access for external preview"],"input_types":["LLM-inferred architecture structure (from Copilot)"],"output_types":["Mermaid.js diagram syntax (markdown file)","metadata log file"],"categories":["code-generation-editing","text-generation-language"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-swark-swark__cap_3","uri":"capability://tool.use.integration.github.copilot.integrated.authentication.and.api.communication","name":"github copilot-integrated authentication and api communication","description":"Leverages existing GitHub Copilot authentication within VS Code, eliminating need for separate API key configuration or credential management. Extension communicates exclusively with GitHub Copilot API (no third-party services involved) to send code for analysis and receive diagram generation instructions. Authentication state is inherited from Copilot extension; no additional setup required beyond Copilot installation.","intents":["Use Swark without managing additional API keys or authentication credentials","Ensure code analysis stays within GitHub's infrastructure (privacy-first design)","Leverage existing Copilot subscription or free tier for diagram generation"],"best_for":["Developers already using GitHub Copilot in VS Code","Teams with GitHub Copilot licenses who want to maximize tool utilization","Organizations with strict API key management policies preferring integrated authentication"],"limitations":["No alternative LLM provider support — locked to GitHub Copilot only; cannot use Claude, GPT-4, Ollama, or other models","Requires GitHub Copilot to be installed and authenticated; extension cannot function without it","No configurable LLM parameters (temperature, token limits, model version) — Copilot settings are fixed","Rate limiting and token quotas are determined by Copilot API, not configurable by extension","Offline usage is not supported; requires active network connection to GitHub Copilot API","If Copilot authentication expires or is revoked, Swark becomes non-functional"],"requires":["Visual Studio Code with GitHub Copilot extension installed","GitHub Copilot authentication (free tier or paid subscription)","Active internet connection to GitHub Copilot API","GitHub account (for Copilot authentication)"],"input_types":["GitHub Copilot authentication token (inherited from Copilot extension)"],"output_types":["API responses from Copilot (diagram generation instructions)"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-swark-swark__cap_4","uri":"capability://automation.workflow.keybinding.triggered.command.execution","name":"keybinding-triggered command execution","description":"Provides keyboard shortcuts (`cmd+shift+r` on macOS, `ctrl+shift+r` on Windows) that invoke the `Swark: Create Architecture Diagram` command from the command palette. Keybindings are pre-configured and trigger the full analysis-and-generation workflow without requiring menu navigation or command palette typing.","intents":["Quickly generate diagrams with a single keyboard shortcut during development workflow","Reduce friction for repeated diagram generation across multiple folders","Integrate diagram generation into muscle-memory developer workflows"],"best_for":["Developers who frequently generate diagrams and prefer keyboard shortcuts over menu navigation","Teams with standardized keybinding configurations across developer machines"],"limitations":["Keybinding rebinding capability is unknown — unclear if users can customize shortcuts","Keybindings may conflict with other VS Code extensions or user-configured shortcuts","No context-aware keybinding behavior — shortcut always triggers full folder selection dialog regardless of current editor state","No keybinding for other Swark operations (e.g., viewing previous diagrams, clearing output folder)"],"requires":["Visual Studio Code with Swark extension installed","Keybindings not already bound to conflicting commands"],"input_types":["keyboard input (cmd+shift+r or ctrl+shift+r)"],"output_types":["command execution trigger"],"categories":["automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-swark-swark__cap_5","uri":"capability://automation.workflow.timestamped.diagram.output.organization","name":"timestamped diagram output organization","description":"Automatically generates timestamped filenames (`<date>__<time>__diagram.md`) for each diagram and stores them in a `swark-output` folder at workspace root. Each diagram generation also produces a metadata log file containing run timestamp and list of analyzed files. This approach creates an audit trail of diagram generation history without overwriting previous diagrams.","intents":["Track diagram generation history and compare how architecture understanding evolved over time","Maintain multiple diagram versions for different codebase snapshots","Audit which files were analyzed in each diagram generation run"],"best_for":["Teams tracking architectural evolution across code reviews or releases","Projects requiring audit trails of documentation generation","Developers comparing architecture diagrams across different codebase versions"],"limitations":["No automatic cleanup or archival — `swark-output` folder accumulates files indefinitely","No built-in versioning or branching strategy — all diagrams stored in single flat folder","Timestamp format is fixed; no customization of filename patterns","No deduplication — identical diagrams generated at different times create separate files","Metadata log format is undocumented; unclear what information is captured beyond timestamp and file list"],"requires":["Write access to workspace root to create `swark-output` folder","Sufficient disk space for accumulating diagram files over time"],"input_types":["system timestamp","analyzed file list"],"output_types":["timestamped markdown files","metadata log files"],"categories":["automation-workflow","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-swark-swark__cap_6","uri":"capability://data.processing.analysis.optional.test.file.inclusion.for.coverage.visualization","name":"optional test file inclusion for coverage visualization","description":"Allows users to optionally include test files in the analysis input to enable visualization of test coverage relationships within the architecture diagram. Test files are treated as optional input metadata that Copilot can use to infer testing patterns and coverage across architectural components. Mechanism for enabling/disabling test file inclusion is undocumented.","intents":["Visualize how test coverage maps to architectural components","Understand testing patterns and dependencies within the architecture","Identify untested architectural layers or services"],"best_for":["Teams practicing test-driven development who want to visualize test-architecture relationships","QA engineers analyzing test coverage distribution across architecture","Projects with complex testing strategies requiring visualization"],"limitations":["Test file inclusion mechanism is undocumented — unclear how users enable/disable this feature","Copilot's handling of test files is not specified — unclear what coverage visualization actually shows","No test framework detection or standardization — all test files treated generically","Test coverage visualization format within Mermaid diagram is unknown","No metrics or quantitative coverage reporting — only visual relationships inferred by LLM"],"requires":["Test files present in selected folder","Unknown mechanism to enable test file analysis"],"input_types":["test files (all frameworks supported generically)"],"output_types":["test-coverage relationships in Mermaid diagram (format unknown)"],"categories":["data-processing-analysis","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-swark-swark__cap_7","uri":"capability://code.generation.editing.language.agnostic.code.analysis.via.llm.inference","name":"language-agnostic code analysis via llm inference","description":"Supports all programming languages through LLM-based semantic analysis rather than language-specific parsers. Copilot infers architectural structure, components, and relationships from source code without requiring language-specific AST parsing or grammar rules. This approach enables universal language support but sacrifices determinism and precision of syntax-aware analysis.","intents":["Generate architecture diagrams for polyglot codebases mixing multiple languages","Analyze code in languages without dedicated parsing tools","Understand architecture without language-specific tooling setup"],"best_for":["Polyglot teams working with multiple programming languages","Projects using niche or emerging languages without mature tooling","Developers who want universal architecture visualization without language-specific configuration"],"limitations":["LLM inference is non-deterministic — same code may produce different architectural interpretations across runs","No language-specific optimizations — architecture inference quality may vary significantly across languages","No tested language list provided — 'universal' support is claimed but not validated","Framework detection is language-agnostic and may miss framework-specific architectural patterns","No syntax validation — LLM may misinterpret code structure, especially in unfamiliar languages","Performance degrades with complex language-specific idioms that LLM may not understand"],"requires":["Source code files in any programming language","GitHub Copilot (which supports all languages via LLM)"],"input_types":["source code in any programming language"],"output_types":["architecture diagram (language-agnostic Mermaid format)"],"categories":["code-generation-editing","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-swark-swark__cap_8","uri":"capability://automation.workflow.vs.code.command.palette.integration","name":"vs code command palette integration","description":"Registers the `Swark: Create Architecture Diagram` command in VS Code's command palette, making the feature discoverable via `Ctrl+Shift+P` (or `Cmd+Shift+P` on macOS) command palette search. Command palette integration provides discoverability for users unfamiliar with keybindings and enables command execution from any editor state.","intents":["Discover Swark functionality through VS Code's standard command palette interface","Execute diagram generation without memorizing keybindings","Access Swark from any editor context without menu navigation"],"best_for":["New users exploring Swark functionality","Developers who prefer command palette over keybindings","Teams with inconsistent keybinding configurations"],"limitations":["Command palette search requires typing or fuzzy matching — slower than direct keybinding","No command parameters or options — command always triggers full folder selection workflow","No context-aware command suggestions — command appears in palette regardless of editor state"],"requires":["Visual Studio Code with Swark extension installed","Knowledge of command palette access (`Ctrl+Shift+P` or `Cmd+Shift+P`)"],"input_types":["command palette search query"],"output_types":["command execution trigger"],"categories":["automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"vscode-swark-swark__cap_9","uri":"capability://safety.moderation.workspace.scoped.file.system.access.with.privacy.boundaries","name":"workspace-scoped file system access with privacy boundaries","description":"Restricts file system access to the VS Code workspace root and user-selected folders within it. Extension cannot read files outside the workspace, preventing accidental exposure of system files or unrelated code. All file reading is performed within VS Code's sandbox and workspace context, enforcing privacy boundaries at the extension level.","intents":["Ensure code analysis is limited to intended project scope","Prevent accidental exposure of sensitive files outside the project","Maintain privacy by restricting Copilot access to selected code only"],"best_for":["Teams with strict data privacy requirements","Developers working with sensitive codebases who want to control what code is analyzed","Organizations requiring audit trails of which code is sent to external APIs"],"limitations":["No fine-grained file filtering — all files in selected folder are analyzed, no exclusion patterns","No .gitignore or .swarkignore support mentioned — cannot exclude specific file types or patterns","External dependencies and imports outside workspace are not analyzed — incomplete architecture view","No symlink handling documented — unclear if symlinks are followed or blocked","Workspace scope is fixed at VS Code workspace root — no multi-workspace support mentioned"],"requires":["Visual Studio Code workspace configured","Read access to files within workspace"],"input_types":["workspace root path","user-selected folder path"],"output_types":["file list within workspace scope"],"categories":["safety-moderation","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":36,"verified":false,"data_access_risk":"high","permissions":["Visual Studio Code (version not specified, assume recent stable)","GitHub Copilot extension installed and authenticated (free tier now available)","Active network connection to GitHub Copilot API","User-selected folder with readable source code files","Visual Studio Code with Swark extension installed","Readable source code files in selected folder","GitHub Copilot authentication","Visual Studio Code with Swark extension","Write access to workspace root (to create `swark-output` folder)","Optional: Mermaid Markdown Preview extension for in-editor preview"],"failure_modes":["LLM-based inference is non-deterministic — same codebase may produce slightly different diagrams across runs","No control over diagram granularity or abstraction level — Copilot determines what constitutes an 'architectural component'","Requires GitHub Copilot authentication; cannot function offline or with alternative LLM providers","Performance degrades with very large codebases due to token limits in Copilot API (exact limit unknown)","No support for incremental updates — each invocation generates a new diagram from scratch","No recursive analysis of dependencies outside selected folder — external imports/dependencies are not automatically included","No filtering options for file types, sizes, or patterns — all files in folder are analyzed","No batch processing — one folder per invocation; analyzing multiple subsystems requires multiple command executions","File system access is read-only and limited to workspace root; cannot access files outside VS Code workspace","Output format is Mermaid.js only — no support for PlantUML, SVG, PNG, or other diagram formats","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.44,"quality":0.3,"ecosystem":0.18,"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.803Z","last_scraped_at":"2026-05-03T15:20:33.198Z","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=swark","compare_url":"https://unfragile.ai/compare?artifact=swark"}},"signature":"tMlMCpp76yocZzLfmEcUMom4+HoC8nhgi+dEJOw/h0jb5rhi22oJO4c9NuXDJMSNT4749TvYo1tVQXD3UP8LAQ==","signedAt":"2026-06-22T03:55:45.376Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/swark","artifact":"https://unfragile.ai/swark","verify":"https://unfragile.ai/api/v1/verify?slug=swark","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"}}