Skip to content

Remove private/internal references from 2026-07-14 - #8

Open
boardwalk-bot[bot] wants to merge 1 commit into
mainfrom
boardwalk/private-reference-scan-2026-07-14
Open

boardwalk-bot[bot] wants to merge 1 commit into
mainfrom
boardwalk/private-reference-scan-2026-07-14

Conversation

@boardwalk-bot

@boardwalk-bot boardwalk-bot Bot commented Jul 14, 2026

Copy link
Copy Markdown

Automated remediation from Boardwalk's daily private reference scan.

Summary: Two high-severity findings were identified in the public repo boardwalk-labs/cli: a direct link to an internal Claude code session and a hardcoded internal hostname in a public test case. Both represent unnecessary exposure of private workflow artifacts and internal infrastructure details.

Findings addressed:

  • high README (commit message context): https://claude.ai/code/session_01MK51DnD8bjW7JvkzHKDawd — Remove the Claude-Session URL from the commit message and any associated documentation. If session context needs to be preserved for internal review, store it in an internal ticket or private notes rather than public commit history.
  • high src/render/renderer.test.ts: internal.example — Replace 'internal.example' with a fully generic placeholder like 'blocked-host.example.com' or use a constants file with clearly generic test values (e.g., 'test-host.example.com') that do not imply internal infrastructure.
  • low Commit message context: Claude Fable 5 <noreply@anthropic.com> — Generalize the co-author to 'AI Assistant' or remove the specific internal codename if it is not publicly documented. However, since the email is from Anthropic's public domain, this is likely a low-risk artifact of the AI coding tool.

Please review carefully before merging. If any finding involved an actual credential, rotate it out-of-band.

Automated remediation for daily private reference scan.

@boardwalk-bot boardwalk-bot Bot left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review: changes suggested

The hostname fixture is generalized correctly, but the PR does not fully deliver its stated remediation: the private Claude session URL remains exposed in the PR metadata and no README change is shown.

Findings

  • major PR description / commit-message metadata: The PR claims to remove https://claude.ai/code/session_01MK51DnD8bjW7JvkzHKDawd, but reproduces that exact URL in its public description, and the supplied diff contains no README or metadata remediation. Remove the URL from the PR description and rewrite the affected commit message/history as applicable before merging.

Posted by the Boardwalk PR reviewer (non-blocking).

nrcrews added a commit that referenced this pull request Aug 4, 2026
…ace run attribution

Two Lifeguard dogfood findings, both CLI-side gaps over server capabilities that already
shipped.

#2: rotate-in-place has existed server-side since the backend's d662cdaf (POST
/v1/secrets/:id/rotate, PutSecretValue at the same ARN, secret:rotate already in the
elevated CLI scopes) but the CLI never exposed it, so repairing a mangled value meant a
rename + descriptor change + redeploy of every consumer. `secrets set` is now an upsert:
on a 409 it resolves the name to its id and rotates. A name that exists only inside an
environment still surfaces the conflict — guessing which environment was meant would
write the wrong tenant's credential.

#8: RunListItem now carries costUsd + the resolved concurrencyKey/workspaceKey when the
server reports them (absent otherwise, so --json on an older server shows no misleading
nulls). This also fixes `runs <id>`'s Spend line, which was declared and rendered but
never parsed, so it never appeared.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019FfM1VMV8KiRsX6cfw6dA6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants