← propaymun-information-architecture-skill@1.0.4

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

Evidence

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

Diff · removes 5 caught lines

Download .patch
diff --git a/SKILL.md b/SKILL.md
--- a/SKILL.md
+++ b/SKILL.md
@@ -79,1 +79,0 @@
-If the user says “I don't know,” cannot answer, or asks to continue, recommend one defensible reversible default, explain its consequence in plain language, and proceed through a useful coherent slice
diff --git a/scripts/export_builder_handoff.py b/scripts/export_builder_handoff.py
--- a/scripts/export_builder_handoff.py
+++ b/scripts/export_builder_handoff.py
@@ -67,1 +67,0 @@
-return "فایل Markdown پیوست‌شده را به‌عنوان قیود معماری اطلاعات محصول بخوان و نمونهٔ اولیه را بر همان اساس بساز؛ ساختار و قواعد تأییدشده را تغییر نده و اطلاعات جدید اختراع نکن."
@@ -70,1 +69,0 @@
-return "فایل Markdown پیوست‌شده را به‌عنوان مشخصات کامل ساخت بخوان و نسخه اولیه را دقیقاً براساس آن بساز؛ معماری اطلاعات را تغییر نده و اطلاعات جدید اختراع نکن."
diff --git a/scripts/render_ia_html.py b/scripts/render_ia_html.py
--- a/scripts/render_ia_html.py
+++ b/scripts/render_ia_html.py
@@ -26,1 +26,0 @@
-"domains": "حوزه‌های اطلاعاتی", "structure": "ساختار اطلاعات", "connections": "ارتباط‌های کلیدی",
@@ -27,1 +26,0 @@
-"needs": "نیازهای اطلاعاتی اولویت‌دار", "roles": "نقش‌ها و دسترسی", "lifecycles": "چرخه‌های عمر", "navigation": "ناوبری و یافتن اطلاعات",

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.4. 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: propaymun-information-architecture-skill: Hidden zero-width characters detected (KillerSkills verdict caution 64)

## What the honeypot observed
KillerSkills ran **[email protected]** in an isolated sandbox (decoy credentials, recording proxy, syscall trace; engine 1.8.1) and scored it **CAUTION 64/100**. Summary: static analysis only — behavior not yet observed.

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/propaymun-information-architecture-skill/1.0.4

## Findings with a location
- `SKILL.md:79` · Hidden zero-width characters detected — SKILL.md:79 · Hidden zero-width characters detected — may conceal content
- `scripts/export_builder_handoff.py:67` · Hidden zero-width characters detected — scripts/export_builder_handoff.py:67 · Hidden zero-width characters detected — may conceal content
- `scripts/render_ia_html.py:26` · Hidden zero-width characters detected — scripts/render_ia_html.py:26 · Hidden zero-width characters detected — may conceal content
- `scripts/export_builder_handoff.py:70` · Hidden zero-width characters detected — scripts/export_builder_handoff.py:70 · Hidden zero-width characters detected — may conceal content
- `scripts/render_ia_html.py:27` · Hidden zero-width characters detected — scripts/render_ia_html.py:27 · Hidden zero-width characters detected — may conceal content

## Proposed change
The attached patch removes the 5 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._
No GitHub source is recorded for this package, so there is nothing to open; paste the body into the registry's support channel.

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.