22 tracked files still carry internal tracker keys on this public repo

Open
#1,230 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
security

Research direction

Start by reading and running script/check-tracker-leaks.ts and its tests to identify the 22 tracked files containing internal tracker keys. Remove those references from the reported files without rewriting CHANGELOG.md, then verify the checker and existing tests pass and confirm the CI check remains clean.

Written by the indexing model from the issue text.

Description

Deferred from the v0.10.0 release review.

22 tracked files still carry internal tracker keys in comments and test fixtures. This repo is public, so those references leak internal ticket identifiers.

The three that this release introduced were scrubbed in the v0.10.0 PR, and script/check-tracker-leaks.ts now runs in CI (it existed with tests but was wired into no workflow, which is how they landed). So new ones are blocked going forward.

Cleaning the remaining backlog was kept out of the release PR because it would roughly double the diff with churn unrelated to the release.

Note: CHANGELOG.md history should not be rewritten as part of this.

Dominant language
TypeScript
Stars
813
Forks
134
Avg merge
2d 5h
Merged PRs (30d)
62

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AltimateAI/altimate-code

All issues in AltimateAI/altimate-code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.