← arc-sentinel@1.0.0

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. 48 · Blocked

Evidence

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

Diff · removes 11 caught lines

Download .patch
diff --git a/scripts/permission-auditor.sh b/scripts/permission-auditor.sh
--- a/scripts/permission-auditor.sh
+++ b/scripts/permission-auditor.sh
@@ -125,1 +125,0 @@
-emit_finding "INFO" "SSH Directory" "No ~/.ssh directory found"
@@ -134,1 +133,0 @@
-"$HOME/.config/gh/hosts.yml"
@@ -135,1 +133,0 @@
-"$HOME/.netrc"
@@ -136,1 +133,0 @@
-"$HOME/.npmrc"
@@ -138,1 +134,0 @@
-"$HOME/.docker/config.json"
@@ -139,1 +134,0 @@
-"$HOME/.kube/config"
diff --git a/scripts/token-watchdog.sh b/scripts/token-watchdog.sh
--- a/scripts/token-watchdog.sh
+++ b/scripts/token-watchdog.sh
@@ -177,1 +177,0 @@
-DOCKER_CONFIG="$HOME/.docker/config.json"
@@ -200,1 +199,0 @@
-NPMRC="$HOME/.npmrc"
@@ -203,1 +201,0 @@
-emit_token "INFO" "NPM" "Auth token present in ~/.npmrc"
@@ -205,1 +202,0 @@
-emit_token "MISSING" "NPM" "No auth token in ~/.npmrc"
@@ -208,1 +204,0 @@
-emit_token "MISSING" "NPM" "No ~/.npmrc found"

Zero-context hunks: apply with git apply --unidiff-zero fix.patch on the tagged source of 1.0.0. 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: arc-sentinel: Reads credential paths from the home directory (KillerSkills verdict blocked 48)

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

- See the findings below.

Full trace and findings: https://killerskills.ai/skills/clawhub/arc-sentinel/1.0.0

## Findings with a location
- `scripts/permission-auditor.sh:125` · Reads credential paths from the home directory — scripts/permission-auditor.sh:125 · Reads credential paths from the home directory
- `scripts/token-watchdog.sh:203` · References a credential file in the home directory — scripts/token-watchdog.sh:203 · References a credential file in the home directory
- `scripts/token-watchdog.sh:205` · References a credential file in the home directory — scripts/token-watchdog.sh:205 · References a credential file in the home directory
- `scripts/permission-auditor.sh:138` · References a credential file in the home directory — scripts/permission-auditor.sh:138 · References a credential file in the home directory
- `scripts/token-watchdog.sh:200` · References a credential file in the home directory — scripts/token-watchdog.sh:200 · References a credential file in the home directory
- `scripts/token-watchdog.sh:177` · References a credential file in the home directory — scripts/token-watchdog.sh:177 · References a credential file in the home directory
- `scripts/token-watchdog.sh:208` · References a credential file in the home directory — scripts/token-watchdog.sh:208 · References a credential file in the home directory
- `scripts/permission-auditor.sh:134` · References a credential file in the home directory — scripts/permission-auditor.sh:134 · References a credential file in the home directory
- `scripts/permission-auditor.sh:136` · References a credential file in the home directory — scripts/permission-auditor.sh:136 · References a credential file in the home directory
- `scripts/permission-auditor.sh:135` · References a credential file in the home directory — scripts/permission-auditor.sh:135 · References a credential file in the home directory
- `scripts/permission-auditor.sh:139` · References a credential file in the home directory — scripts/permission-auditor.sh:139 · References a credential file in the home directory

## Proposed change
The attached patch removes the 11 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.