Imperva
v1.0.0Imperva integration. Manage data, records, and automate workflows. Use when the user wants to interact with Imperva data.
⭐ 0· 53·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
Name/description say 'Imperva integration' and the SKILL.md explains how to use the Membrane CLI to connect to Imperva, list/run actions, and proxy API requests. Required network access and a Membrane account are coherent with this purpose.
Instruction Scope
Runtime instructions are limited to installing/using the Membrane CLI, performing browser-based login, creating a connector, listing/running actions, and proxying requests to Imperva. The instructions do not ask to read unrelated files, exfiltrate environment variables, or modify other skills/configs.
Install Mechanism
SKILL.md suggests installing @membranehq/cli via npm (global or npx). That is a public npm installation (moderate risk if you do it), but the skill itself does not auto-install or fetch arbitrary URLs. Verify the npm package and publisher before installing; using npx avoids a persistent global install.
Credentials
The skill declares no required environment variables or credentials and relies on Membrane to manage Imperva authentication server-side. This is proportionate to its functionality, but it does imply trusting Membrane with access to Imperva on your behalf.
Persistence & Privilege
Skill is instruction-only, has no install spec, and is not marked always:true. It does not request persistent presence or modifications to other skills or system-wide settings.
Assessment
This skill is internally consistent: it instructs you to use the Membrane CLI to connect to Imperva and does not request unrelated secrets or elevated privileges. Before installing/running the CLI: (1) verify the @membranehq/cli npm package and its publisher (check GitHub, downloads, and reviews); (2) prefer npx for one-off commands to avoid a global install; (3) understand that Membrane will handle Imperva credentials server-side—ensure you trust that service and review its privacy/security docs; (4) run installs in a controlled environment (e.g., isolated container or dev machine) if you are cautious. If you want deeper assurance, provide the Membrane package checksum or repository link for independent review.Like a lobster shell, security has layers — review code before you run it.
latestvk979e0zv52j92hsmhdyw0pdt8d84e2ky
License
MIT-0
Free to use, modify, and redistribute. No attribution required.