← laserfiche-mcp@2.6.2
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. 63 · Caution
Evidence
The sandbox observed nothing beyond the static findings; the proposal cites those.
Diff · removes 9 caught lines
Download .patchdiff --git a/src/laserfiche_mcp/auth.py b/src/laserfiche_mcp/auth.py --- a/src/laserfiche_mcp/auth.py +++ b/src/laserfiche_mcp/auth.py @@ -29,1 +29,0 @@ -as :class:`PassthroughTokenStrategy`. Only meaningful under ``--http`` with @@ -410,1 +409,0 @@ -class PassthroughTokenStrategy(AuthStrategy): @@ -506,1 +504,0 @@ -return PassthroughTokenStrategy() diff --git a/tests/test_auth.py b/tests/test_auth.py --- a/tests/test_auth.py +++ b/tests/test_auth.py @@ -20,1 +20,0 @@ -PassthroughTokenStrategy, @@ -543,1 +542,0 @@ -# --- PassthroughTokenStrategy (delegated / on-behalf-of, beta) -------------- @@ -559,1 +557,0 @@ -strategy = PassthroughTokenStrategy() @@ -573,1 +570,0 @@ -strategy = PassthroughTokenStrategy() @@ -590,1 +586,0 @@ -assert isinstance(strategy, PassthroughTokenStrategy) diff --git a/src/laserfiche_mcp/permissions.py b/src/laserfiche_mcp/permissions.py --- a/src/laserfiche_mcp/permissions.py +++ b/src/laserfiche_mcp/permissions.py @@ -177,1 +177,0 @@ -``~/.ssh/id_rsa`` is caught as well.
Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 2.6.2. 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: laserfiche-mcp: Credential pass-through configuration (KillerSkills verdict caution 63)
## 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 63/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/laserfiche-mcp/2.6.2 ## Findings with a location - `src/laserfiche_mcp/auth.py:506` · Credential pass-through configuration — src/laserfiche_mcp/auth.py:506 · Credential pass-through configuration — agent relays sensitive credentials - `src/laserfiche_mcp/auth.py:29` · Credential pass-through configuration — src/laserfiche_mcp/auth.py:29 · Credential pass-through configuration — agent relays sensitive credentials - `src/laserfiche_mcp/auth.py:410` · Credential pass-through configuration — src/laserfiche_mcp/auth.py:410 · Credential pass-through configuration — agent relays sensitive credentials - `tests/test_auth.py:590` · Credential pass-through configuration — tests/test_auth.py:590 · Credential pass-through configuration — agent relays sensitive credentials - `tests/test_auth.py:573` · Credential pass-through configuration — tests/test_auth.py:573 · Credential pass-through configuration — agent relays sensitive credentials - `tests/test_auth.py:20` · Credential pass-through configuration — tests/test_auth.py:20 · Credential pass-through configuration — agent relays sensitive credentials - `tests/test_auth.py:543` · Credential pass-through configuration — tests/test_auth.py:543 · Credential pass-through configuration — agent relays sensitive credentials - `src/laserfiche_mcp/permissions.py:177` · References a credential file in the home directory — src/laserfiche_mcp/permissions.py:177 · References a credential file in the home directory - `tests/test_auth.py:559` · Credential pass-through configuration — tests/test_auth.py:559 · Credential pass-through configuration — agent relays sensitive credentials ## Proposed change The attached patch removes the 9 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 adventist-gc/laserfiche-mcp --clone && cd laserfiche-mcp curl -s https://killerskills.ai/skills/pypi/laserfiche-mcp/2.6.2/patch.diff | git apply --unidiff-zero git checkout -b killerskills/2.6.2 && git commit -am "laserfiche-mcp: Credential pass-through configuration" gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/pypi/laserfiche-mcp/2.6.2/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.