Skip to content

[OSS Tool] Fix OSS license entries: replace licenseDetail with fullLicenseText/fullLicenseTextUri#311657

Draft
vs-code-engineering[bot] wants to merge 1 commit intorelease/1.117from
oss-license-fix-1.117-20260421-1062e055e69fae98
Draft

[OSS Tool] Fix OSS license entries: replace licenseDetail with fullLicenseText/fullLicenseTextUri#311657
vs-code-engineering[bot] wants to merge 1 commit intorelease/1.117from
oss-license-fix-1.117-20260421-1062e055e69fae98

Conversation

@vs-code-engineering
Copy link
Copy Markdown
Contributor

OSS License Fixes

Fixes license errors from OSS tool run: https://github.com/microsoft/vscode-engineering/actions/runs/24718179550

The reported packages already had entries in cglicenses.json, but used the legacy licenseDetail field that the current OSS tool does not recognize. This PR updates them to use the correct fullLicenseText or fullLicenseTextUri fields.

Changes

Package Fix Type License Source Notes
@anthropic-ai/claude-agent-sdk fullLicenseText Commercial LICENSE.md No npm repo URL; resolved via homepage. Commercial license (Anthropic ToS).
@microsoft/dev-tunnels-connections fullLicenseTextUri MIT LICENSE No npm repo URL; resolved to microsoft/dev-tunnels
@microsoft/dev-tunnels-contracts fullLicenseTextUri MIT LICENSE No npm repo URL; resolved to microsoft/dev-tunnels
@microsoft/dev-tunnels-management fullLicenseTextUri MIT LICENSE No npm repo URL; resolved to microsoft/dev-tunnels
brorand fullLicenseText MIT README.md No standalone LICENSE file; license text is in README.md
emitter-listener fullLicenseText BSD-2-Clause package.json No LICENSE file in repo; copyright holder from package.json author field
bignumber.js fullLicenseTextUri MIT LICENCE.md License file uses British spelling LICENCE.md; pinned to v9.3.1 tag commit
miller-rabin fullLicenseText MIT README.md No standalone LICENSE file; license text is in README.md
randombytes fullLicenseTextUri MIT LICENSE npm URL lists crypto-browserify/randombytes but actual GitHub repo is browserify/randombytes

⚠️ Packages requiring manual resolution

The following package could not be resolved automatically. A human must add an entry to ./vscode/cglicenses.json using fullLicenseText, fullLicenseTextUri, or prependLicenseText:

Package Reason
@github/blackbird-external-ingest-utils@0.3.0 No public repository URL found in npm registry. Cannot determine copyright holder for the MIT license. Likely a private GitHub internal package.

Next steps

After merging this PR, run the OSS tool workflow to regenerate ThirdPartyNotices.txt with the updated license data.

Generated by OSS Tool License Fixer · ● 3.3M ·

…ullLicenseTextUri

Update 9 entries in cglicenses.json to use the correct fields
(fullLicenseText or fullLicenseTextUri) instead of the legacy
licenseDetail field, which the OSS tool does not recognize.

- @anthropic-ai/claude-agent-sdk: use fullLicenseText
- @microsoft/dev-tunnels-{connections,contracts,management}: use fullLicenseTextUri -> microsoft/dev-tunnels
- brorand: use fullLicenseText (license in README.md)
- emitter-listener: use fullLicenseText (no LICENSE file; BSD-2-Clause from package.json)
- bignumber.js: use fullLicenseTextUri -> MikeMcl/bignumber.js LICENCE.md at v9.3.1
- miller-rabin: use fullLicenseText (license in README.md)
- randombytes: use fullLicenseTextUri -> browserify/randombytes

Note: @github/blackbird-external-ingest-utils requires manual resolution
(no public repository URL or copyright holder found).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@vs-code-engineering vs-code-engineering Bot added the ~release-cherry-pick Trigger: cherry-pick this PR to the latest release branch label Apr 21, 2026
@vs-code-engineering
Copy link
Copy Markdown
Contributor Author

This PR will be automatically cherry-picked to main when merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

~release-cherry-pick Trigger: cherry-pick this PR to the latest release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants