viasocket-apps@0.21.0
CAUTION· install onlyPublisher claims: "viaSocket for your product and your coding agent: let your users connect any of 2,300+ apps, run actions and react to events; an AI assistant on any model with your endpoints as tools; AI memory per user; login, teams and organisations; automations per us" Observed in sandbox: sends data to flow.viasocket.com, connect.viasocket.com.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 2 of 2 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
What changed since 0.19.0
vet-skills diff viasocket-apps 0.19.0 0.21.0This version reaches for something 0.19.0 did not: 5 new hosts (connect.viasocket.com, flow.viasocket.com, msg91.com, sokt.io, …) · 4 new credential variables (MCP_TOKEN_ENV, VIASOCKET_EMBED_SECRET, VIASOCKET_OAUTH_RESOURCE, VIASOCKET_TEST_EMBED_TOKEN). Compared from the two recorded runs, not from source.
- New hosts
- connect.viasocket.com, flow.viasocket.com, msg91.com, sokt.io, viasocket.com
- New credential variables
- MCP_TOKEN_ENV, VIASOCKET_EMBED_SECRET, VIASOCKET_OAUTH_RESOURCE, VIASOCKET_TEST_EMBED_TOKEN
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-20 and scored it 55/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: Auto-update or dynamic fetch configuration; Auto-update or dynamic fetch configuration; Access to sensitive file paths. Summary: sends data to flow.viasocket.com, connect.viasocket.com.
Behavior trace
Honeypot run · 0 s · 2 scenariosStatic findings
if (block.enableSearchApi || block.willDynamicFetchOptions)Fix: Pin versions and sources; vendor anything fetched at install time.if (block.enableSearchApi || block.willDynamicFetchOptions)Fix: Pin versions and sources; vendor anything fetched at install time.* npx -y viasocket-apps login [--env .env] [--no-open] [--timeout 300]Fix: Pin versions and sources; vendor anything fetched at install time.* It never reads a .env file, sends only the slugs, keys and ids it finds to viaSocket, and printsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* npx -y viasocket-apps setup [--env .env] [--project <id> | --new] [--name <title>] [--no-open] [--timeout 300]Fix: Pin versions and sources; vendor anything fetched at install time.* npx -y viasocket-apps oauth-app <app> [--id-env <NAME> --secret-env <NAME>] [--remove] [--env .env]Fix: Pin versions and sources; vendor anything fetched at install time.* viasocket-login.mjs — signs in to viaSocket from the command line and sets up .env.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.say('FAIL', where, 'VIASOCKET_EMBED_SECRET is a string literal in source — it lives in .env and nowhere else')Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* npx -y viasocket-apps connect <app> [--user <id>] [--env .env] [--no-open] [--timeout 300]Fix: Pin versions and sources; vendor anything fetched at install time.'usage: node viasocket-check.mjs [folder or file ...] (or: npx -y viasocket-apps check [folder or file ...])',Fix: Pin versions and sources; vendor anything fetched at install time.* npx -y viasocket-apps oauth-app <app> [--id-env <NAME> --secret-env <NAME>] [--remove] [--env .env]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* block with no `options` (or with `enableSearchApi` / `willDynamicFetchOptions`), and anFix: Pin versions and sources; vendor anything fetched at install time.* npx -y viasocket-apps setup [--env .env] [--project <id> | --new] [--name <title>] [--no-open] [--timeout 300]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* npx -y viasocket-apps login [--env .env] [--no-open] [--timeout 300]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* npx -y viasocket-apps mcp [--file viasocket.mcp.json] [--ids viasocket.mcp.ids.json] [--call <tool> --args <json> --token <t>]Fix: Pin versions and sources; vendor anything fetched at install time.* npx -y viasocket-apps connect <app> [--user <id>] [--env .env] [--no-open] [--timeout 300]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* user's servers, nor yours. Your product's own single MCP server is made with `npx viasocket-apps mcp` instead.Fix: Pin versions and sources; vendor anything fetched at install time.if (name.startsWith('.env') || name === 'viasocket-check.mjs' || name === 'viasocket-login.mjs') return falseFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* as the `viasocket.mcp.json` of `npx viasocket-apps mcp`, without the slug (a URL alias is yours, not a user's).Fix: Pin versions and sources; vendor anything fetched at install time.…; plus the skill for building your own automations and plugs on viaSocket, and `npx viasocket-apps login`.", "keywords": [ "viasocket", "integrations", "automation"…Fix: Pin versions and sources; vendor anything fetched at install time.* as the `viasocket.mcp.json` of `npx viasocket-apps mcp`, without the slug (a URL alias is yours, not a user's).Fix: Pin versions and sources; vendor anything fetched at install time.* user's servers, nor yours. Your product's own single MCP server is made with `npx viasocket-apps mcp` instead.Fix: Pin versions and sources; vendor anything fetched at install time.* as the `viasocket.mcp.json` of `npx viasocket-apps mcp`, without the slug (a URL alias is yours, not a user's).Fix: Pin versions and sources; vendor anything fetched at install time.* user's servers, nor yours. Your product's own single MCP server is made with `npx viasocket-apps mcp` instead.Fix: Pin versions and sources; vendor anything fetched at install time.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
Not checked against OSV yet; the weekly check has not reached this version.
What would make this Verified
25 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Contacts a host you did not declare≈ +23 on the totalList every host you talk to in SKILL.md frontmatter (`network: [api.example.com]`), or stop contacting the ones you cannot justify.
- Unclaimed publisher≈ +8 on the totalClaim walkover-web-solution: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- 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.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.