Propose a patch

Evidence

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

diff --git a/arxyne_platform/cli_onboarding.py b/arxyne_platform/cli_onboarding.py
--- a/arxyne_platform/cli_onboarding.py
+++ b/arxyne_platform/cli_onboarding.py
@@ -411,1 +411,0 @@
-print("Paste your API key. Arxyne reads which service it belongs to from the key itself,")
@@ -846,1 +845,0 @@
-import getpass
@@ -848,1 +846,0 @@
-secret = getpass.getpass("  Paste your API key: ").strip()

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.10.31. 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: arxyne: Prompting user to enter sensitive credentials (KillerSkills verdict caution 68)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.6) and scored it **CAUTION 68/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/arxyne/0.10.31

## Findings with a location
- `arxyne_platform/cli_onboarding.py:848` · Prompting user to enter sensitive credentials — arxyne_platform/cli_onboarding.py:848 · Prompting user to enter sensitive credentials — social engineering
- `arxyne_platform/cli_onboarding.py:846` · Credential pass-through configuration — arxyne_platform/cli_onboarding.py:846 · Credential pass-through configuration — agent relays sensitive credentials
- `arxyne_platform/cli_onboarding.py:411` · Prompting user to enter sensitive credentials — arxyne_platform/cli_onboarding.py:411 · Prompting user to enter sensitive credentials — social engineering

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