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. 62 · Caution

Evidence

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

Diff · removes 5 caught lines

Download .patch

diff --git a/mcp-server/src/browser-product.js b/mcp-server/src/browser-product.js
--- a/mcp-server/src/browser-product.js
+++ b/mcp-server/src/browser-product.js
@@ -300,1 +300,0 @@
-//                            SIGNED OUT and type the credentials. Handing it a saved session
@@ -563,1 +562,0 @@
-…t = 0, launch = false, workspaceRoot, githubProvider, publicOrigin = "", trustedProxyToken = "", directLogin = null, publicEgressOnly = null, publicAccess = false, access…
@@ -564,1 +562,0 @@
-const hosted = !!trustedProxyToken || !!directLogin || !!publicAccess;
@@ -778,1 +775,0 @@
-const proxyAuthenticated = !!trustedProxyToken && sameSecret(request.headers["x-tapp-proxy-token"], trustedProxyToken);
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -20,1 +20,0 @@
-A real Tapp focus run reaches Update Profile from source and an observed route

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.35.6. 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: tapp: Credential pass-through configuration (KillerSkills verdict caution 62)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/npm/tapp/0.35.6

## Findings with a location
- `mcp-server/src/browser-product.js:564` · Credential pass-through configuration — mcp-server/src/browser-product.js:564 · Credential pass-through configuration — agent relays sensitive credentials
- `mcp-server/src/browser-product.js:778` · Credential pass-through configuration — mcp-server/src/browser-product.js:778 · Credential pass-through configuration — agent relays sensitive credentials
- `mcp-server/src/browser-product.js:300` · Prompting user to enter sensitive credentials — mcp-server/src/browser-product.js:300 · Prompting user to enter sensitive credentials — social engineering
- `mcp-server/src/browser-product.js:563` · Credential pass-through configuration — mcp-server/src/browser-product.js:563 · Credential pass-through configuration — agent relays sensitive credentials
- `README.md:20` · Image alt text carrying instructions — README.md:20 · Image alt text carrying instructions

## Proposed change
The attached patch removes the 5 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._

Open the issue on GitHub (aarwitz/tapp)Fork to open a PR

# or from a terminal, under your own account:
gh repo fork aarwitz/tapp --clone && cd tapp
curl -s https://killerskills.ai/skills/npm/tapp/0.35.6/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/0.35.6 && git commit -am "tapp: Credential pass-through configuration"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/npm/tapp/0.35.6/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.