Propose a patch

Evidence

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

diff --git a/src/components/doorway-ui.tsx b/src/components/doorway-ui.tsx
--- a/src/components/doorway-ui.tsx
+++ b/src/components/doorway-ui.tsx
@@ -695,1 +695,0 @@
-register ? "Create a secure password" : "Enter your password"
diff --git a/src/app/globals.css b/src/app/globals.css
--- a/src/app/globals.css
+++ b/src/app/globals.css
@@ -1,1 +1,0 @@
-@import url("https://fonts.googleapis.com/css2?family=DM+Sans:wght@400;450;500;550;600;650;700&family=Instrument+Serif:ital@0;1&display=swap");

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: doorway: Prompting user to enter sensitive credentials (KillerSkills verdict caution 69)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/glama/doorway/0.1.0

## Findings with a location
- `src/components/doorway-ui.tsx:695` · Prompting user to enter sensitive credentials — src/components/doorway-ui.tsx:695 · Prompting user to enter sensitive credentials — social engineering
- `src/app/globals.css:1` · URL with embedded credentials — src/app/globals.css:1 · 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._