# Work Repository Map
AI Summary
Purpose:
- Keep a public-safe/internal-onboarding map between Hyunwook's main work areas and the Bitbucket repositories that a successor or new teammate should inspect first.
Key points:
- This is an internal onboarding aid, not public resume copy.
- The map intentionally excludes malicious-package work because that area is still under review.
- Repository names were observed from Bitbucket workspace listing during the portfolio gap analysis on 2026-06-13.
- Use repository names as navigational hints only; exact ownership, current default branches, archived state, and deployment status should be rechecked before code work.
Relevant when:
- Building onboarding pages that explain where code lives for crawler, binlog/on-premise, data platform, or issue/document-governance work.
- Translating Jira/Confluence work history into practical code navigation.
Do not read full document unless:
- You need the repo grouping table or public-safety notes.
Linked documents:
crawler-collection-count-log.md../projects/labrador-platform.md../projects/bts.md
Open Questions
- Needs confirmation: exact current maintainer and archived/replaced status for each repo before assigning follow-up work.
- Needs confirmation: whether some repository names should be hidden from broader internal presentation.
Details
Repo groups
| Work area | Repositories to inspect first | Notes |
|---|---|---|
| Library crawler family | crawler-lib-java, crawler-lib-golang, crawler-lib-php, crawler-lib-ruby, crawler-lib-swift, crawler-lib-dotnet | Main ecosystem crawler code families. Use with crawler modernization and collection-count log onboarding pages. |
| Crawler operation / diagnostics | data_check_script, oss-buildserver | Useful around collection validation, build/runtime support, and ad-hoc diagnosis. Confirm current usage before editing. |
| Binlog / on-premise delivery | logwatcher, onpremiseinstaller | Relevant to on-premise DB delivery, log collection, deployment packaging, and customer-environment support. |
| Vulnerability/data API surface | cdbvdbapi, lab2backend, labscan3, vulnerability-alarm | API/product-side surfaces tied to vulnerability data and analysis operations. Some older repos may have been replaced by nested or newer service repos. |
| Analysis / product-adjacent security | bsca-analysis | Relevant to binary or SBOM/component-analysis work; verify sensitive details before public use. |
Public-safety rule
- Public portfolio pages should describe the work by problem and technical approach, not expose internal repository names.
- Internal onboarding pages may list repository names when the purpose is practical handoff.
- Customer names, issue keys, credentials, private URLs, and sensitive package/security details should not be copied into public-facing pages.
Excluded for now
- Malicious package collection/analysis repositories and issue details are intentionally excluded from this map update because the work is still under review.