vexa@0.1.3
CAUTION· static onlyPublisher claims: "Send bots to Zoom, Google Meet, and Microsoft Teams meetings. Get live transcripts, recordings, and reports. Works with Vexa Cloud or your own self-hosted in..." Observed in sandbox: static analysis only — behavior not yet observed.
Coverage
Static only; nothing was run yet.The label rests on the code, the instruction files and the publisher. The honeypot run replaces this verdict when it completes.
Is [email protected] safe to install?
KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-19 and scored it 60/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Sends the whole process environment out. Summary: static analysis only — behavior not yet observed.
Behavior trace
Queued for honeypot run · static analysis onlyThis version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.
Static findings
const epEnvFile = path.join(SKILL_SECRETS_DIR, `vexa-${name}.env`);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.endpointFiles.push(path.join(SKILL_SECRETS_DIR, `vexa-${epConfig.active}.env`));Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* Priority: VEXA_BASE_URL env > endpoints config > default prod URL.Fix: Never read or enumerate credential locations; accept a documented environment variable instead.* 1) Capture API key and optionally persist it in skills/vexa/secrets/vexa.env (chmod 600)Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.envFile: hasEpEnv ? `vexa-${name}.env` : "vexa.env (fallback)"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…al.env`, etc. When switching endpoints with `env:use`, the matching `vexa-<name>.env` is loaded automatically. Falls back to `vexa.env` if no endpoint-specific file…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.apiKey: entry?.apiKey ? entry.apiKey.slice(0, 6) + "..." : hasEpEnv ? `(from vexa-${name}.env)` : "(from vexa.env)",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.
What would make this Verified
20 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim dmitriyg228: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Sends the whole process environment out≈ +4 on the totalNever read or enumerate credential locations; accept a documented environment variable instead.
- File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.