Skills/Glama/envdoctor

envdoctor@0.1.0

VERIFIED· install only

Publisher claims: "Runs deterministic local environment checks against a repository and returns a JSON pass/fail report covering Node version, git and npm availability, lockfiles, and env-file key completeness without executing repository code or exposing secret values." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher cloudcorprecords · publishing for 8 daysInstalls 0Last detonated 3d ago
$npx skills add envdoctor
WatchReport an issue

Coverage

Nothing executable in the bundle ran; the trace covers the install step only.
Tested
every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What this means for the label: Verified 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 · no network
What we could not test
use of the skill by an agent

Connect it under the guard. Nothing executable in the bundle ran; the trace covers the install step only. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- <the server's command>

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 (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-12 and scored it 83/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 1 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessscript backend runs setup only
0.0sprocessscript backend runs setup only
0.0sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathssrc/core.ts:10 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* - ENV-FILE: when .env.example exists, .env exists and names every keyFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathspackage.json:9 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files…o: node version against engines, git present, package manager lockfile present, .env present when .env.example exists (names only, values never read), and required …Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/core.ts:13 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* Env values are never read into any output. The .env and .env.exampleFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstest/pipe.test.ts:48 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files// .env exists but names no keys, so every example key is missing.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstest/core.test.ts:185 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesassert.equal(envCheck?.fix, "copy .env.example to .env and fill values");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/core.ts:422 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesconst examplePath = join(root, ".env.example");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstest/core.test.ts:177 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileswriteFileSync(join(dir, ".env.example"), "API_KEY=\n", "utf8");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstest/pipe.test.ts:49 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileswriteFileSync(join(root, ".env"), "", "utf8");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathsDockerfile:23 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files…o: node version against engines, git present, package manager lockfile present, .env present when .env.example exists (names only, values never read), and required …Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/mcp.ts:13 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files…json engines, git is available, the expected lockfile for the project exists, a .env file is present when .env.example declares one is needed (only key names compar…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstest/core.test.ts:48 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileswriteFileSync(join(root, ".env.example"), "API_KEY=\nDATABASE_URL=\n", "utf8");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstest/core.test.ts:49 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileswriteFileSync(join(root, ".env"), "API_KEY=test-secret-value-123\nDATABASE_URL=test-secret-value-456\n", "utf8");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstest/pipe.test.ts:12 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* whose .env.example declares 4000 keys while its .env is empty: thatFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
Access to sensitive file pathstest/pipe.test.ts:47 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileswriteFileSync(join(root, ".env.example"), keys.join("\n") + "\n", "utf8");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈37 tok
1 file · 21 in bundle

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.