← nanobanana-imagen-mcp@1.2.0

Propose a patch

A fix the maintainer can act on, with the evidence attached. It opens under your GitHub account in your browser; KillerSkills holds no token and never modifies the package. The fix is verified the only way we verify anything: the next crawl re-runs the new version in the honeypot. 79 · Caution

Evidence

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

Diff · removes 2 caught lines

Download .patch
diff --git a/tests/test_fleet_regressions.py b/tests/test_fleet_regressions.py
--- a/tests/test_fleet_regressions.py
+++ b/tests/test_fleet_regressions.py
@@ -53,1 +53,0 @@
-"~/.ssh/key.png", "~/.aws/credentials", "~/.config/gcloud/key.png", "x\x00.png"])
diff --git a/nanobanana_mcp_server/tools/generate_image.py b/nanobanana_mcp_server/tools/generate_image.py
--- a/nanobanana_mcp_server/tools/generate_image.py
+++ b/nanobanana_mcp_server/tools/generate_image.py
@@ -434,1 +434,0 @@
-extra_info += f" • 👨‍👩‍👧 Parent: {meta.get('parent_file_id')}"

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.2.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: nanobanana-imagen-mcp: References a credential file in the home directory (KillerSkills verdict caution 79)

## 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 79/100**. Summary: no network, touches nothing outside the project, writes no memory.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/pypi/nanobanana-imagen-mcp/1.2.0

## Findings with a location
- `tests/test_fleet_regressions.py:53` · References a credential file in the home directory — tests/test_fleet_regressions.py:53 · References a credential file in the home directory
- `nanobanana_mcp_server/tools/generate_image.py:434` · Hidden zero-width characters detected — nanobanana_mcp_server/tools/generate_image.py:434 · 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._
# or from a terminal, under your own account:
gh repo fork u2n4/gemini-media-mcp --clone && cd gemini-media-mcp
curl -s https://killerskills.ai/skills/pypi/nanobanana-imagen-mcp/1.2.0/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/1.2.0 && git commit -am "nanobanana-imagen-mcp: References a credential file in the home directory"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/nanobanana-imagen-mcp/1.2.0/patch.md)

We count proposals opened, not merged: a merge shows up as a new version that the crawl re-runs. Disputes: the maintainer can contest the verdict from its page; a person reviews it and the outcome is published.