← keysrs@r1

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

Evidence

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

Diff · removes 9 caught lines

Download .patch
diff --git a/scripts/tests/site_fixture.cjs b/scripts/tests/site_fixture.cjs
--- a/scripts/tests/site_fixture.cjs
+++ b/scripts/tests/site_fixture.cjs
@@ -16,1 +16,0 @@
-if (ext === '.html') body = Buffer.from(body.toString().replace(/<link[^>]+href="https:\/\/fonts[^>]+>/g, ''));
diff --git a/Site/index.html b/Site/index.html
--- a/Site/index.html
+++ b/Site/index.html
@@ -464,1 +464,0 @@
-<summary>What does my agent actually see?</summary><p>Variable names, providers, the last four characters of a key, whether it's in your vault, and a token plus
@@ -467,1 +466,0 @@
-<summary>What happens when the 30 days are up?</summary><p>The token stops working and you get a notification about three days before. Ask your agent to set the
@@ -469,1 +467,0 @@
-<summary>Where's the window?</summary><p>Keysrs runs in the background. Open it from Applications or Spotlight, or run <code>keys dashboard</code>, to see your 
@@ -470,1 +467,0 @@
-<summary>How does a VM get a dummy key?</summary><p>Run <code>keys wrap</code> on the project's env file with your Worker's URL. Copy that file to the VM. Each 
@@ -471,1 +467,0 @@
-<summary>Does the Worker see my keys?</summary><p>No. It's a pipe you deploy from the repo into your own Cloudflare account; Keysrs hosts none. It holds one rel
diff --git a/Web/index.html b/Web/index.html
--- a/Web/index.html
+++ b/Web/index.html
@@ -34,1 +34,0 @@
-The status line has its own strip so a long message never covers a pane's header.
@@ -42,1 +41,0 @@
-First use only: an empty vault with nothing dismissed yet. It is filled from the help dialog's guide so the two can never drift apart, and it stays reachable fr
@@ -134,1 +132,0 @@
-The rows' gateway figures share the page's unit; this switch names what those figures show and moves them between requests and USD, which is everything a key's 

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of r1. 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: keysrs: Host or code assembled from base64 fragments (KillerSkills verdict caution 70)

## What the honeypot observed
KillerSkills ran **keysrs@r1** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.7) and scored it **CAUTION 70/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/keysrs/r1

## Findings with a location
- `scripts/tests/site_fixture.cjs:16` · Host or code assembled from base64 fragments — scripts/tests/site_fixture.cjs:16 · Host or code assembled from base64 fragments
- `Site/index.html:469` · Collapsed <details> block carrying instructions — Site/index.html:469 · Collapsed <details> block carrying instructions · informational: not an instruction file
- `Web/index.html:134` · HTML comment carrying imperative instructions to the agent — Web/index.html:134 · HTML comment carrying imperative instructions to the agent · informational: not an instruction file
- `Site/index.html:471` · Collapsed <details> block carrying instructions — Site/index.html:471 · Collapsed <details> block carrying instructions · informational: not an instruction file
- `Site/index.html:470` · Collapsed <details> block carrying instructions — Site/index.html:470 · Collapsed <details> block carrying instructions · informational: not an instruction file
- `Site/index.html:464` · Collapsed <details> block carrying instructions — Site/index.html:464 · Collapsed <details> block carrying instructions · informational: not an instruction file
- `Web/index.html:34` · HTML comment carrying imperative instructions to the agent — Web/index.html:34 · HTML comment carrying imperative instructions to the agent · informational: not an instruction file
- `Web/index.html:42` · HTML comment carrying imperative instructions to the agent — Web/index.html:42 · HTML comment carrying imperative instructions to the agent · informational: not an instruction file
- `Site/index.html:467` · Collapsed <details> block carrying instructions — Site/index.html:467 · Collapsed <details> block carrying instructions · informational: not an instruction file

## 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 gshost1/Keysreallysafe --clone && cd Keysreallysafe
curl -s https://killerskills.ai/skills/glama/keysrs/r1/patch.diff | git apply --unidiff-zero
git checkout -b killerskills/r1 && git commit -am "keysrs: Host or code assembled from base64 fragments"
gh pr create --fill --body-file <(curl -s https://killerskills.ai/skills/glama/keysrs/r1/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.