Plate Recognizer

v1.0.2

Plate Recognizer integration. Manage Vehicles, Cameras, Regions, Users, Alerts. Use when the user wants to interact with Plate Recognizer data.

0· 121·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name/description claim a Plate Recognizer integration and the instructions consistently show how to access Plate Recognizer via Membrane. Required capabilities (network access, Membrane account/CLI) match the stated purpose and no unrelated services or credentials are requested.
Instruction Scope
SKILL.md only instructs use of the Membrane CLI (search/connect/run actions/proxy requests) and browser-based auth flow; it does not ask the agent to read unrelated files, access other credentials, or exfiltrate data to unexpected endpoints.
Install Mechanism
There is no formal install spec in the registry (instruction-only), but the SKILL.md tells users to run 'npm install -g @membranehq/cli' or use npx. Global npm installs and npx network fetches are common but carry standard supply-chain risk; this is proportionate to providing a CLI but worth verifying the package source before installing.
Credentials
The skill declares no required env vars or credentials and explicitly advises letting Membrane handle auth (no local API keys). That is proportional: Membrane manages Plate Recognizer credentials server-side via the browser login flow described.
Persistence & Privilege
The skill is not force-enabled (always:false) and does not request persistent system-wide changes or access to other skills' configs. Autonomous invocation is allowed by default but not combined with other concerning privileges here.
Assessment
This skill appears to do what it says: it expects you to use the Membrane CLI to connect to Plate Recognizer and does not ask for unrelated credentials. Before installing or running commands: 1) verify the Membrane CLI package (@membranehq/cli) on the npm registry and prefer using 'npx' or a pinned version rather than an unrestricted global '-g' install if you are cautious; 2) confirm you trust the skill publisher (source is 'unknown' in the registry metadata) and the homepage (getmembrane.com); 3) be mindful that running the described CLI commands will open browser-based authentication flows and may transmit data via Membrane's servers (intended behavior for this integration). If you need higher assurance, request the skill owner/source repo or a signed release for the CLI they recommend.

Like a lobster shell, security has layers — review code before you run it.

latestvk97b4rp2v22tejg7y5rwndxwcn843a7e

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments