Airbyte
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This appears to be a coherent Membrane-based Airbyte integration, but it can use OAuth-backed account access to run broad Airbyte management and API commands.
Install this skill only if you are comfortable letting an agent use Membrane to access your Airbyte tenant. Use least-privileged credentials, confirm any create/update/proxy action before it runs, and consider pinning or verifying the Membrane CLI package before global installation.
Static analysis
No static analysis findings were reported for this release.
VirusTotal
VirusTotal findings are pending for this skill version.
Risk analysis
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If connected to a real Airbyte tenant, the agent could make account or pipeline changes when instructed to run those actions.
The skill documents commands that can create or update Airbyte resources and also provides a direct API proxy fallback. This is consistent with an Airbyte management integration, but it is broad enough to affect production data pipelines.
Popular actions ... Create Connection ... Create Destination ... Create Source ... Create Workspace ... Update Connection ... Update Destination ... Update Source ... Update Workspace ... Running actions ... membrane action run <actionId> ... Proxy requests ... send requests directly to the Airbyte API through Membrane's proxy
Require explicit confirmation for create, update, or proxy requests; review action inputs before execution; and use a least-privileged Airbyte/Membrane connection where possible.
The agent may continue to have authorized access through Membrane until the user revokes or changes that connection.
The integration relies on delegated authentication and automatic credential refresh through Membrane. This is expected for an Airbyte API integration, but it grants ongoing access to the connected account.
Membrane handles authentication and credentials refresh automatically ... membrane login --tenant --clientName=<agentType> ... The user completes authentication in the browser.
Authenticate with the minimum required Airbyte permissions, review Membrane connection scopes, and revoke the connection when it is no longer needed.
Future installs could receive a different CLI version than the one available when the skill was published.
The setup uses a globally installed npm package with the moving latest tag. This is normal for CLI setup, but it means the exact installed code is not pinned in the skill artifact.
npm install -g @membranehq/cli@latest
Install the CLI from the official source, consider pinning a known-good version, and keep the CLI updated intentionally.
Airbyte request metadata, responses, and authenticated API operations may pass through the Membrane service.
Airbyte API requests and authentication are routed through Membrane's proxy. This provider boundary is disclosed and purpose-aligned, but users should understand that Membrane is part of the data and credential path.
send requests directly to the Airbyte API through Membrane's proxy ... injects the correct authentication headers
Review Membrane's data-handling terms and avoid sending unnecessary sensitive Airbyte data through proxy requests.