Is ferc-form1@0.1.0 safe to install?

ferc-form1@0.1.0

VERIFIED

Publisher claims: "Enables users to look up utility financial statements, balance sheets, and plant summaries by utility name or FERC respondent ID and report year, with trend histories across annual filings." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher pipeworx-io · publishing for 7 daysInstalls 0Last detonated 7d ago

$npx skills add ferc-form1

Watch Report an issue

Coverage

Server started and answered tools/list.

Tested: MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested: what the tools do when called with real credentials

Before you give it your token

Code inventory arrives with this version's next honeypot run.

It will ask for: unknown until the next run
Where it talks to: unknown until the next run
What the honeypot saw: no credential files read · no network
What we could not test: what the tools do when called with real credentials

The run was clean; the code inventory is pending. Server started and answered tools/list. What the code asks for and which hosts it names arrive with the next run; until then, connect it under the guard with the network pinned to what the honeypot saw.

$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 (2 scenarios) on 2026-11-07 and scored it 85/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations

t+CategoryObserved action

0.0sprocessno install scripts in bundle

0.4sprocessexec /usr/bin/date

0.4sprocessexec /usr/bin/timeout

0.4sclaimed5 tools: ferc1_find_utility, ferc1_income_statement, ferc1_income_history, ferc1_balance_sheet, ferc1_utility_plant

0.4sprocessscript backend runs setup only

0.4sprocessno install scripts to re-run

Static findings

LOW

Unpinned dependency.github/workflows/publish.yml:65 · Unpinned dependencynpm install -g npm@latestFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.

AST06

MEDIUM

Privileged sudo command.github/workflows/publish.yml:334 · Privileged sudo command — agent may execute with elevated privilegessudo mv mcp-publisher /usr/local/bin/mcp-publisherFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.

AST05

MEDIUM

npx invocation of non-well-known packagebin/cli.js:2 · npx invocation of non-well-known package — may execute untrusted code// Entry point for `npx @pipeworx/mcp-<slug>` in gateway mode (bin/cli.js).Fix: Pin versions and sources; vendor anything fetched at install time.

AST06

Cost to the agent

Instructions loaded

≈38 tok

1 file · 9 in bundle

Tool list per prompt

≈1,013 tok

5 tools · 203 per tool

Handshake

373 ms

launch to tools/list, stdio

Undocumented tools

description under 20 chars · avg 254

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

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.