Skills/npm/labby

labby@2.7.0

CAUTION· startup only

Publisher claims: "Rust MCP gateway with Code Mode, authentication, setup, logs, CLI, HTTP API, and operator web UI." Observed in sandbox: sends data to release-assets.githubusercontent.com.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher dinglebear · publishing for 132 daysInstalls 0Last detonated 11 h ago

Coverage

Startup only; authenticated tool behavior not tested.
Tested
install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · contacted release-assets.githubusercontent.com (undeclared)
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Find out what these hosts are first. In the honeypot it contacted release-assets.githubusercontent.com, which nothing in the package names as its own. If that is the vendor's service, fine; if you cannot place it, do not connect it.

$vet-skills run --net release-assets.githubusercontent.com -- npx -y @dinglebear/labby

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-14 and scored it 67/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. Summary: sends data to release-assets.githubusercontent.com.

Behavior trace

Honeypot run · 21 s · 3 scenarios
t+CategoryObserved action
0.0sprocessinstall script run in the sandbox
0.3snetworkCONNECT tcp://github.com:443
0.3snetworkCONNECT tcp://release-assets.githubusercontent.com:443 · not in the allow-list, refused
0.3sprocessexited 1: labby: Failed to establish tunnel to release-assets.githubusercontent.com:443 via http://127.0.0.1:35099: HTTP/1.1 403 Egress blocked by sandbox
0.3sprocessinstall script run in the sandbox
0.5snetworkCONNECT tcp://github.com:443
0.5snetworkCONNECT tcp://release-assets.githubusercontent.com:443 · not in the allow-list, refused
0.5snetworkCONNECT tcp://github.com:443
0.5snetworkCONNECT tcp://release-assets.githubusercontent.com:443 · not in the allow-list, refused
0.5sprocessexited 1: labby: Failed to establish tunnel to release-assets.githubusercontent.com:443 via http://127.0.0.1:35099: HTTP/1.1 403 Egress blocked by sandbox
21snetworkCONNECT tcp://github.com:443
21snetworkCONNECT tcp://release-assets.githubusercontent.com:443 · not in the allow-list, refused
21sclaimedstartup only: exited (0) before answering · (node:84) [UNDICI-EHPA] Warning: EnvHttpProxyAgent is experimental, expect them to change at any time. (Use `node --trace-warnings ...` to show where the warning was created) labby: Failed to establish tunnel to release-assets.githubusercontent.com:443 via http://127.0.0.1:35365: HTTP/1.1 403 Egress blocked by sandbox labby: binary is not installed; postinstall may have failed
21sprocessscript backend runs setup only
21sprocesssecond launch, clock +45 days, CI unset
21snetworkCONNECT tcp://github.com:443
21snetworkCONNECT tcp://release-assets.githubusercontent.com:443 · not in the allow-list, refused
21sprocessexited 1: labby: Failed to establish tunnel to release-assets.githubusercontent.com:443 via http://127.0.0.1:34807: HTTP/1.1 403 Egress blocked by sandbox
21snetworkCONNECT tcp://github.com:443
21snetworkCONNECT tcp://release-assets.githubusercontent.com:443 · not in the allow-list, refused
21snetworkCONNECT tcp://github.com:443
21snetworkCONNECT tcp://release-assets.githubusercontent.com:443 · not in the allow-list, refused
21sprocessexited 1: labby: Failed to establish tunnel to release-assets.githubusercontent.com:443 via http://127.0.0.1:34807: HTTP/1.1 403 Egress blocked by sandbox

Static findings

HIGH
Access to sensitive file pathsscripts/check-package.js:239 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

No other findings across 2,532 lines in 9 files.

Cost to the agent

Instructions loaded
≈60 tok
1 file · 9 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @dinglebear/labby@2.7.0 as of 10 h ago. This is the package itself, not its dependencies.

What would make this Verified

13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. 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.
  2. Unclaimed publisher≈ +8 on the totalClaim dinglebear: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  3. 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.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim dinglebearPropose a patch to the maintainer