Propose a patch

Evidence

The sandbox observed nothing beyond the static findings; the proposal cites those.

diff --git a/tests/fixtures/detail.html b/tests/fixtures/detail.html
--- a/tests/fixtures/detail.html
+++ b/tests/fixtures/detail.html
@@ -59,1 +59,0 @@
-…ma/proteam-insan-kaynaklari-f1471443","name":"Proteam İnsan Kaynakları","logo":"https://cdn.eleman.net/firma_logo/kucuk/1471443.gif"},"validThrough":"2026-12-07","responsibilities":"","workHours":"","specialCommitments":"","baseSalary":{"@type":"MonetaryAmount","currency":"TRY","value":{"@type":"QuantitativeValue","va…
diff --git a/tests/fixtures/garson.html b/tests/fixtures/garson.html
--- a/tests/fixtures/garson.html
+++ b/tests/fixtures/garson.html
@@ -52,1 +52,0 @@
-…rvis Personeli İlanı LÜTFEN WHATSAPP ÜZERİNDEN MESAJ YOLUYLA İLETİŞİME GEÇİNİZ… ​Firmamız, (TCDD) bünyesinde Yüksek Hızlı Tr...</span></span> <div class="u-flex …

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.1.0. If the behavior is intended, declare it (host under permissions.network, a line in the README) instead of removing it; the next crawl scores declarations.

Issue / PR body

Title: eleman-net-mcp: URL with embedded credentials (KillerSkills verdict caution 60)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 60/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/glama/eleman-net-mcp/0.1.0

## Findings with a location
- `tests/fixtures/detail.html:59` · URL with embedded credentials — tests/fixtures/detail.html:59 · URL with embedded credentials — may be phishing or credential leaking
- `tests/fixtures/garson.html:52` · Hidden zero-width characters detected — tests/fixtures/garson.html:52 · Hidden zero-width characters detected — may conceal content

## Proposed change
The attached patch removes the 2 lines above. If the behavior is intended, the fix is to declare it instead: list the host under `permissions.network` (or the MCP manifest) and say in the README why the package needs it; the next crawl will re-score it with the declaration taken into account.

## How this will be verified
Nothing is "verified safe" by assertion. When a new version is published, KillerSkills re-runs it in the honeypot and the verdict page updates; you can trigger it early from the verdict page ("Re-scan after I publish a fix"). Reply here or at [email protected] if you believe the verdict is wrong; disputes are reviewed by a person and the outcome is published on the verdict page.

_Proposed through killerskills.ai/threats by a user of the package, under their own GitHub account. The evidence is public; the package was never modified by KillerSkills._