This repo still specifies node 18 which is EOL. Update to latest LTS.
edit: Or, if this whole repo is getting deprecated, make it known in readme.
🤖 Refined and Investigated by Claude — 2026-08-06
Session: Wallet Hygiene cloud routine, run 2026-08-06
Labels added: Type → Task, Tech → Frontend
Investigation notes:
- Code: Not applicable — the linked GitHub issue (
safe-global/safe-react-apps#875) targets safe-react-apps, which is outside this routine's 6 scoped repos (safe-wallet-monorepo, safe-client-gateway, safe-config-service, safe-balance-service, safe-transaction-service, safe-queue-service, safe-decoder-service), so no code search was run against it.
- Notion: not applicable.
- Datadog/Mixpanel: not applicable.
- Unclear/missing: whether
safe-react-apps is still an actively maintained repo relevant to the Wallet team (the issue itself asks to clarify this in the README if not) is unresolved.
Flagged for a human: This issue has no recorded creator (createdBy/createdById both absent), and its only GitHub attachment points to safe-react-apps — a repo outside the 6 repos this routine treats as in-scope for the external-issue exclusion rule. Per that rule, an attachment to an out-of-scope repo does not make the issue external, so it was processed as internal rather than skipped, despite superficially resembling the bot-filed shapes this routine usually excludes. A human should confirm (a) whether safe-react-apps is still relevant to this team's backlog at all, and (b) the null-creator origin of this issue.
Auto-generated best-effort draft. Edit freely. React 👎 on this issue or ping to flag misses so I learn.
🤖 Refined and Investigated by Claude — 2026-09-03 (re-evaluation)
Session: Wallet Hygiene cloud routine, run 2026-09-03
Labels added: none
Investigation notes:
- Code: not applicable, same as prior pass — the linked GitHub issue targets
safe-react-apps, outside the 6 repos scoped for this routine's local investigation.
- Notion: not applicable.
- Datadog/Mixpanel: not applicable.
- Unclear/missing: still unresolved whether
safe-react-apps is actively maintained/relevant to this team.
Flagged for a human: Staleness has worsened — issue has now sat untouched in Triage (not even Backlog) for ~120 days (created 2026-05-06), well past the point a Triage-status issue should sit idle. Prior pass already flagged the null-creator + out-of-scope-repo (safe-react-apps) combination; that determination still holds (processed as internal per the repo-scope rule, not external). Recommend a human either triage this out (Won't Fix / route to the right repo's own tracker) or move it to Backlog with a real decision, since it structurally cannot be resolved by an agent scoped to the other 6 repos.
Auto-generated best-effort draft. Edit freely. React 👎 on this issue or ping to flag misses so I learn.
This repo still specifies node 18 which is EOL. Update to latest LTS.
edit: Or, if this whole repo is getting deprecated, make it known in readme.
🤖 Refined and Investigated by Claude — 2026-08-06
Session: Wallet Hygiene cloud routine, run 2026-08-06
Labels added: Type → Task, Tech → Frontend
Investigation notes:
safe-global/safe-react-apps#875) targetssafe-react-apps, which is outside this routine's 6 scoped repos (safe-wallet-monorepo, safe-client-gateway, safe-config-service, safe-balance-service, safe-transaction-service, safe-queue-service, safe-decoder-service), so no code search was run against it.safe-react-appsis still an actively maintained repo relevant to the Wallet team (the issue itself asks to clarify this in the README if not) is unresolved.Flagged for a human: This issue has no recorded creator (
createdBy/createdByIdboth absent), and its only GitHub attachment points tosafe-react-apps— a repo outside the 6 repos this routine treats as in-scope for the external-issue exclusion rule. Per that rule, an attachment to an out-of-scope repo does not make the issue external, so it was processed as internal rather than skipped, despite superficially resembling the bot-filed shapes this routine usually excludes. A human should confirm (a) whethersafe-react-appsis still relevant to this team's backlog at all, and (b) the null-creator origin of this issue.Auto-generated best-effort draft. Edit freely. React 👎 on this issue or ping to flag misses so I learn.
🤖 Refined and Investigated by Claude — 2026-09-03 (re-evaluation)
Session: Wallet Hygiene cloud routine, run 2026-09-03
Labels added: none
Investigation notes:
safe-react-apps, outside the 6 repos scoped for this routine's local investigation.safe-react-appsis actively maintained/relevant to this team.Flagged for a human: Staleness has worsened — issue has now sat untouched in Triage (not even Backlog) for ~120 days (created 2026-05-06), well past the point a Triage-status issue should sit idle. Prior pass already flagged the null-creator + out-of-scope-repo (
safe-react-apps) combination; that determination still holds (processed as internal per the repo-scope rule, not external). Recommend a human either triage this out (Won't Fix / route to the right repo's own tracker) or move it to Backlog with a real decision, since it structurally cannot be resolved by an agent scoped to the other 6 repos.Auto-generated best-effort draft. Edit freely. React 👎 on this issue or ping to flag misses so I learn.