Jumio
v1.0.2Jumio integration. Manage data, records, and automate workflows. Use when the user wants to interact with Jumio data.
⭐ 0· 97·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The README/instructions describe interacting with Jumio via the Membrane platform and CLI. Required actions (connecting, listing actions, proxying requests) align with a Jumio integration; there are no unrelated credentials, binaries, or config paths requested.
Instruction Scope
SKILL.md limits runtime actions to installing/using the @membranehq/cli, logging into Membrane, creating a Jumio connection, listing/running actions, and proxying requests to the Jumio API. It does not instruct reading unrelated files, harvesting environment variables, or exfiltrating data to unexpected endpoints.
Install Mechanism
There is no embedded install spec (skill is instruction-only) but the docs instruct users to run `npm install -g @membranehq/cli`. Installing a global npm package is a reasonable step for a CLI-based integration but carries the usual npm risks (verify package name/version and publisher).
Credentials
The skill requests no environment variables or local credentials and explicitly advises against asking users for API keys. Authentication is delegated to Membrane, which is proportionate for a connector-based integration.
Persistence & Privilege
always is false and the skill is instruction-only with no install artifacts. It does not request permanent presence or modify other skills or system-wide settings.
Assessment
This skill is coherent: it delegates auth and API calls to the Membrane platform and tells you to install the Membrane CLI. Before installing or using it, verify you trust the Membrane service and the @membranehq/cli package (check the publisher, package version, and release source). Be aware that granting Membrane connector access gives that service the ability to act on Jumio data for your account—review connector permissions and Membrane's privacy/security docs. If you prefer not to rely on a third-party proxy, consider implementing a direct Jumio integration that you control. Finally, when installing any global npm package, prefer auditing the package and avoid running installs in sensitive production hosts without review.Like a lobster shell, security has layers — review code before you run it.
latestvk9770r2fnhez0gnpzsx0zx9zsx8424r9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.