Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Flexera
v1.0.0Flexera integration. Manage data, records, and automate workflows. Use when the user wants to interact with Flexera data.
⭐ 0· 49·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The SKILL.md describes a Flexera integration implemented by calling the Membrane CLI and proxying requests to Flexera — this matches the skill name/description. However the registry metadata declares no required binaries or credentials while the instructions explicitly require npm (to install @membranehq/cli), network access, and a Membrane account (browser-based login). The missing runtime requirements in metadata are an inconsistency.
Instruction Scope
The instructions stay within the stated purpose: they show how to install the Membrane CLI, authenticate, create a Flexera connection, run actions, and proxy arbitrary Flexera API calls through Membrane. There are no instructions to read unrelated local files or exfiltrate data to unexpected endpoints. The ability to proxy arbitrary API requests via 'membrane request' is powerful but expected for this integration.
Install Mechanism
This is an instruction-only skill (no install spec), but it instructs users to run 'npm install -g @membranehq/cli' and uses 'npx' in examples. Installing a global npm package (or invoking npx) introduces a supply‑chain risk and writes code to disk — a moderate risk that is normal for CLI-based integrations but worth calling out. The skill did not include an install spec in the registry metadata to make this explicit.
Credentials
The skill declares no required env vars or primary credential in metadata, and the SKILL.md likewise relies on Membrane to manage authentication rather than asking for explicit API keys. That is proportionate. However the SKILL.md does require a Membrane account and an interactive browser login (or headless flow), and the metadata does not document where credentials/tokens will be stored (the Membrane CLI will keep local tokens/config).
Persistence & Privilege
always is false and model invocation is enabled (the platform default). The skill does not request persistent system‑wide privileges or claim to modify other skills. Installing/using the Membrane CLI will create local state (auth tokens/config) but that is normal for a CLI tool and scoped to the local user profile.
What to consider before installing
What to consider before installing:
- The skill requires you to install and run the @membranehq/cli npm package (global install or npx) — verify the package and publisher (https://getmembrane.com, repo link in SKILL.md) before installing. Installing global npm packages carries supply‑chain risk.
- The SKILL.md omitted runtime requirements from the registry metadata: you need npm/node, network access, and a Membrane account (browser login or headless flow). Expect the CLI to store auth tokens/config locally.
- The Membrane CLI can proxy arbitrary requests to Flexera using your credentials — only use it if you trust the Membrane service and the connector configuration. Prefer reviewing the connector/action schemas and limiting the connection's permissions where possible.
- If you want lower risk: run the CLI in an isolated environment/container, pin the exact CLI version (avoid unconstrained npx --latest in production), inspect the @membranehq/cli package source or its published artifacts, and confirm the repository/homepage match the publisher identity.
- If you need more assurance, ask the skill publisher for a signed install spec or explicit metadata listing required binaries and where the CLI stores auth tokens; that would raise confidence that the skill's metadata and runtime behavior are consistent.Like a lobster shell, security has layers — review code before you run it.
latestvk978fr4kcg7eq5bb9t8cy60xgh848ecw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
