chore: scrub committed API keys + security baseline - #1409
Merged
Conversation
Console Labs consolidation hardening (lighter adoption). - SECURITY: pkg/config/config.go hardcoded SOLSCAN_TOKEN + BIRDEYE_API_KEY as viper defaults in this PUBLIC repo. Scrubbed to "" (env-only). The exposed keys must be ROTATED at the providers (still in git history). See docs/SECURITY-AUDIT-2026-06-25.md. - .gitleaks.toml: allowlist test/seed/sample fixtures (47 false positives) so CI gates on real leaks; gitleaks now clean. - .github/workflows/security.yml: gitleaks + govulncheck on PRs. - CLAUDE.md + docs/ARCHITECTURE.md: repo guidance + reindex. No other logic touched, no dependency bumped. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Additive (consolidation hardening): points at CLAUDE.md + ARCHITECTURE + security baseline + build/test. Existing 7KB README preserved. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The SOLSCAN_TOKEN/BIRDEYE_API_KEY scrub and the gitleaks/govulncheck CI setup this PR originally proposed were both superseded upstream by the time it rebased onto develop. Update the two doc files to describe what actually landed instead of what the original diff proposed.
tieubao
force-pushed
the
chore/harden-mochi-api
branch
from
August 27, 2026 06:25
559ffa1 to
23720b9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Console Labs consolidation hardening pass (sub-goal 05), lighter adoption.
SECURITY (action needed): pkg/config/config.go hardcoded two live third-party API keys as viper defaults in this PUBLIC repo (SOLSCAN_TOKEN, BIRDEYE_API_KEY). This PR scrubs them to "" (env-only; prod already injects via env). They are still in git history, so rotate both keys at SolScan + Birdeye. Values are not reproduced anywhere. Pre-merge: confirm prod supplies both via env. See docs/SECURITY-AUDIT-2026-06-25.md.
Also:
No other logic touched, no dependency bumped. Reviewable + reversible.