{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"remote-ssh","slug":"remote-ssh","name":"Remote - SSH","type":"extension","url":"https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-ssh","page_url":"https://unfragile.ai/remote-ssh","categories":["browser-extensions"],"tags":[],"pricing":{"model":"free","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"remote-ssh__cap_0","uri":"capability://tool.use.integration.ssh.based.remote.machine.connection.and.authentication","name":"ssh-based remote machine connection and authentication","description":"Establishes persistent SSH connections to remote hosts using OpenSSH-compatible clients with support for both password and key-based authentication. The extension manages SSH session lifecycle, credential handling, and connection state within VS Code's process model, enabling seamless switching between local and remote development contexts without requiring source code to exist locally.","intents":["Connect to a development server and work on code as if it were local","Authenticate to a remote machine using SSH keys or passwords","Maintain persistent SSH sessions across multiple VS Code operations","Switch between multiple remote hosts without restarting VS Code"],"best_for":["Teams developing on shared servers or cloud instances","Developers working with embedded systems or ARM-based hardware","Organizations with centralized development infrastructure","Solo developers needing to offload compute to remote machines"],"limitations":["Requires OpenSSH-compatible SSH client on local machine — proprietary SSH clients may not work","SSH authentication limited to password or key-based methods — no GSSAPI or certificate-based auth documented","Connection quality and latency depend entirely on network — no local caching or offline fallback","Remote machine must have SSH server running and accessible — no automatic server provisioning"],"requires":["OpenSSH-compatible SSH client installed locally","VS Code 1.41+ or VS Code Insiders","SSH server running on remote host (Linux, macOS, or Windows 10/Server 2016+)","Network connectivity to remote host with SSH port (default 22) accessible"],"input_types":["SSH connection string (user@host or user@domain@host)","SSH private key file (PEM format)","SSH password (plaintext or prompted)"],"output_types":["Authenticated SSH session","Remote machine context within VS Code"],"categories":["tool-use-integration","infrastructure-connectivity"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"remote-ssh__cap_1","uri":"capability://tool.use.integration.remote.filesystem.browsing.and.file.editing.with.live.synchronization","name":"remote filesystem browsing and file editing with live synchronization","description":"Provides full read-write access to remote machine filesystems through VS Code's file explorer, enabling users to open, create, edit, and delete files on remote hosts as if they were local. The extension uses SSH's SFTP protocol layer to transfer file contents bidirectionally, with real-time change detection and conflict resolution, allowing simultaneous editing of remote files without requiring local copies.","intents":["Open a folder on a remote server and browse its entire directory structure","Edit files on a remote machine with full VS Code editor features (syntax highlighting, IntelliSense)","Create new files and directories on the remote filesystem","Delete or rename files on the remote machine without using terminal commands"],"best_for":["Developers working with large codebases that shouldn't be cloned locally","Teams sharing a single development server with limited storage","Embedded systems developers working with ARM boards or IoT devices","Researchers or data scientists working with remote compute clusters"],"limitations":["File transfer speed limited by SSH bandwidth — large binary files or media may transfer slowly","No local caching of remote files — every file access requires SSH round-trip","Filesystem operations are sequential — bulk operations (copy, move) on large directories may be slow","Some VS Code features may degrade with high-latency connections (autocomplete, diagnostics)","File permissions and ownership preserved but may not match local user's expectations on Windows"],"requires":["SSH access to remote machine with read/write permissions on target directories","Remote machine with SFTP server support (included in OpenSSH)","Sufficient disk space on remote machine for edited files","Network bandwidth adequate for file transfer (minimum 1 Mbps recommended)"],"input_types":["Remote filesystem path","File contents (text or binary)","File metadata (permissions, timestamps)"],"output_types":["File contents displayed in VS Code editor","File tree structure in sidebar","Change notifications and sync status"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"remote-ssh__cap_10","uri":"capability://tool.use.integration.multi.machine.workspace.context.switching.and.connection.management","name":"multi-machine workspace context switching and connection management","description":"Manages multiple simultaneous or sequential SSH connections to different remote machines, allowing developers to switch between remote development contexts without closing and reopening VS Code. The extension maintains a list of recently connected hosts and provides quick-access commands to reconnect or switch to different machines. Each connection maintains its own workspace context, extensions, and terminal sessions.","intents":["I want to quickly switch between working on different remote servers without closing VS Code","I need to maintain separate workspace contexts for multiple remote machines","I want to access a list of frequently used remote hosts for quick connection"],"best_for":["DevOps engineers managing multiple servers","Developers working across multiple environments (dev, staging, production)","Teams with distributed infrastructure"],"limitations":["Only one remote connection can be active at a time — cannot have multiple remote folders open simultaneously","Connection history is stored locally — switching machines requires re-establishing SSH connection each time","Workspace state is not preserved when switching machines — open files and editor state are lost","Extensions must be individually installed on each remote machine — switching machines may show different available extensions"],"requires":["SSH access to multiple remote machines","SSH configuration for each remote host"],"input_types":["Remote host address","Connection history selection"],"output_types":["Active SSH connection","Remote workspace context","Connection status"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"remote-ssh__cap_11","uri":"capability://safety.moderation.ssh.key.based.authentication.with.fallback.password.support","name":"ssh key-based authentication with fallback password support","description":"Supports SSH key-based authentication as the primary authentication method, with fallback to password-based authentication if keys are not available. The extension uses the local SSH client's key agent (ssh-agent) to provide keys for authentication, eliminating the need to enter passwords for each connection. If key-based authentication fails, the extension prompts for a password and uses password-based authentication as a fallback.","intents":["I want to connect to remote machines using SSH keys without entering passwords","I need to use SSH key agent forwarding to access remote machines with different key pairs","I want a fallback authentication method if SSH keys are not available"],"best_for":["Security-conscious developers using SSH key-based authentication","Teams with SSH key infrastructure and policies","Engineers accessing machines without password authentication enabled"],"limitations":["SSH key setup is manual — extension does not generate or manage SSH keys","Key agent must be running locally — ssh-agent must be started and keys added before VS Code connection","Passphrase-protected keys require entering passphrase on first connection — subsequent connections use cached passphrase","Password-based authentication is discouraged but supported — security policies may prohibit password authentication","Key agent forwarding is not supported — cannot use local keys to authenticate to machines accessed through jump hosts"],"requires":["SSH key pair generated locally (id_rsa, id_ed25519, etc.)","Public key installed on remote machine (~/.ssh/authorized_keys)","SSH agent running locally with keys added (ssh-add)"],"input_types":["SSH key file path","Passphrase for encrypted keys","Password for fallback authentication"],"output_types":["Authenticated SSH connection","Authentication status"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"remote-ssh__cap_2","uri":"capability://tool.use.integration.remote.terminal.shell.access.with.environment.inheritance","name":"remote terminal shell access with environment inheritance","description":"Provides integrated terminal access to the remote machine's shell environment, executing commands directly on the remote host with full access to the remote user's PATH, environment variables, and shell configuration. The extension spawns a remote shell session over SSH and pipes stdin/stdout/stderr through the VS Code terminal UI, inheriting the remote user's login environment without requiring manual shell initialization.","intents":["Run build commands, tests, or deployment scripts on the remote machine","Execute git commands against repositories stored on the remote machine","Install dependencies or packages on the remote machine using package managers","Debug issues by inspecting logs or running diagnostics on the remote system"],"best_for":["Developers building and testing code on the same machine where it will run","DevOps engineers managing remote servers and infrastructure","Teams using containerized development environments on remote machines","Developers working with language-specific tools that must run on the target platform"],"limitations":["Terminal latency depends on SSH connection quality — high-latency connections make interactive commands sluggish","No local terminal history or command caching — each command requires SSH round-trip","Shell features like job control or terminal multiplexing may behave differently than native terminals","Some interactive tools (vim, less, top) may have rendering issues over SSH due to terminal emulation differences","Environment variables set in local shell do not carry over to remote terminal"],"requires":["SSH access to remote machine","Shell interpreter on remote machine (bash, zsh, sh, etc.)","Terminal emulation support on remote machine (standard on Linux/macOS/Windows)","Network connectivity with acceptable latency for interactive use (< 500ms recommended)"],"input_types":["Shell commands (text)","Standard input (stdin) from user","Environment variables from remote shell"],"output_types":["Command output (stdout)","Error messages (stderr)","Exit codes","Terminal UI rendering"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"remote-ssh__cap_3","uri":"capability://tool.use.integration.port.forwarding.from.local.machine.to.remote.services","name":"port forwarding from local machine to remote services","description":"Establishes SSH port forwarding tunnels that map local ports to services running on the remote machine, enabling developers to access remote web servers, databases, or APIs as if they were running locally. The extension manages the SSH tunnel lifecycle and exposes forwarded ports through VS Code's port forwarding UI, with automatic detection of commonly-used ports and one-click forwarding setup.","intents":["Access a web application running on the remote machine from a local browser","Connect a local database client to a database server running on the remote machine","Test API endpoints running on the remote machine using local tools","Debug remote services by connecting local debugging tools to remote processes"],"best_for":["Full-stack developers testing web applications on remote servers","Teams running shared development databases on a central server","Developers working with microservices deployed on remote machines","QA engineers testing applications on production-like remote environments"],"limitations":["Port forwarding requires SSH tunnel to remain active — disconnecting SSH closes all forwarded ports","Local ports must be available and not already in use — conflicts with other services require manual port remapping","Forwarded ports are only accessible from the local machine — cannot be shared with other team members without additional configuration","Performance depends on SSH bandwidth — high-traffic services may saturate the SSH connection","No built-in load balancing or failover for multiple remote instances"],"requires":["SSH access to remote machine","Service running on remote machine listening on a specific port","Local port available for forwarding (not already in use)","Network connectivity between local and remote machines"],"input_types":["Remote port number (integer)","Local port number (integer)","Service address on remote machine (localhost or IP)"],"output_types":["Local port mapping","Forwarding status (active/inactive)","Connection logs"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"remote-ssh__cap_4","uri":"capability://tool.use.integration.remote.vs.code.extension.installation.and.execution","name":"remote vs code extension installation and execution","description":"Enables installation and execution of VS Code extensions directly on the remote machine's extension host, allowing extensions to access remote filesystem, processes, and environment without requiring code to be copied locally. The extension manager detects which extensions are compatible with the remote platform (x86_64, ARMv7l, ARMv8l) and handles installation of platform-specific native binaries, with fallback to local execution for extensions that don't support remote operation.","intents":["Use language-specific extensions (Python, Go, Rust) that need to run on the target platform","Install linters, formatters, and debuggers that must execute on the remote machine","Enable IntelliSense and code completion for languages installed only on the remote machine","Run remote-specific tools (Docker, Kubernetes) that require local filesystem access on the remote machine"],"best_for":["Developers using language-specific extensions that require platform-specific binaries","Teams developing for ARM-based systems (Raspberry Pi, embedded Linux)","Developers working with compiled languages (C++, Go, Rust) that need native toolchains","Teams using container-based development where tools are installed in the container, not locally"],"limitations":["Some extensions with native code dependencies may fail on ARM platforms (ARMv7l/ARMv8l) if they don't provide ARM binaries","Extension compatibility depends on remote platform — x86_64 extensions may not work on ARM without recompilation","Remote extension installation requires sufficient disk space on remote machine — no automatic cleanup of unused extensions","Extensions that depend on local system resources (GPU, specific hardware) may not function on remote machines","No automatic synchronization of extension settings between local and remote — settings must be manually configured per machine"],"requires":["SSH access to remote machine","Remote machine with supported architecture (x86_64, ARMv7l, ARMv8l)","Sufficient disk space on remote machine for extension installation (typically 50-500 MB per extension)","Remote machine with glibc-based Linux, macOS 10.14+, or Windows 10/Server 2016+ with OpenSSH","Extension must support remote execution (not all extensions are compatible)"],"input_types":["Extension ID (from VS Code marketplace)","Extension manifest (package.json)","Platform architecture identifier"],"output_types":["Installed extension on remote machine","Extension status (enabled/disabled/incompatible)","Extension-provided features (IntelliSense, debugging, etc.)"],"categories":["tool-use-integration","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"remote-ssh__cap_5","uri":"capability://tool.use.integration.multi.platform.ssh.host.support.with.architecture.detection","name":"multi-platform ssh host support with architecture detection","description":"Supports SSH connections to diverse remote platforms (Linux x86_64/ARMv7l/ARMv8l, macOS 10.14+, Windows 10/Server 2016+) with automatic detection of remote architecture and OS, enabling appropriate binary selection for extensions and tools. The extension queries the remote system's uname output to determine platform capabilities and adjusts feature availability accordingly, with graceful degradation for unsupported platforms.","intents":["Connect to a Linux development server and use platform-specific tools","Develop on a Raspberry Pi or other ARM-based embedded system","Work on a macOS machine remotely with full IDE support","Develop on Windows Server or Windows 10 with OpenSSH enabled"],"best_for":["Embedded systems developers working with ARM hardware","Teams with heterogeneous infrastructure (mix of Linux, macOS, Windows servers)","Organizations running development environments on cloud instances with various OS options","Developers needing to test code on multiple platforms without local VMs"],"limitations":["ARM platform support (ARMv7l/ARMv8l) limited to Debian 8+, Ubuntu 16.04+, or Raspbian Stretch — other ARM distros may not work","Windows support requires Windows 10 1803+ or Server 2016+ with official OpenSSH — older Windows versions not supported","macOS support requires 10.14+ with Remote Login enabled — older macOS versions not supported","Some extensions may not provide ARM binaries — native code extensions may fail on ARM platforms","Performance on ARM platforms may be significantly slower than x86_64 due to hardware limitations"],"requires":["SSH server running on remote machine (OpenSSH or compatible)","Supported OS on remote machine (Linux with glibc, macOS 10.14+, or Windows 10/Server 2016+)","Minimum 1 GB RAM on remote machine (2 GB recommended)","Network connectivity to remote machine with SSH port accessible"],"input_types":["SSH connection string","Remote machine OS and architecture (detected automatically)"],"output_types":["Platform detection results","Supported features list","Architecture-specific binary selection"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"remote-ssh__cap_6","uri":"capability://tool.use.integration.vs.code.command.palette.integration.for.remote.operations","name":"vs code command palette integration for remote operations","description":"Exposes all remote SSH operations through VS Code's command palette with `Remote-SSH:` prefixed commands, providing discoverable access to connection management, folder opening, and configuration without requiring users to learn SSH syntax or terminal commands. Commands are context-aware, showing available remote hosts and suggesting next steps based on current connection state.","intents":["Quickly connect to a frequently-used remote machine without typing SSH commands","Open a folder on a remote machine through the standard VS Code file dialog","View and manage list of saved SSH host configurations","Disconnect from a remote machine and return to local development"],"best_for":["Non-expert users unfamiliar with SSH command-line syntax","Teams standardizing on VS Code as the primary IDE","Developers who prefer GUI-based workflows over terminal commands","Organizations with frequent context switching between local and remote development"],"limitations":["Command palette discovery requires knowing to search for 'Remote-SSH' — not obvious to new users","Advanced SSH options (custom ports, identity files, proxy commands) may not be exposed in command palette — requires manual SSH config file editing","Command palette is modal and interrupts workflow — cannot be accessed while typing in editor","No keyboard shortcuts pre-configured for common operations — users must remember command names or search each time"],"requires":["VS Code 1.41+ or VS Code Insiders","Remote - SSH extension installed","Knowledge of remote machine hostname or IP address"],"input_types":["Command name (text search)","SSH host identifier (user@host)","Folder path on remote machine"],"output_types":["Command execution results","Connection status","File dialog for folder selection"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"remote-ssh__cap_7","uri":"capability://tool.use.integration.remote.environment.variable.and.shell.configuration.management","name":"remote environment variable and shell configuration management","description":"Manages environment variables and shell configuration on the remote machine to ensure that VS Code extensions and terminal sessions have access to the correct runtime environment. The extension sources shell configuration files (.bashrc, .zshrc, etc.) on the remote machine and applies environment variables to extension processes and terminal sessions, enabling language-specific tools (Python interpreters, Node.js, Go toolchain) to be discovered and used correctly.","intents":["I want language servers and linters to use the correct interpreter versions installed on the remote machine","I need environment variables set in my remote shell to be available to VS Code extensions","I want to use Python virtual environments or Node.js version managers on the remote machine"],"best_for":["Developers using multiple language runtimes on remote machines","Teams with standardized development environments configured via shell scripts","Engineers using version managers (nvm, pyenv, rbenv) on remote servers"],"limitations":["Shell configuration must be manually set up on remote machine — no automatic environment provisioning","Environment variable inheritance is not guaranteed — some shell configurations may not be sourced correctly","Version managers (nvm, pyenv) require additional setup on remote machine — not automatically detected","Environment variables set in VS Code settings do not automatically propagate to remote machine","Shell configuration changes require reconnecting to remote host to take effect"],"requires":["Active SSH connection to remote host","Shell configuration files on remote machine (.bashrc, .zshrc, etc.)","Runtimes and tools installed on remote machine (Python, Node.js, Go, etc.)"],"input_types":["Shell configuration files","Environment variable definitions"],"output_types":["Environment variables available to extensions","Terminal environment configuration","Runtime discovery results"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"remote-ssh__cap_8","uri":"capability://tool.use.integration.remote.workspace.settings.and.extension.configuration.synchronization","name":"remote workspace settings and extension configuration synchronization","description":"Synchronizes VS Code workspace settings and extension configurations between local and remote contexts, allowing developers to maintain consistent editor behavior and extension settings across local and remote development. Settings can be configured to apply only locally, only remotely, or to both contexts, enabling per-machine customization while maintaining a shared configuration baseline. The extension stores remote-specific settings in the remote VS Code Server instance.","intents":["I want to use the same editor settings (formatting, indentation, theme) on both local and remote machines","I need to configure extensions differently on remote machines (e.g., different Python interpreter path)","I want to maintain workspace-specific settings that apply only when working on a remote server"],"best_for":["Teams with standardized development environments across local and remote machines","Developers switching between local and remote development","Engineers maintaining multiple remote development servers with different configurations"],"limitations":["Settings synchronization is one-way from local to remote — remote settings do not sync back to local machine","Some settings may not be applicable to remote context — UI-only settings are ignored on remote","Settings changes require reconnecting to remote host to take full effect","No conflict resolution if same setting is configured differently locally and remotely — remote setting takes precedence"],"requires":["Active SSH connection to remote host","VS Code settings file (settings.json) configured locally"],"input_types":["VS Code settings (JSON format)","Extension configuration"],"output_types":["Remote VS Code Server configuration","Extension behavior on remote machine"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"remote-ssh__cap_9","uri":"capability://automation.workflow.automatic.vs.code.server.provisioning.and.updates.on.remote.machine","name":"automatic vs code server provisioning and updates on remote machine","description":"Automatically downloads, installs, and updates the VS Code Server component on the remote machine when establishing an SSH connection, eliminating manual server setup. The extension detects the remote machine's architecture and OS, downloads the appropriate VS Code Server binary, and installs it in a hidden directory on the remote machine. Updates are handled automatically when the local VS Code version changes, ensuring version compatibility between local and remote components.","intents":["I want to connect to a remote machine without manually installing VS Code Server","I need VS Code Server to be automatically updated when I update my local VS Code","I want to work on multiple remote machines with different architectures without manual setup"],"best_for":["Developers who want zero-configuration remote development setup","Teams managing multiple remote development servers","Engineers working on machines with limited administrative access"],"limitations":["Automatic installation requires internet access from remote machine to download VS Code Server binary","Installation can take 30-60 seconds on first connection, blocking editor access during installation","Updates are automatic and cannot be deferred — version mismatches between local and remote can cause compatibility issues if updates fail","Installation directory is hidden (~/.vscode-server) and cannot be customized","Offline installation is not supported — remote machine must have internet access to download server binary"],"requires":["Active SSH connection to remote host","Internet access from remote machine to download VS Code Server binary","Sufficient disk space on remote machine (~500MB for VS Code Server installation)","Supported remote OS (Linux, Windows, macOS)"],"input_types":["Remote machine architecture detection"],"output_types":["Installed VS Code Server on remote machine","Server process running on remote machine","Connection status indicator"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"remote-ssh__headline","uri":"capability://tool.use.integration.remote.development.extension.for.visual.studio.code","name":"remote development extension for visual studio code","description":"A powerful extension that enables developers to seamlessly connect to and work on remote machines over SSH, providing full VS Code functionality including terminal access and extension support.","intents":["best remote development extension","remote SSH for Visual Studio Code","how to develop on remote servers with VS Code","top tools for remote coding","VS Code extensions for SSH access"],"best_for":["developers needing remote access","teams collaborating across locations"],"limitations":["requires SSH access","cannot access local files directly"],"requires":["OpenSSH compatible SSH client"],"input_types":[],"output_types":[],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":57,"verified":false,"data_access_risk":"high","permissions":["OpenSSH-compatible SSH client installed locally","VS Code 1.41+ or VS Code Insiders","SSH server running on remote host (Linux, macOS, or Windows 10/Server 2016+)","Network connectivity to remote host with SSH port (default 22) accessible","SSH access to remote machine with read/write permissions on target directories","Remote machine with SFTP server support (included in OpenSSH)","Sufficient disk space on remote machine for edited files","Network bandwidth adequate for file transfer (minimum 1 Mbps recommended)","SSH access to multiple remote machines","SSH configuration for each remote host"],"failure_modes":["Requires OpenSSH-compatible SSH client on local machine — proprietary SSH clients may not work","SSH authentication limited to password or key-based methods — no GSSAPI or certificate-based auth documented","Connection quality and latency depend entirely on network — no local caching or offline fallback","Remote machine must have SSH server running and accessible — no automatic server provisioning","File transfer speed limited by SSH bandwidth — large binary files or media may transfer slowly","No local caching of remote files — every file access requires SSH round-trip","Filesystem operations are sequential — bulk operations (copy, move) on large directories may be slow","Some VS Code features may degrade with high-latency connections (autocomplete, diagnostics)","File permissions and ownership preserved but may not match local user's expectations on Windows","Only one remote connection can be active at a time — cannot have multiple remote folders open simultaneously","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.7,"quality":0.9,"ecosystem":0.15000000000000002,"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:25.061Z","last_scraped_at":null,"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=remote-ssh","compare_url":"https://unfragile.ai/compare?artifact=remote-ssh"}},"signature":"lzaNvtBM2Aqe5S2waysPf1/oIxw7QfcyteFY4ZAtKQ4/wcE7S4cg/SxZJ3qmQTZCn11pWDAHFXRApmThBmCoAQ==","signedAt":"2026-06-21T12:51:22.631Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/remote-ssh","artifact":"https://unfragile.ai/remote-ssh","verify":"https://unfragile.ai/api/v1/verify?slug=remote-ssh","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"}}