Propose a patch

Evidence

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

diff --git a/scripts/self-test.mjs b/scripts/self-test.mjs
--- a/scripts/self-test.mjs
+++ b/scripts/self-test.mjs
@@ -211,1 +211,0 @@
-run("extract rejects password userinfo before key without echo", ["extract", "https://user:[email protected]/", "--no-cache", "--no-log"], {
@@ -214,1 +213,0 @@
-stderrExcludes: ["https://user:[email protected]/", "user:pass", "[email protected]"],

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.36. 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: tavily-search-pro-native-node: URL with embedded credentials (KillerSkills verdict caution 57)

## 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 57/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/tavily-search-pro-native-node/1.0.36

## Findings with a location
- `scripts/self-test.mjs:214` · URL with embedded credentials — scripts/self-test.mjs:214 · URL with embedded credentials — may be phishing or credential leaking
- `scripts/self-test.mjs:211` · URL with embedded credentials — scripts/self-test.mjs:211 · URL with embedded credentials — may be phishing or credential leaking

## 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._