Propose a patch

Evidence

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

diff --git a/packages/cli/test/hardening.test.mjs b/packages/cli/test/hardening.test.mjs
--- a/packages/cli/test/hardening.test.mjs
+++ b/packages/cli/test/hardening.test.mjs
@@ -253,1 +253,0 @@
-assert.equal(publicUrl(`https://user:${SECRET}@app.test/x?token=${SECRET}#f`), 'https://app.test/x');
diff --git a/packages/cli/src/redact.ts b/packages/cli/src/redact.ts
--- a/packages/cli/src/redact.ts
+++ b/packages/cli/src/redact.ts
@@ -8,1 +8,0 @@
-// Credentials in any URL's userinfo (postgres://u:pw@, redis://:pw@, https://u:pw@), before the email pattern sees them.

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: attested: URL with embedded credentials (KillerSkills verdict caution 76)

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

## Findings with a location
- `packages/cli/test/hardening.test.mjs:253` · URL with embedded credentials — packages/cli/test/hardening.test.mjs:253 · URL with embedded credentials — may be phishing or credential leaking
- `packages/cli/src/redact.ts:8` · URL with embedded credentials — packages/cli/src/redact.ts:8 · 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._