chore: exclude website/ docusaurus tree from FOSSA license scan#5472
Conversation
The Docusaurus dev-server stack (webpack-dev-server → selfsigned → node-forge) pulls a `(BSD-3-Clause OR GPL-2.0)` dual SPDX expression that the org license policy flags as GPL-2.0 (and triggers a GPL-1.0 text-scanner finding from the same LICENSE file). FOSSA has been failing the License Compliance check on master since #5443's dependabot bump re-resolved node-forge to 1.4.0. node-forge is build-time only for serving the docs site locally; it is not distributed via the Wails Go module or @wailsio/runtime, so excluding website/ from FOSSA's npm target scan keeps the compliance posture focused on what users actually consume.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe ChangesFOSSA npm license scanning exclusion
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Adds a FOSSA v3 configuration file to exclude the website/ (Docusaurus docs site) npm dependency tree from FOSSA license scanning, so license compliance findings from build-time-only transitive dependencies don’t gate merges.
Changes:
- Introduces
.fossa.ymlusing the v3 schema. - Excludes the
website/npm target from FOSSA scanning viatargets.exclude.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
Resolves the 3 FOSSA License Compliance findings currently red on every master commit since #5443.
All three findings trace to a single package:
node-forge@1.4.0, pulled in only at depth-4 by Docusaurus's dev-server stack:node-forge declares
(BSD-3-Clause OR GPL-2.0). FOSSA's default policy flags the GPL branch of anyORexpression unless an explicit election is recorded, and its text-scanner reports both GPL-1.0 and GPL-2.0 from the bundled LICENSE file — same package, 3 findings.Why exclude rather than elect
.fossa.yml(v3 schema) has no per-dependency license-election syntax — that lives in FOSSA's web UI under a paid SKU. The available YAML mechanisms are path/target exclusion.node-forge is build-time only for serving the docs site locally; it is not distributed with the Wails Go module or
@wailsio/runtime. Scoping FOSSA out ofwebsite/keeps the compliance posture focused on what wails users actually consume.Narrow exclusion (
website/only) —docs/andscripts/sponsors/also carry LGPLsharptransitives but those aren't currently flagging, so they're left in scope.Test plan
Summary by CodeRabbit