registry / @chrono-meta/fh-gate / 1.4.55

@chrono-meta/fh-gate@1.4.55

FH runtime adapters — run FH governance, skills, and agents via Claude or Codex with machine-parseable gates.

Static Scan Results

scanned 3h ago · by rust-scanner

Static analysis flagged 8 finding(s) at 72.0% confidence. This version is warn-only unless an AI or security-team review confirms malicious behavior.

Static reason

One or more suspicious static signals were detected.

Decision evidence

public snapshot

Behavioral surface

Source

ChildProcessFilesystem

Supply chain

HighEntropyStrings

ManifestNo manifest risk signals triggered.

scanned 4 file(s), 13.1 KB of source

Source & flagged code

3 flagged

plugins/fh-meta/skills/public-surface-audit/SKILL.mdView file

Lines 109-149markdown

109**Binary / generated carve-out**: skip binaries. Additionally note (do not auto-suppress) hits inside

110generated artifacts (e.g. `paper/*.html` exported from a private source) — these are real leaks on the

111public surface and must be reported, but the fix is "regenerate from a sanitized source," not "edit the

112HTML by hand." Flag them with a `(generated artifact)` note.

113

114> **Detail**: See `SKILL_detail.md §Step3-Scan-Script` — the grep-per-pattern bash implementation,

115> flag reference (`-n`/`-I`/`-E`) — read when executing this step.

116

117---

118

119## Step 3b. FP Hygiene — Placeholder & Example Exclusion

120

121A scan that flags its own placeholders erodes trust. Two **value-shape** classes are never real leaks

122and are dropped before the report — imported from `gstack-redact`'s canonical-example allowlist, scoped

123in PSA's direction to the *matched token* (not the whole line, so a real leak sharing a substring still

124reports):

125

126- **Angle-bracket placeholders** — the matched token is itself a placeholder (`<your-unix-username>`,

127 `<company-asset>`, `{project}`). PSA dogfoods these in Step 1; the scan must not report them as leaks.

128- **Canonical dummy values** — the matched token is a documented example/dummy (`EXAMPLE`, `dummy`,

129 `changeme`, `REDACTED`, `xxxx`, AWS-doc keys like `AKIAIOSFODNN7EXAMPLE`). A high-entropy *example* is

Critical

Critical Secret

Package contains a critical-looking secret pattern.

plugins/fh-meta/skills/public-surface-audit/SKILL.mdView on unpkg · L129

Critical

Secret Pattern

AWS access key ID in plugins/fh-meta/skills/public-surface-audit/SKILL.md

plugins/fh-meta/skills/public-surface-audit/SKILL.mdView on unpkg · L129

130 not a secret.

131

132This differs from the Step 2 allowlist: Step 2 suppresses by **file::token legitimacy**, Step 3b by

133**token value-shape**. Both run — Step 2 then Step 3b. Keep it tight (PSA's "allowlist tight" rule): if a

134token only *contains* an example substring but is otherwise a real private value, it still reports.

135

136> **Detail**: See `SKILL_detail.md §Step3b-FP-Hygiene-Script` — the token-shape-only extraction bash

137> implementation (never line-level) — read when executing this step.

138

139---

140

141## Step 3c. Ignore-Verification — the gitignore-mistake safeguard (root-cause, runs before Step 4)

142

143Steps 3/3b scan what **is** tracked. This step checks the inverse and the upstream cause: a file you

144*intend* to be private that is **not actually ignored** — the gitignore mistake that becomes tomorrow's

145tracked leak. For each expected-private path, `git check-ignore -v` reports whether it is ignored **and

146by which layer** (committed `.gitignore` · local `.git/info/exclude` · global `core.excludesFile`). A

147path that resolves to no ignore rule is a MISS — surface it before it is ever `git add`ed.

148

149- **OK** — ignored; the report names which layer covers it (operator-private files should resolve to

scripts/fh-gate.shView file

•path = scripts/fh-gate.sh kind = build_helper sizeBytes = 21599 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

scripts/fh-gate.shView on unpkg

Source & flagged code

3 flagged · loading source

plugins/fh-meta/skills/public-surface-audit/SKILL.mdView file

129patternName = aws_access_key severity = critical line = 129 matchedText = `changem...* is

Critical

Critical Secret

Package contains a critical-looking secret pattern.

plugins/fh-meta/skills/public-surface-audit/SKILL.mdView on unpkg · L129

129patternName = aws_access_key severity = critical line = 129 matchedText = `changem...* is

Critical

Secret Pattern

AWS access key ID in plugins/fh-meta/skills/public-surface-audit/SKILL.md

plugins/fh-meta/skills/public-surface-audit/SKILL.mdView on unpkg · L129

scripts/fh-gate.shView file

•path = scripts/fh-gate.sh kind = build_helper sizeBytes = 21599 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

scripts/fh-gate.shView on unpkg

Findings

2 Critical2 Medium4 Low

CriticalCritical Secretplugins/fh-meta/skills/public-surface-audit/SKILL.md

CriticalSecret Patternplugins/fh-meta/skills/public-surface-audit/SKILL.md

MediumShips Build Helperscripts/fh-gate.sh

MediumStructural Risk Force Deep Review

LowNon Install Lifecycle Scripts

LowScripts Present

LowFilesystem

LowHigh Entropy Strings

Source & flagged code

3 flagged

plugins/fh-meta/skills/public-surface-audit/SKILL.mdView file

Lines 109-149markdown

109**Binary / generated carve-out**: skip binaries. Additionally note (do not auto-suppress) hits inside

110generated artifacts (e.g. `paper/*.html` exported from a private source) — these are real leaks on the

111public surface and must be reported, but the fix is "regenerate from a sanitized source," not "edit the

112HTML by hand." Flag them with a `(generated artifact)` note.

113

114> **Detail**: See `SKILL_detail.md §Step3-Scan-Script` — the grep-per-pattern bash implementation,

115> flag reference (`-n`/`-I`/`-E`) — read when executing this step.

116

117---

118

119## Step 3b. FP Hygiene — Placeholder & Example Exclusion

120

121A scan that flags its own placeholders erodes trust. Two **value-shape** classes are never real leaks

122and are dropped before the report — imported from `gstack-redact`'s canonical-example allowlist, scoped

123in PSA's direction to the *matched token* (not the whole line, so a real leak sharing a substring still

124reports):

125

126- **Angle-bracket placeholders** — the matched token is itself a placeholder (`<your-unix-username>`,

127 `<company-asset>`, `{project}`). PSA dogfoods these in Step 1; the scan must not report them as leaks.

128- **Canonical dummy values** — the matched token is a documented example/dummy (`EXAMPLE`, `dummy`,

129 `changeme`, `REDACTED`, `xxxx`, AWS-doc keys like `AKIAIOSFODNN7EXAMPLE`). A high-entropy *example* is

Critical

Critical Secret

Package contains a critical-looking secret pattern.

plugins/fh-meta/skills/public-surface-audit/SKILL.mdView on unpkg · L129

Critical

Secret Pattern

AWS access key ID in plugins/fh-meta/skills/public-surface-audit/SKILL.md

plugins/fh-meta/skills/public-surface-audit/SKILL.mdView on unpkg · L129

130 not a secret.

131

132This differs from the Step 2 allowlist: Step 2 suppresses by **file::token legitimacy**, Step 3b by

133**token value-shape**. Both run — Step 2 then Step 3b. Keep it tight (PSA's "allowlist tight" rule): if a

134token only *contains* an example substring but is otherwise a real private value, it still reports.

135

136> **Detail**: See `SKILL_detail.md §Step3b-FP-Hygiene-Script` — the token-shape-only extraction bash

137> implementation (never line-level) — read when executing this step.

138

139---

140

141## Step 3c. Ignore-Verification — the gitignore-mistake safeguard (root-cause, runs before Step 4)

142

143Steps 3/3b scan what **is** tracked. This step checks the inverse and the upstream cause: a file you

144*intend* to be private that is **not actually ignored** — the gitignore mistake that becomes tomorrow's

145tracked leak. For each expected-private path, `git check-ignore -v` reports whether it is ignored **and

146by which layer** (committed `.gitignore` · local `.git/info/exclude` · global `core.excludesFile`). A

147path that resolves to no ignore rule is a MISS — surface it before it is ever `git add`ed.

148

149- **OK** — ignored; the report names which layer covers it (operator-private files should resolve to

scripts/fh-gate.shView file

•path = scripts/fh-gate.sh kind = build_helper sizeBytes = 21599 magicHex = [redacted]

Medium

Ships Build Helper

Package ships non-JavaScript build or shell helper files.

scripts/fh-gate.shView on unpkg