Skip to content

[estate-tracker] panic-attack Track C + Cargo.lock Track E roll-up (49+26 repos, ~1029+140 findings) #313

Description

@hyperpolymath

Estate-wide security-triage roll-up — 2026-05-30

Rolls up the per-repo security: N Critical/High panic-attack findings need human triage (Track C) issues filed estate-wide via automation 2026-05-26, plus the companion security: N CVE advisories in Cargo.lock (bridge triage, Track E) issues filed 2026-05-26/27.

This tracker is navigational, not load-bearing: the per-repo issues remain canonical. Use this to prioritize where to spend triage time first.

Track C — panic-attack Critical/High findings

49 repos · ~1,029 findings

RepoIssueFindings
julia-ecosystem#6209
developer-ecosystem#83166
gitbot-fleet#20751
panll#4844
standards#17839
reposystem#6837
ambientops#10334
proven#6833
grim-repo#2229
protocol-squisher#6423
idaptik#9923
svalinn#1319
burble#9119
wordpress-tools#2518
patallm-gallery#5515
academic-workflow-suite#20115
my-lang#6714
stapeln#6313
januskey#3713
verisimdb#4710
eclexia#2010
conflow#1710
claude-integrations#3810
bofig#8010
ssg-collection#139
asdf-tool-plugins#329
affinescript#3789
valence-shell#338
game-server-admin#208
ephapax#1388
echidna#1048
conative-gating#538
proven-servers#127
odds-and-sods-package-manager#317
boj-server#1557
absolute-zero#437
wokelang#616
proof-burrower#146
project-wharf#346
palimpsest-plasma#196
betlang#316
zotero-tools#145
vex-tools#245
vexometer#205
social-media-tools#275
maa-framework#725
fireflag#295
file-soup#415
accessibility-everywhere#415

Track E — CVE advisories in Cargo.lock

26 repos · ~140 CVEs

RepoIssueCVEs
git-reticulator#1024
docmatrix#2122
presswerk#4020
formatrix-docs#1319
intsoc-transactor#1616
vcs-ircd#365
verisimdb#484
hesiod-dns-map#474
multiterm#13
bunsenite#483
zerostep#392
reposystem#692
eclexia#212
007#162
veridical-simulation-core#51
rpa-elysium#471
proof-of-work#711
project-wharf#351
panll#491
januskey#381
hypatia#3301
ephapax#1391
echidnabot#181
conflow#181
cloudguard-server#161
cloudguard-cli#151

What this tracker IS

  • A single place to see the scale of the per-repo automation backlog (1029 Track C + 140 Track E).
  • A navigational index for triage prioritization.
  • A pointer for future automation: when the per-repo issues update (counts go down as findings are addressed), this roll-up can be regenerated.

What this tracker is NOT

  • It does not replace the per-repo issues — those remain canonical.
  • It does not itself triage anything; closing this tracker without addressing the per-repo backlog would be cosmetic.
  • It does not double-count: each finding lives in exactly one per-repo issue.

Suggested prioritization

  • Top-10 Track C repos account for 665 of 1029 findings (~65%). Triaging just those would clear two-thirds of the backlog: julia-ecosystem, developer-ecosystem, gitbot-fleet, panll, standards, reposystem, ambientops, proven, grim-repo, protocol-squisher.
  • Track E top-5 account for 101 of 140 CVEs (~72%): git-reticulator, docmatrix, presswerk, formatrix-docs, intsoc-transactor. These are Cargo.lock churns — cargo update + verify might clear them in a single sweep per repo.

Related context

  • panic-attack#33 (VeriSimDB hexad persistence campaign) — feeds the bridge classifier that filters these findings.
  • panic-attack bridge classifier schema 0.2.0 (companion trackers panic-attack#74, ci: fix unresolvable setup-beam pins in 21 hypatia-scan.yml (Refs #64) #75).
  • hypatia#358 (consume panic-attack patch-bridge registry as a fact source) — closes the loop on auto-triage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    recurrence-metaMeta control-plane gap that generates other recurring issues (RCA 2026-06-24)recurringRecurring problem-class: same defect appears across many issues/repos (RCA 2026-06-24)

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions