Repository navigation
ci: check editor dependency licenses - #2
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Write inventory outside report cleanup and upload both audit directories. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keep bytecode instrumentation disabled and remove its unused declaration. Do not change plugin behavior or allow unknown third-party licenses. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The platform plugin supplies compiler defaults even without the tools DSL. Remove them only while instrumentation is disabled and fail on enabling it until compiler dependencies receive a new review. Keep license gates intact. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Preserve pinned upstream Apache terms and source notices for five test SDK modules. Require exact version, binary hash and test-only scope before the license gate can apply dependency-specific metadata allowances. Reject unbound allowances and exercise guard failures in CI. All other unknown metadata remains rejected. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Capture bounded UTF-8 license texts from resolved IDE distributions and exact cached POMs from resolved buildscript plugin marker components. Reject path escapes, oversized evidence and ambiguous cached metadata. Keep all remaining license failures closed pending review. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Include exact Ktav license texts in every project JAR, including generated search options. Reject SDK/tooling JVM classes, hidden archives and native payloads outside declared LSP paths in the actual plugin ZIP. Require the shared guard before verification, publication and license checks. Retain CI-only archive evidence and explicit native-audit limits. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review JBR API, Trove, metadata-only plugin markers and the verifier SDK against original sources, notices, artifact hashes and restricted scopes. Preserve all 209 SDK notice files and reject marker code, new versions, changed bytes or unbound missing-license and GPL allowances. Require a fresh actual plugin ZIP check and apply the same license gates to production build, publication and final artifact upload. Add negative guard coverage without changing project or dependency versions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Embed locked source-backed Cargo/std notices without new runtime crates or changes to LSP stdout/protocol behavior. Verify actual resource bytes after an incremental input rebuild and capture Linux executable maps. Run the published 0.8.1 source with the metadata-only hook and retain audit evidence only. Do not distribute prototype executables before non-Cargo startup/runtime terms receive their own review. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Retain the original cargo-about report and explicitly record the exact valuable source revision, package checksum and upstream MIT text. Keep graph coverage fail-closed and exercise supplement guards in CI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Preserve seven exact upstream MIT texts and their locked package and VCS identities instead of allowing cargo-about's generated MIT fallback. Keep the original tool report and record all supplements in NOTICE. Add regression guards for changed package, source and license evidence. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Check exact executable archive members and retained Scrt1 sections. Capture original startup object sections and symbols and verify that _IO_stdin_used is absent from the actual final ELF symbol tables. Keep this retained-input proof separate from source/license conclusions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Package the actual source overlay, locked vendored dependencies, target Rust link inputs, complete pinned Zig source and original GNU texts. Verify the actual source archive before rebuilding from supplied materials. Modify the supplied ARM64 startup and require its NOP at the final ELF entry while retaining the same exact embedded notice resource. Keep this audit prototype separate from production distribution. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Do not also match the suffix of __data_start when inserting the relink proof instruction. Preserve exact original source identity verification and require the modified instruction at the actual final ELF entry. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add all reviewed GNU/LLVM runtime and executable startup notices to the actual embedded bundle. Verify SDK source bytes and every original legal comment, retain complete GNU documents and distinguish architecture-specific compiled-linking permissions without weakening ARM64 source requirements. Bind the exact executable, notice and corresponding-source archive in a separate manifest, avoiding self-referential source-archive hashes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Capture platform linker maps, SDK/compiler evidence and actual binary fingerprints for the four remaining published-source targets. Preserve the existing lock and exact core source. Keep this inventory separate from distribution licensing conclusions and never upload executables. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Record the real compiler link command without changing SDK selection. Preserve original installed SDK legal documents as exact bytes and hashes for redistribution review. Keep candidate identity separate from verified selected inputs and do not infer runtime licenses from Rust metadata. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Record every candidate legal document and its size before materializing text so a size failure identifies the exact file and aggregate size. Keep the original per-document and total safety limits unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The original VS notice file is 6,167,634 bytes; the complete candidate inventory is 7,018,732 bytes. Support that real document with an 8 MiB per-file bound while retaining the 32 MiB aggregate bound and all texts. Add regression tests for the observed size and both exact boundaries. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Test an isolated official LLVM-MinGW candidate against the exact existing LSP source and lock. Pin and verify SDK integrity, capture PE imports and original runtime notices, and run the real matching-CPU tests in CI. Keep production MSVC targets, public interfaces and project versions unchanged; do not infer compatibility for other host bindings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The first successful builds still imported libunwind.dll from the SDK. Evaluate static runtime linkage, reject compiler runtime DLL imports and run a copy of the actual x64 executable from an empty directory with only Windows system directories on PATH. Keep production unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Cargo test was overwriting the shared map with its last integration-test executable. Put tests in their own target directory without the release map flag and require release binary/map hashes to remain unchanged. Keep the actual standalone executable probe and all real tests. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keep the linker reproduction outside uploaded evidence and record only input paths, sizes and SHA-256 values beside release binary/map hashes. Preserve isolated tests and the clean-PATH standalone executable probe. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Preserve exact Cargo/std notices and original MinGW, Lucent and LLVM runtime terms in the executable resource and plain sidecar. Bind the final PE CPU, embedded bytes, release map and SDK input fingerprints to the reviewed source catalogue. Keep isolated host tests and the standalone probe without compiler-runtime DLL search paths. This remains an audit-only candidate, not a production toolchain switch or proof of compatibility for the other host-language bindings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Check actual thin Mach-O CPUs and embedded Cargo/std notice bytes on both architectures. Preserve release binary/map identity across tests and reject external static SDK objects in the structural linker map. Capture undefined symbol origins and the selected iconv interface for separate system-library licensing review instead of treating system stubs as automatic proof of distribution compliance. No production target, release publication or crate version changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Classify the linker-reported public stub name separately from its resolved target. Normalize SDK directory aliases while still rejecting file aliases that escape the selected SDK and unknown public names. Record canonical targets and add positive and negative symlink guards. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Both actual LSP architectures load libiconv without importing any of its symbols. Enable dead_strip_dylibs for release and matching-CPU tests, then require only the system libSystem dependency in the final Mach-O. Keep imported-symbol evidence and reject unexpected libraries instead of inferring LGPL obligations from a library name. This changes audit-only linker flags, not protocol, public API, source versions, production release targets or other host-language bindings. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Preserve the six existing raw asset names and bind each binary to its exact embedded/compressed notice, readable package/runtime notices, original Rust copyright report, own licences and existing Cargo lock. Require the GNU ARM corresponding-source archive and its matching binary/notice/source binding in the same bounded payload. Reject omitted legal roles, changed source material, wrong executable formats and unexpected files. Exercise all six target producers and upload only verified complete payloads after their existing checks. No production release workflow, registry or store publication changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Organize all six verified platform payloads without dropping notices, own licences, Rust reports, Cargo locks or matching GNU ARM source. Rename only the executable for the existing plugin lookup paths and rebind generated metadata without changing binary/notice/source bytes. Make the verified producers reusable so the parent CI can consume all six artifacts from one run. Keep source selection immutable and apply the existing metadata hook idempotently to legacy or already-hooked source. Production publishers and stores remain unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keep Python isolation enabled and add only the trusted script directory for sibling imports. Exercise the actual isolated CLI from a separate working directory with a poisoned cwd module as a regression guard. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Share the existing distribution content invariants between filesystem and bounded ZIP readers. Require all six canonical executables, exact notices and matching GNU ARM source in actual VSIX and IntelliJ builds. Keep existing IntelliJ SDK/class/license and VSIX runtime/mode guards. Allow the larger ARM source entry only after full payload verification; retain the normal entry and total archive bounds everywhere else. Add regression coverage without publishing or changing product versions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Give each Node address-family connection attempt 2500 ms instead of 250 ms in the E2E launcher. CI failed while resolving the VS Code version with a short IPv4 timeout and unreachable IPv6, before any extension test started. Keep test assertions and execution unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Match the established license CI invocation: disable configuration on demand and parallel configuration, and request the artifact inventory. The actual IntelliJ package job could not select checkLicense while configuration on demand deferred its init-script task registration. Keep the license gate and actual distribution checks enabled. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Reuse the verified six-target producers in release builds and PR checks. Pin the selected source commit, preserve complete plugin binary trees, and require actual plugin archive checks before any publication gate. Stage raw LSP assets with their original filenames, exact legal sidecars and matching ARM source. Collect only reviewed payload and plugin artifacts instead of merging unrelated audit artifacts into releases. Upload the complete candidate inventory for dry-run inspection. Keep all existing publication opt-ins unchanged. No release, registry or store publication is performed by this commit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Clarify first-party and third-party license boundaries, complete payload redistribution, GNU ARM source/relink access and universal plugin size in English, Russian and Chinese source units. Include the exact three README files generated by canonical GitHub CI run 41049160269. Keep the product parity-check workflow unchanged; no generated Markdown was hand-edited or generated locally. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Include complete pinned Rust compiler-builtins, LLVM compiler-rt and libm originals in the LSP compiler notice resource. Preserve all existing Cargo/std, source, SDK and distribution materials. Bind the collection to the exact Rust 1.99.1 source commit and verify original file sizes, SHA256 and Git blob identities. The source witnesses form a conservative collection, not a claim that every source line survives into every target binary. Stage the materials in all three existing native producers and run fail-closed collection tests before the native build. Keep the existing plugin packaging and source/relink gates intact. No first-party license, Cargo graph, API or version changes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PHPCraftdream
marked this pull request as ready for review
November 2, 2026 12:33
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
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.
Summary
Blocked: IntelliJ dependency licensing
The Gradle license gate remains red: several JetBrains SDK and plugin-marker artifacts have no Maven license metadata, and trove4j declares LGPL-2.1 with additional CERN notices. These cannot be automatically treated as permissive; their exact provenance, usage and terms require review. The npm EULA checks do not constitute legal acceptance or a determination that all uses are permitted.
Verification
VS Code/docs and LSP license checks passed; the IntelliJ gate is intentionally fail-closed pending review. No store publication or local builds/tests were performed.
🤖 Generated with Claude Code