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. 60 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 4 caught lines
Download .patchdiff --git a/lucerna_mcp/api/api_client_base.py b/lucerna_mcp/api/api_client_base.py --- a/lucerna_mcp/api/api_client_base.py +++ b/lucerna_mcp/api/api_client_base.py @@ -7,1 +7,0 @@ -in once at client-construction time, and never a service-level/admin bypass @@ -47,1 +46,0 @@ -a bypass credential" invariant: ``opensearchpy.RequestsHttpConnection`` diff --git a/lucerna_mcp/auth.py b/lucerna_mcp/auth.py --- a/lucerna_mcp/auth.py +++ b/lucerna_mcp/auth.py @@ -4,1 +4,0 @@ -PRINCIPAL's own bearer token, never a service-level/admin bypass credential @@ -75,1 +74,0 @@ -# entire contract is "never fall back to a bypass credential" (CA-43) —
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 0.3.7. 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: lucerna-mcp: Credential pass-through configuration (KillerSkills verdict caution 60)
## What the honeypot observed KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 60/100**. Summary: static analysis only — behavior not yet observed. - See the findings below. Full trace and findings: https://killerskills.ai/skills/pypi/lucerna-mcp/0.3.7 ## Findings with a location - `lucerna_mcp/api/api_client_base.py:7` · Credential pass-through configuration — lucerna_mcp/api/api_client_base.py:7 · Credential pass-through configuration — agent relays sensitive credentials - `lucerna_mcp/api/api_client_base.py:47` · Credential pass-through configuration — lucerna_mcp/api/api_client_base.py:47 · Credential pass-through configuration — agent relays sensitive credentials - `lucerna_mcp/auth.py:4` · Credential pass-through configuration — lucerna_mcp/auth.py:4 · Credential pass-through configuration — agent relays sensitive credentials - `lucerna_mcp/auth.py:75` · Credential pass-through configuration — lucerna_mcp/auth.py:75 · Credential pass-through configuration — agent relays sensitive credentials ## Proposed change The attached patch removes the 4 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._
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.