Ravelin
Security checks across static analysis, malware telemetry, and agentic risk
Overview
This is a coherent Ravelin/Membrane integration, but it needs review because it can use a logged-in Membrane connection to make arbitrary Ravelin API requests, including changes and deletes.
Before installing, make sure you trust Membrane and the npm CLI package, connect only a least-privilege Ravelin account, and require explicit confirmation for any action that creates, updates, deletes, labels, decides, or otherwise changes Ravelin data.
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.
An agent using this connection could change or delete Ravelin records, labels, decisions, chargeback-related data, or other business data if a request is mistaken or overly broad.
This documents a raw API escape hatch with mutating and deleting methods for a fraud/business-data system, but the artifacts do not define approval requirements, endpoint limits, or rollback guidance.
When the available actions don't cover your use case, you can send requests directly to the Ravelin API through Membrane's proxy... `membrane request CONNECTION_ID /path/to/endpoint` ... HTTP method (GET, POST, PUT, PATCH, DELETE).
Require explicit user confirmation before POST, PUT, PATCH, DELETE, or proxy requests; prefer discovered scoped actions; and restrict the connection to the least Ravelin permissions needed.
The skill can act with the privileges of the connected Membrane/Ravelin account.
The skill requires delegated Membrane/Ravelin account authentication and automatic credential refresh, which is expected for the integration but gives the agent access under that account's permissions.
Requires network access and a valid Membrane account... `membrane login --tenant --clientName=<agentType>` ... Membrane handles authentication and credentials refresh automatically.
Use a dedicated least-privilege account or connection, review granted scopes, and revoke the connection when it is no longer needed.
Installing the CLI runs and trusts external package code in the user's environment.
The skill instructs a global npm installation of the latest Membrane CLI. This is purpose-aligned and user-directed, but it relies on an external moving package version.
npm install -g @membranehq/cli@latest
Install from a trusted environment, consider pinning a reviewed CLI version, and follow the Membrane package/repository provenance before use.
Ravelin request data and authentication handling pass through Membrane rather than going directly only between the user and Ravelin.
Ravelin API requests and authentication are mediated by the Membrane gateway/proxy, which is expected for this skill but is an important external data and credential boundary.
send requests directly to the Ravelin API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers
Review Membrane's privacy/security posture and only send the Ravelin data needed for the task.