chore(brand): expand TRUSCA as Trusted SCA - #10
Merged
Conversation
The lockup tagline read "TrustedOSS SCA" while CHANGELOG already recorded "Trust + SCA". Settle on Trusted SCA — it reads without knowing the umbrella initiative — and rewrite the login pitch, whose Korean rendered "for the whole portfolio" literally and named no portfolio. Past release notes keep their wording.
haksungjang
force-pushed
the
brand/trusted-sca
branch
from
August 4, 2026 09:34
ff4a200 to
96b4cf3
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.
The lockup tagline said "TrustedOSS SCA" while CHANGELOG said "Trust + SCA" — two expansions for one name. Trusted SCA wins: a first-time visitor can read it without knowing the umbrella initiative, and it is what the changelog already recorded. Current surfaces (tagline, README, docs intro, docs landing, the GitHub Action and the GitLab CI template) now say it consistently. Past release notes keep their wording, since they record what was true when they shipped.
The login pitch was rewritten in the same pass. The Korean read "오픈소스 위험을 포트폴리오 단위로 봅니다" — a literal rendering of "for the whole portfolio" that named no portfolio and dropped "in one place" entirely. It now says what the product actually answers: which open source you run, and what in it is risky.
The action's
uses:path is unchanged, so existing workflows keep working; only the display name and the job-summary heading move.One follow-up: the login visual baselines still carry the old pitch string and need a CI refresh before this can go green.