{"$schema":"https://json.schemastore.org/sarif-2.1.0.json","version":"2.1.0","runs":[{"tool":{"driver":{"name":"codehealth","informationUri":"https://codehealth.canine.dev","rules":[{"id":"D1","name":"Cyclomatic Complexity","shortDescription":{"text":"Cyclomatic Complexity"},"helpUri":"https://codehealth.canine.dev/dimensions/D1"},{"id":"D2","name":"Cognitive Complexity","shortDescription":{"text":"Cognitive Complexity"},"helpUri":"https://codehealth.canine.dev/dimensions/D2"},{"id":"D3","name":"God Classes","shortDescription":{"text":"God Classes"},"helpUri":"https://codehealth.canine.dev/dimensions/D3"},{"id":"D4","name":"Code Duplication","shortDescription":{"text":"Code Duplication"},"helpUri":"https://codehealth.canine.dev/dimensions/D4"},{"id":"D5","name":"Coupling","shortDescription":{"text":"Coupling"},"helpUri":"https://codehealth.canine.dev/dimensions/D5"},{"id":"D8","name":"Code Coverage","shortDescription":{"text":"Code Coverage"},"helpUri":"https://codehealth.canine.dev/dimensions/D8"},{"id":"D9","name":"Test Distribution","shortDescription":{"text":"Test Distribution"},"helpUri":"https://codehealth.canine.dev/dimensions/D9"},{"id":"D12","name":"Dependency Hygiene","shortDescription":{"text":"Dependency Hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/D12"},{"id":"D13","name":"Secret Scanning","shortDescription":{"text":"Secret Scanning"},"helpUri":"https://codehealth.canine.dev/dimensions/D13","relationships":[{"target":{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A07:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-798","CWE-259"],"owasp":"A07:2025"}},{"id":"D14","name":"License Compliance","shortDescription":{"text":"License Compliance"},"helpUri":"https://codehealth.canine.dev/dimensions/D14"},{"id":"D15","name":"Churn \u00D7 Complexity Hotspots","shortDescription":{"text":"Churn \u00D7 Complexity Hotspots"},"helpUri":"https://codehealth.canine.dev/dimensions/D15"},{"id":"D17","name":"Explicit Debt","shortDescription":{"text":"Explicit Debt"},"helpUri":"https://codehealth.canine.dev/dimensions/D17"},{"id":"D18","name":"Solution Shape","shortDescription":{"text":"Solution Shape"},"helpUri":"https://codehealth.canine.dev/dimensions/D18"},{"id":"D19","name":"Documentation Quality","shortDescription":{"text":"Documentation Quality"},"helpUri":"https://codehealth.canine.dev/dimensions/D19"},{"id":"D26","name":"Project Cohesion","shortDescription":{"text":"Project Cohesion"},"helpUri":"https://codehealth.canine.dev/dimensions/D26"},{"id":"D27","name":"Navigability","shortDescription":{"text":"Navigability"},"helpUri":"https://codehealth.canine.dev/dimensions/D27"},{"id":"D28","name":"Secrets (history)","shortDescription":{"text":"Secrets (history)"},"helpUri":"https://codehealth.canine.dev/dimensions/D28","relationships":[{"target":{"id":"CWE-798","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A07:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-798","CWE-259"],"owasp":"A07:2025"}},{"id":"D29","name":"Static Analysis (SAST)","shortDescription":{"text":"Static Analysis (SAST)"},"helpUri":"https://codehealth.canine.dev/dimensions/D29","relationships":[{"target":{"id":"CWE-79","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-89","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-78","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-94","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-77","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A05:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-79","CWE-89","CWE-78","CWE-94","CWE-77"],"owasp":"A05:2025"}},{"id":"D30","name":"Dependency Vulnerabilities","shortDescription":{"text":"Dependency Vulnerabilities"},"helpUri":"https://codehealth.canine.dev/dimensions/D30","relationships":[{"target":{"id":"CWE-1395","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-937","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-1395","CWE-937"],"owasp":"A03:2025"}},{"id":"D31","name":"IaC \u0026 Container Security","shortDescription":{"text":"IaC \u0026 Container Security"},"helpUri":"https://codehealth.canine.dev/dimensions/D31","relationships":[{"target":{"id":"CWE-1032","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-732","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"CWE-16","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A02:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-1032","CWE-732","CWE-16"],"owasp":"A02:2025"}},{"id":"D35","name":"Change Coupling","shortDescription":{"text":"Change Coupling"},"helpUri":"https://codehealth.canine.dev/dimensions/D35"},{"id":"D39","name":"IL Efficiency","shortDescription":{"text":"IL Efficiency"},"helpUri":"https://codehealth.canine.dev/dimensions/D39"},{"id":"D40","name":"Network Egress Confinement","shortDescription":{"text":"Network Egress Confinement"},"helpUri":"https://codehealth.canine.dev/dimensions/D40"},{"id":"D41","name":"Kernel \u0026 Syscall Confinement","shortDescription":{"text":"Kernel \u0026 Syscall Confinement"},"helpUri":"https://codehealth.canine.dev/dimensions/D41"},{"id":"D43","name":"Malicious Dependencies","shortDescription":{"text":"Malicious Dependencies"},"helpUri":"https://codehealth.canine.dev/dimensions/D43","relationships":[{"target":{"id":"CWE-506","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},"kinds":["relevant"]},{"target":{"id":"A08:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},"kinds":["relevant"]}],"properties":{"cwe":["CWE-506"],"owasp":"A08:2025"}},{"id":"D44","name":"Platform End-of-Life","shortDescription":{"text":"Platform End-of-Life"},"helpUri":"https://codehealth.canine.dev/dimensions/D44"},{"id":"AX10","name":"Code composition","shortDescription":{"text":"Code composition"},"helpUri":"https://codehealth.canine.dev/dimensions/AX10"},{"id":"AX3","name":"Project dependency cycles","shortDescription":{"text":"Project dependency cycles"},"helpUri":"https://codehealth.canine.dev/dimensions/AX3"},{"id":"AX4","name":"Dependency direction","shortDescription":{"text":"Dependency direction"},"helpUri":"https://codehealth.canine.dev/dimensions/AX4"},{"id":"AX5","name":"Architecture \u0026 structure","shortDescription":{"text":"Architecture \u0026 structure"},"helpUri":"https://codehealth.canine.dev/dimensions/AX5"},{"id":"AXB2","name":"Runtime readiness","shortDescription":{"text":"Runtime readiness"},"helpUri":"https://codehealth.canine.dev/dimensions/AXB2"},{"id":"AXR1","name":"Runtime accessibility","shortDescription":{"text":"Runtime accessibility"},"helpUri":"https://codehealth.canine.dev/dimensions/AXR1"},{"id":"AXS1","name":"Runtime exposed surface","shortDescription":{"text":"Runtime exposed surface"},"helpUri":"https://codehealth.canine.dev/dimensions/AXS1"},{"id":"ED5","name":"Idempotency","shortDescription":{"text":"Idempotency"},"helpUri":"https://codehealth.canine.dev/dimensions/ED5"},{"id":"GD1","name":"Unfinished \u0026 placeholder code","shortDescription":{"text":"Unfinished \u0026 placeholder code"},"helpUri":"https://codehealth.canine.dev/dimensions/GD1"},{"id":"M1","name":"Documentation (README)","shortDescription":{"text":"Documentation (README)"},"helpUri":"https://codehealth.canine.dev/dimensions/M1"},{"id":"M2","name":"Architecture documentation","shortDescription":{"text":"Architecture documentation"},"helpUri":"https://codehealth.canine.dev/dimensions/M2"},{"id":"M3","name":"Folder \u0026 project structure","shortDescription":{"text":"Folder \u0026 project structure"},"helpUri":"https://codehealth.canine.dev/dimensions/M3"},{"id":"M4","name":"Documentation accuracy","shortDescription":{"text":"Documentation accuracy"},"helpUri":"https://codehealth.canine.dev/dimensions/M4"},{"id":"P1","name":"CI/CD gates","shortDescription":{"text":"CI/CD gates"},"helpUri":"https://codehealth.canine.dev/dimensions/P1"},{"id":"P10","name":"Library API \u0026 versioning","shortDescription":{"text":"Library API \u0026 versioning"},"helpUri":"https://codehealth.canine.dev/dimensions/P10"},{"id":"P12","name":"CI test-gate honesty","shortDescription":{"text":"CI test-gate honesty"},"helpUri":"https://codehealth.canine.dev/dimensions/P12"},{"id":"P2","name":"Observability","shortDescription":{"text":"Observability"},"helpUri":"https://codehealth.canine.dev/dimensions/P2"},{"id":"P4","name":"Deployment \u0026 Rollback","shortDescription":{"text":"Deployment \u0026 Rollback"},"helpUri":"https://codehealth.canine.dev/dimensions/P4"},{"id":"P6","name":"Release Hygiene","shortDescription":{"text":"Release Hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/P6"},{"id":"P7","name":"Outbound HTTP resilience","shortDescription":{"text":"Outbound HTTP resilience"},"helpUri":"https://codehealth.canine.dev/dimensions/P7"},{"id":"PF1","name":"Benchmark discipline","shortDescription":{"text":"Benchmark discipline"},"helpUri":"https://codehealth.canine.dev/dimensions/PF1"},{"id":"PF3","name":"Async \u0026 latency hygiene","shortDescription":{"text":"Async \u0026 latency hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/PF3"},{"id":"S1","name":"Web-Security Posture","shortDescription":{"text":"Web-Security Posture"},"helpUri":"https://codehealth.canine.dev/dimensions/S1"},{"id":"SC1","name":"Supply-chain hygiene","shortDescription":{"text":"Supply-chain hygiene"},"helpUri":"https://codehealth.canine.dev/dimensions/SC1"},{"id":"X1","name":"Async correctness","shortDescription":{"text":"Async correctness"},"helpUri":"https://codehealth.canine.dev/dimensions/X1"},{"id":"X10","name":"Duplicated predicate","shortDescription":{"text":"Duplicated predicate"},"helpUri":"https://codehealth.canine.dev/dimensions/X10"},{"id":"X12","name":"Unreachable branch","shortDescription":{"text":"Unreachable branch"},"helpUri":"https://codehealth.canine.dev/dimensions/X12"},{"id":"X13","name":"Undrained process stream","shortDescription":{"text":"Undrained process stream"},"helpUri":"https://codehealth.canine.dev/dimensions/X13"},{"id":"X14","name":"Bypassable address classification","shortDescription":{"text":"Bypassable address classification"},"helpUri":"https://codehealth.canine.dev/dimensions/X14"},{"id":"X15","name":"Unvalidated length from an untrusted reader","shortDescription":{"text":"Unvalidated length from an untrusted reader"},"helpUri":"https://codehealth.canine.dev/dimensions/X15"},{"id":"X16","name":"Unfloored truncation loop","shortDescription":{"text":"Unfloored truncation loop"},"helpUri":"https://codehealth.canine.dev/dimensions/X16"},{"id":"X17","name":"Uncapped recursion over a caller-supplied document","shortDescription":{"text":"Uncapped recursion over a caller-supplied document"},"helpUri":"https://codehealth.canine.dev/dimensions/X17"},{"id":"X18","name":"Disposal-pattern correctness","shortDescription":{"text":"Disposal-pattern correctness"},"helpUri":"https://codehealth.canine.dev/dimensions/X18"},{"id":"X19","name":"Unrestored process-global state","shortDescription":{"text":"Unrestored process-global state"},"helpUri":"https://codehealth.canine.dev/dimensions/X19"},{"id":"X20","name":"Mistyped argument guard","shortDescription":{"text":"Mistyped argument guard"},"helpUri":"https://codehealth.canine.dev/dimensions/X20"},{"id":"X21","name":"Side-effecting pattern guard","shortDescription":{"text":"Side-effecting pattern guard"},"helpUri":"https://codehealth.canine.dev/dimensions/X21"},{"id":"X22","name":"Contradicted release guard","shortDescription":{"text":"Contradicted release guard"},"helpUri":"https://codehealth.canine.dev/dimensions/X22"},{"id":"X23","name":"Unguarded diagnostic materialisation","shortDescription":{"text":"Unguarded diagnostic materialisation"},"helpUri":"https://codehealth.canine.dev/dimensions/X23"},{"id":"X24","name":"Document value interpolated into markup unescaped","shortDescription":{"text":"Document value interpolated into markup unescaped"},"helpUri":"https://codehealth.canine.dev/dimensions/X24"},{"id":"X25","name":"Inert configuration knob","shortDescription":{"text":"Inert configuration knob"},"helpUri":"https://codehealth.canine.dev/dimensions/X25"},{"id":"X26","name":"Unsynchronised callback handoff","shortDescription":{"text":"Unsynchronised callback handoff"},"helpUri":"https://codehealth.canine.dev/dimensions/X26"},{"id":"X27","name":"Collection changed while being enumerated","shortDescription":{"text":"Collection changed while being enumerated"},"helpUri":"https://codehealth.canine.dev/dimensions/X27"},{"id":"X28","name":"Index access outside its own emptiness guard","shortDescription":{"text":"Index access outside its own emptiness guard"},"helpUri":"https://codehealth.canine.dev/dimensions/X28"},{"id":"X29","name":"Per-element action decided by a fixed element","shortDescription":{"text":"Per-element action decided by a fixed element"},"helpUri":"https://codehealth.canine.dev/dimensions/X29"},{"id":"X3","name":"Exception handling","shortDescription":{"text":"Exception handling"},"helpUri":"https://codehealth.canine.dev/dimensions/X3"},{"id":"X30","name":"Support guard that admits what it rejects","shortDescription":{"text":"Support guard that admits what it rejects"},"helpUri":"https://codehealth.canine.dev/dimensions/X30"},{"id":"X32","name":"Type resolved by simple name across every loaded assembly","shortDescription":{"text":"Type resolved by simple name across every loaded assembly"},"helpUri":"https://codehealth.canine.dev/dimensions/X32"},{"id":"X4","name":"Structured logging","shortDescription":{"text":"Structured logging"},"helpUri":"https://codehealth.canine.dev/dimensions/X4"},{"id":"X5","name":"Nullable reference types","shortDescription":{"text":"Nullable reference types"},"helpUri":"https://codehealth.canine.dev/dimensions/X5"},{"id":"X6","name":"Hand-rolled structured-format parsing","shortDescription":{"text":"Hand-rolled structured-format parsing"},"helpUri":"https://codehealth.canine.dev/dimensions/X6"},{"id":"X7","name":"Silent fallback defaults","shortDescription":{"text":"Silent fallback defaults"},"helpUri":"https://codehealth.canine.dev/dimensions/X7"},{"id":"X9","name":"Subsumed condition operand","shortDescription":{"text":"Subsumed condition operand"},"helpUri":"https://codehealth.canine.dev/dimensions/X9"}]}},"results":[{"ruleId":"D8","level":"note","message":{"text":"No tests \u2014 template/sample: This repo declares itself a template / kata / sample; tests are deferred to the application built from it, so coverage is not scored here."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"e5ca94717741d80f619caad143078fae4342c89e6107210846d2f8d1d28343db"}},{"ruleId":"D9","level":"note","message":{"text":"No tests found: No test suite could be collected \u2014 no discoverable tests to count. If this repository does test, wiring the suite to a framework a runner can collect (xUnit, NUnit or MSTest) is what makes it countable here; a pipeline step that invokes a runner is not evidence on its own, because a runner over an empty suite passes. Tests written as plain executables or shell/PowerShell harnesses are not collectible this way and are not scored here."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"c9bf64cbb5a4ae13d6bcd01fa3bc8d2879d860c73bc67f176ee3c2cecb8adce3"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.AspNetCore.Serilog: \u0060Volo.Abp.AspNetCore.Serilog\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.API/IngosAbpTemplate.API.csproj"},"region":{"startLine":36}}}],"partialFingerprints":{"codehealthFindingId/v1":"56ce9b2b5b3c85efec8d1baec2773ff150704cde7255698e155a36ced6271f44"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.AuditLogging.Domain: \u0060Volo.Abp.AuditLogging.Domain\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Domain/IngosAbpTemplate.Domain.csproj"},"region":{"startLine":12}}}],"partialFingerprints":{"codehealthFindingId/v1":"4cef092d2f1ee611c950cca39d35968dac398fb7812b303ebb0cfc86f0e69448"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.AuditLogging.Domain.Shared: \u0060Volo.Abp.AuditLogging.Domain.Shared\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Domain.Shared/IngosAbpTemplate.Domain.Shared.csproj"},"region":{"startLine":11}}}],"partialFingerprints":{"codehealthFindingId/v1":"9a486872b2e92084da49e2b264f74ff3bcfcaffeefd4065d86991c5285010e3c"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.AuditLogging.EntityFrameworkCore: \u0060Volo.Abp.AuditLogging.EntityFrameworkCore\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Infrastructure/IngosAbpTemplate.Infrastructure.csproj"},"region":{"startLine":14}}}],"partialFingerprints":{"codehealthFindingId/v1":"43d28ae9b76c810b4743082662fa27d84b1f9a3d069637a1e5c22cbab621622a"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Autofac: \u0060Volo.Abp.Autofac\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.API/IngosAbpTemplate.API.csproj"},"region":{"startLine":34}}}],"partialFingerprints":{"codehealthFindingId/v1":"f7850df8d2f215b45e2e1d5e78a8d75e5b87eb9fb9eba0558ff572849d20d953"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.BackgroundJobs.Domain: \u0060Volo.Abp.BackgroundJobs.Domain\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Domain/IngosAbpTemplate.Domain.csproj"},"region":{"startLine":11}}}],"partialFingerprints":{"codehealthFindingId/v1":"da6f00538c20b2f305763329a2d84d258dd948107b1a0b99719fa43e66723801"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.BackgroundJobs.Domain.Shared: \u0060Volo.Abp.BackgroundJobs.Domain.Shared\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Domain.Shared/IngosAbpTemplate.Domain.Shared.csproj"},"region":{"startLine":10}}}],"partialFingerprints":{"codehealthFindingId/v1":"849d3b68a47d785e2e2fff1f37d8a38b0e385cb63488b79f41d0292a3af6cb3c"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.BackgroundJobs.EntityFrameworkCore: \u0060Volo.Abp.BackgroundJobs.EntityFrameworkCore\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Infrastructure/IngosAbpTemplate.Infrastructure.csproj"},"region":{"startLine":13}}}],"partialFingerprints":{"codehealthFindingId/v1":"38d3b13c4d2641d8715cf5806ec7606a9c315f5420a5617f571cc62c00ba4e31"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Caching.StackExchangeRedis: \u0060Volo.Abp.Caching.StackExchangeRedis\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.API/IngosAbpTemplate.API.csproj"},"region":{"startLine":35}}}],"partialFingerprints":{"codehealthFindingId/v1":"354012aed476c5d0daeefc09b2c1c03efcc2d3a0550046bdddc1f7fc609f8195"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Ddd.Application: \u0060Volo.Abp.Ddd.Application\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Application/IngosAbpTemplate.Application.csproj"},"region":{"startLine":19}}}],"partialFingerprints":{"codehealthFindingId/v1":"69bb6015d51f9be1d828c1d0dc264b4a05a69692c8c437aa0e58133c0e51ec8c"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Ddd.Application.Contracts: \u0060Volo.Abp.Ddd.Application.Contracts\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Application.Contracts/IngosAbpTemplate.Application.Contracts.csproj"},"region":{"startLine":17}}}],"partialFingerprints":{"codehealthFindingId/v1":"5289c1891bf3aea4ee65ea6a5766edabb1235e5220109800045d7a7037cc0431"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Emailing: \u0060Volo.Abp.Emailing\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Domain/IngosAbpTemplate.Domain.csproj"},"region":{"startLine":10}}}],"partialFingerprints":{"codehealthFindingId/v1":"08632b9cab372ab3af8f6814c1f9b83d45987517185b356b5b86c486ab366a20"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.EntityFrameworkCore.MySQL: \u0060Volo.Abp.EntityFrameworkCore.MySQL\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Infrastructure/IngosAbpTemplate.Infrastructure.csproj"},"region":{"startLine":15}}}],"partialFingerprints":{"codehealthFindingId/v1":"5bb5fbf606eeb24624f1ad7623b51b360415467734b20c083bc18865ca22ca52"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.EntityFrameworkCore.PostgreSql: \u0060Volo.Abp.EntityFrameworkCore.PostgreSql\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Infrastructure/IngosAbpTemplate.Infrastructure.csproj"},"region":{"startLine":17}}}],"partialFingerprints":{"codehealthFindingId/v1":"191dc32531885d7f5b8ed6a6a6fa850866a8c94c4f59ba62f3ce353a6857f2b9"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.EntityFrameworkCore.SqlServer: \u0060Volo.Abp.EntityFrameworkCore.SqlServer\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Infrastructure/IngosAbpTemplate.Infrastructure.csproj"},"region":{"startLine":16}}}],"partialFingerprints":{"codehealthFindingId/v1":"7ba262204d2fca4911017157a7ba82ce06db76fd6b87edf40df982a59fddd680"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.ObjectExtending: \u0060Volo.Abp.ObjectExtending\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Application.Contracts/IngosAbpTemplate.Application.Contracts.csproj"},"region":{"startLine":18}}}],"partialFingerprints":{"codehealthFindingId/v1":"afb61263e10b091d07a3c748475a4b2116794baf1caf40ff479dc8a10f9c3a3c"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.PermissionManagement.Application: \u0060Volo.Abp.PermissionManagement.Application\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Application/IngosAbpTemplate.Application.csproj"},"region":{"startLine":20}}}],"partialFingerprints":{"codehealthFindingId/v1":"8aba22c190583af32817ae9e6fe517eec610fcc32f77c3ae0cceaacb8a77682f"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.PermissionManagement.Application.Contracts: \u0060Volo.Abp.PermissionManagement.Application.Contracts\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Application.Contracts/IngosAbpTemplate.Application.Contracts.csproj"},"region":{"startLine":19}}}],"partialFingerprints":{"codehealthFindingId/v1":"9d0f38d9340d53b5f39aa9cdd4f565ad0fd5525b87f2709ba54cd4e7d44863ba"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.PermissionManagement.Domain: \u0060Volo.Abp.PermissionManagement.Domain\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Domain/IngosAbpTemplate.Domain.csproj"},"region":{"startLine":13}}}],"partialFingerprints":{"codehealthFindingId/v1":"a8f8f0098a4dd742ae696699d2df31d82a31859c06e632a7ca737c53369f7f3b"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.PermissionManagement.Domain.Shared: \u0060Volo.Abp.PermissionManagement.Domain.Shared\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Domain.Shared/IngosAbpTemplate.Domain.Shared.csproj"},"region":{"startLine":21}}}],"partialFingerprints":{"codehealthFindingId/v1":"a9d37328b640f9937f044bb513d4ca11313e336e36da56dde599367bdca853fe"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.PermissionManagement.EntityFrameworkCore: \u0060Volo.Abp.PermissionManagement.EntityFrameworkCore\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Infrastructure/IngosAbpTemplate.Infrastructure.csproj"},"region":{"startLine":18}}}],"partialFingerprints":{"codehealthFindingId/v1":"e0d78819be26b26fadf58682f1b871f3037ac0ce5f953018e5cf6298ddbcd304"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.PermissionManagement.HttpApi: \u0060Volo.Abp.PermissionManagement.HttpApi\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.API/IngosAbpTemplate.API.csproj"},"region":{"startLine":37}}}],"partialFingerprints":{"codehealthFindingId/v1":"618f0c59e6a67993fd0d3c121953fc3fc4042c7204e38ea0cebe842195378f2e"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Swashbuckle: \u0060Volo.Abp.Swashbuckle\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.API/IngosAbpTemplate.API.csproj"},"region":{"startLine":38}}}],"partialFingerprints":{"codehealthFindingId/v1":"e7b24320bfa3b8aa5dfe5d7ba4203d9ce33005b424aa923e940f451f84c32d1e"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Validation: \u0060Volo.Abp.Validation\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Domain.Shared/IngosAbpTemplate.Domain.Shared.csproj"},"region":{"startLine":22}}}],"partialFingerprints":{"codehealthFindingId/v1":"bfbf2b0a75034648f6e447ec09e8570fa9565a92aad2202696143bdf04ea43d4"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.AspNetCore: \u0060Volo.Abp.AspNetCore\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"05c1c97e8e4210ab1afc57feeb383daad7f42ab9da42ad041d1fab50573865a6"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.MultiTenancy: \u0060Volo.Abp.MultiTenancy\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"f8f8f071a87171edf934508534f1b1098c549efbc3c7bdc73b1872c6a0797a0c"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Auditing: \u0060Volo.Abp.Auditing\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"2f63c1616f95953f9b00850dd65725323c74a463e11ba5fee0958ac14bc6c91d"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Ddd.Domain: \u0060Volo.Abp.Ddd.Domain\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"b36a9b2519554317b6a136142d3deb0b4493194ad234c22a4f082a72899b6a2e"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Localization: \u0060Volo.Abp.Localization\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"e99617936f725a46350d030146a4c8b0f6b562902976dac6600a30f534155f49"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.EntityFrameworkCore: \u0060Volo.Abp.EntityFrameworkCore\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"b912287e39299b96dfb9230ec69b3b3b3c3b09d3f8c8e1952535d7f80b5903cd"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Castle.Core: \u0060Volo.Abp.Castle.Core\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"51c2fc987e190ef4f87c6de103ec9852affddfef0eb1b3d81c197a4f053d0122"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.AutoMapper: \u0060Volo.Abp.AutoMapper\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"5eae36a1feb8e7fd85a839fa29578ea03aad9e2f7c55332f42ddbcad8f19e6ef"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.BackgroundJobs: \u0060Volo.Abp.BackgroundJobs\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"dd045d73dfd02b979c9ff680aeea098de689b6dee205bc22833c1a6cbf4f9f40"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Core: \u0060Volo.Abp.Core\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"04ea75ac56aa762b861e4765f9eda2d5d4c90f0923787863f9436741fdab3981"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Caching: \u0060Volo.Abp.Caching\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"3fe42cb05802d9c71d39355dfbcf5d30d2c7782bd6280af77d8bb7888d015176"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Authorization: \u0060Volo.Abp.Authorization\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"c2d17183f22318aa31ba132e140df8a728eab02824ac1a638c578e4034a61a3c"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Features: \u0060Volo.Abp.Features\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"56ca97ded105f335c558dbba29a2af30b45055b5eb927e854f183f30594edad0"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.GlobalFeatures: \u0060Volo.Abp.GlobalFeatures\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"85f4899c7899cfd6e3d153d6f0e1115a6ffd26ddfa3ffe5e24cfdfdf79aa86f2"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Http.Abstractions: \u0060Volo.Abp.Http.Abstractions\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"6a8ba34fd75265c80c23818cf25df6c230f555468e5fb962245ce6bdecc0e8a4"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.ObjectMapping: \u0060Volo.Abp.ObjectMapping\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"e96f987ae2164a34572ec482213be178e7ce979d370d33b63cc1d345f7687861"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Security: \u0060Volo.Abp.Security\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"fc14dece880025f46cbe2b603b74ba8082e54822b5e678797f3716e85c25adc2"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Settings: \u0060Volo.Abp.Settings\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"bbc45429116e51930d815d50f1dbe789e48d2ce556073c5179bebd658bfb894f"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.BackgroundJobs.Abstractions: \u0060Volo.Abp.BackgroundJobs.Abstractions\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"a132e19182536ba509001ce0a5643b0d77a4a9a2ca9232183c1cf211912097e9"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.TextTemplating: \u0060Volo.Abp.TextTemplating\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"aea793269e77f904ec77b5ca6377203abd925dc386fe95b4c811e58624f5c14b"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.VirtualFileSystem: \u0060Volo.Abp.VirtualFileSystem\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"8db78afddae234fb489fdd76914fadc82be19ba26e566324fbf88d943fe8117d"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Localization.Abstractions: \u0060Volo.Abp.Localization.Abstractions\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"e3a0bae980d1a32b4c559a16c6145a61f7067d49f8394158976a91b346f5bcb0"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Validation.Abstractions: \u0060Volo.Abp.Validation.Abstractions\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"b980c233f5ed84720942f48e50a586de5351882ac5a4b1fb390ce65361e4c6a8"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Authorization.Abstractions: \u0060Volo.Abp.Authorization.Abstractions\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"0ca1c2066eef4c1e24bd0d74f4124ba4aa81cfd8e36988a4bea8e2c17b717a6f"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Json: \u0060Volo.Abp.Json\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"aa2225776c7a32e5af2d5251d047b392724496103a086263ef4f627c603d0f55"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.AspNetCore.Mvc: \u0060Volo.Abp.AspNetCore.Mvc\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"8b726371fb0ca0e69629cf1d2dfa7cd2fbb6f78fce1449466227c9d298feb9c4"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.ExceptionHandling: \u0060Volo.Abp.ExceptionHandling\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"b6f2153c607f41e22f67776cf36017064de33e0af976c7bd3b9a2cb5925e4b31"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Http: \u0060Volo.Abp.Http\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"6ed99dd43ddc6c48ac4c31fd7f1a450d850ba674c770aa8ac821a307bc56dedb"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Uow: \u0060Volo.Abp.Uow\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"fc1f5cf82f7c0ccadbb9a634c685bc79e62c26e5bab4de83b3d51149d96c9c0c"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Data: \u0060Volo.Abp.Data\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"bf7b4b2a14e910668d6e40bfd057773abb2c84ce1535397b3a40cad0810b9689"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.EventBus.Abstractions: \u0060Volo.Abp.EventBus.Abstractions\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"fec00d9f6739beb94ada52f8d448de8ef38d61a5df3368143179196473b53197"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Threading: \u0060Volo.Abp.Threading\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"b034a1843ff7b04b58b83ee1cd89c92e3f3945cee214d960fa20433b315f1de4"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Timing: \u0060Volo.Abp.Timing\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"618785ee1f3d4c160b57baeacc9a353d7fbdfff21e6485922dca80bd8765e85f"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.EventBus: \u0060Volo.Abp.EventBus\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"527b004e42f890e9e785f26c9bfc28aaa1ca710febf4f6359a21a54a48749721"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Guids: \u0060Volo.Abp.Guids\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"25c6597a1bb572997888997c2cd1daf0cbe75c64431a0423cb3bf99cf66848a2"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Specifications: \u0060Volo.Abp.Specifications\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"38030caa560629557e21a2f115d929cac6695c469083280211a0337288cb5317"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.BackgroundWorkers: \u0060Volo.Abp.BackgroundWorkers\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"be5f2f987181aa040057bb7e8a05c8d413ba4dbb3c37b549cb08e74de74b7818"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.Serialization: \u0060Volo.Abp.Serialization\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"2fd9a748efb7da1a34e84e75266b1a292f0c877893d653850725fd5df0f09dc9"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.TextTemplating.Scriban: \u0060Volo.Abp.TextTemplating.Scriban\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"b5d2967fba5da009736ecc51ed324a096190d470b439dcd18255410e2896679f"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.ApiVersioning.Abstractions: \u0060Volo.Abp.ApiVersioning.Abstractions\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"0a0b18401d85db64219c5ff694ab26e2642269da74ea409f727258d8e23a16f7"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.AspNetCore.Mvc.Contracts: \u0060Volo.Abp.AspNetCore.Mvc.Contracts\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"5d4cc32e09ff65766fd0806a86822e5049a960aea73d2488a9f0215668066e58"}},{"ruleId":"D14","level":"error","message":{"text":"Banned license: Volo.Abp.UI.Navigation: \u0060Volo.Abp.UI.Navigation\u0060 4.4.3 resolves to SPDX id LGPL-3.0-only, and this run\u0027s banned set is AGPL-3.0, GPL-2.0, GPL-3.0, LGPL-3.0. The id is read as an SPDX expression: an \u0060OR\u0060 is a choice and is charged only when every branch is banned, an \u0060AND\u0060 binds every operand, and a \u0060WITH\u0060 exception leaves the licence it attaches to as it is. Each licence id is then matched as a SUBSTRING that starts at a token boundary, not an exact comparison \u2014 which is how variants like \u0060-only\u0060 and \u0060-or-later\u0060 are caught while \u0060LGPL-2.0-only\u0060 is not read as \u0060GPL-2.0\u0060, and it is the rule to apply if you re-check this by hand. The set is policy, not law: it is configurable, so a licence banned here may be acceptable in your context, and the row is then something to record an exception for rather than to fix. \u2605 This arm reads the resolved package list and knows nothing about dependency SCOPE \u2014 it cannot tell a runtime dependency from a build- or test-only one, so unlike the Bundler arm it is NOT claiming this ships to your users. Check where it sits before acting. \u2605 DEPTH: this repository\u0027s MSBuild projects declare 36 direct \u0060PackageReference\u0060(s), and 214 further package(s) were reached beyond them by closing the graph over nuget.org\u0027s own nuspec dependency graph \u2014 so a banned licence pulled in only by a dependency\u0027s OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer\u0027s exact resolution. \u2605 The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do \u2014 that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository\u0027s licence policy rather than replacing it: add \u0060LGPL-3.0-only\u0060 / \u0060LGPL-3.0-or-later\u0060 to the allow-list of the licence check your CI runs (\u0060license-checker --onlyAllow\u0060, the \u0060allow-licenses\u0060 input of GitHub\u0027s dependency-review-action, \u0060[licenses] allow\u0060 in cargo-deny\u0027s deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan\u0027s banned set is not read from that file, so the row stays until it is hidden."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"f6cf09f00a5c55c76a69aacd1950235921840a889756e7e07016bb3e3f138e90"}},{"ruleId":"D17","level":"error","message":{"text":"NoWarnInCsproj: NU5128 \u2014 this warning is switched off for the WHOLE project, including builds years from now. It is raised by the build itself \u2014 the packaging, restore or SDK step \u2014 about the project as a whole, not by the compiler or an analyzer at a line of code, so there is no call site to narrow it to and no per-site directive that could carry a reason: this element is the only place the decision can be recorded. Say WHY here, in a comment on the entry, or fix what the rule is reporting and drop the code from the list."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Ingos.Abp.Templates.csproj"},"region":{"startLine":17}}}],"partialFingerprints":{"codehealthFindingId/v1":"0386f595a91995477a2932d663c609fcf77a20c79f48e65cc6d905940e551e6a"}},{"ruleId":"D17","level":"warning","message":{"text":"Dead code: L: Method L \u2014 Roslyn\u0027s SymbolFinder walked every project the solution loads, including IngosAbpTemplate.Application.Contracts, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository \u2014 a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol\u0027s name, and any project the workspace could not load. This is \u0027no caller found by this walk\u0027, not a verdict that the symbol is unused."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Application.Contracts/Permissions/IngosAbpTemplatePermissionDefinitionProvider.cs"},"region":{"startLine":17}}}],"partialFingerprints":{"codehealthFindingId/v1":"047753e015ec337cbd6bc8f6369f469dc06d52091e27c0be12a8d7c008d9e232"}},{"ruleId":"D17","level":"warning","message":{"text":"Dead code: IngosAbpTemplateDomainErrorCodes: NamedType IngosAbpTemplateDomainErrorCodes \u2014 Roslyn\u0027s SymbolFinder walked every project the solution loads, including IngosAbpTemplate.Domain.Shared, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository \u2014 a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol\u0027s name, and any project the workspace could not load. This is \u0027no caller found by this walk\u0027, not a verdict that the symbol is unused."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Domain.Shared/IngosAbpTemplateDomainErrorCodes.cs"},"region":{"startLine":3}}}],"partialFingerprints":{"codehealthFindingId/v1":"92a6f62a71c51fe88594af795f003cbdb477498739e2efa12161638b03d385b6"}},{"ruleId":"D17","level":"warning","message":{"text":"Dead code: Consts: NamedType Consts \u2014 Roslyn\u0027s SymbolFinder walked every project the solution loads, including IngosAbpTemplate.Infrastructure, and found no reference to it. That walk cannot see three kinds of caller, so check them before removing it: code outside the solution file (a solution is a curated list, not the repository \u2014 a sibling test tree with its own .sln is invisible), a call resolved by reflection or dependency injection from the symbol\u0027s name, and any project the workspace could not load. This is \u0027no caller found by this walk\u0027, not a verdict that the symbol is unused."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Infrastructure/EntityConfigurations/Consts.cs"},"region":{"startLine":13}}}],"partialFingerprints":{"codehealthFindingId/v1":"2ba2bf37ca8157669ebaa0f339d093a2e4460f70064fb10be88ee867e8ce96d7"}},{"ruleId":"D28","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"4d79dbf2b8de6ed87225bb5b5364e1113f325ab40e6ab8fcdf7a80d9bb48a129"},"properties":{"commitSha":"f03fe3f3288df9195f41f6c08fb43b0c6506de83"},"taxa":[{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-540","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A01:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D28","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"3110b48e61a9e8f9d7a4fbd4eef14763e73e0752c508c3fa28ac7e5b657ab457"},"properties":{"commitSha":"f7099f23f3c797addfc7b2663278b2a418ae641d"},"taxa":[{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-540","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A01:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D28","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"4456d14040f42e8c36594ccb58880c6c9c5afa9ccc2cb6c87f606e159faf2f40"},"properties":{"commitSha":"72f094200acd340da3f7cf50f0a7d6cb86e825ba"},"taxa":[{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-540","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A01:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D28","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"7557987acb868326a86687e7cc9e7cbe36e1aa217ffe7a3d440397ca85da551d"},"properties":{"commitSha":"3bcffc28a351a294f5284e9f9a6eeb462d698f8d"},"taxa":[{"id":"CWE-259","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-540","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A01:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D28","level":"note","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"3cdfd7beb31b791ae18dcb425e21eb157c842e7bbcd522cc330573c1a6538db1"}},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"73fff3c6c9e2d9da7d4f738c40b8a223e17cfd14b0555814ffc82880faec5f41"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D29","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"f6d629032dff8af67a8377dc92a11bc9f3174a637468e2db142a019acc12e4ab"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D29","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"638f54a4cfdcd6f371802b06bdae11893fe1a62edc151da9789202668b33043b"},"taxa":[{"id":"CWE-1104","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-1329","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},{"id":"CICD-SEC-8","toolComponent":{"name":"OWASP Top 10 CI/CD Security Risks","guid":"3c9b2a6e-5d14-4f7b-8e02-6a1d9c4b7f35"}}]},{"ruleId":"D29","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"9bd6a34bf35384ec363c75f8c402351fc96b8496c9c411f9ae94249553f6f53e"},"taxa":[{"id":"CWE-1104","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-1329","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},{"id":"CICD-SEC-8","toolComponent":{"name":"OWASP Top 10 CI/CD Security Risks","guid":"3c9b2a6e-5d14-4f7b-8e02-6a1d9c4b7f35"}}]},{"ruleId":"D29","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"060f51daf7ba6cd5326938122ddaa91326cc4495721af4fd5bcb4f4126fad5a6"},"taxa":[{"id":"CWE-1104","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-1352","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}},{"id":"CICD-SEC-7","toolComponent":{"name":"OWASP Top 10 CI/CD Security Risks","guid":"3c9b2a6e-5d14-4f7b-8e02-6a1d9c4b7f35"}}]},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"2ab6c36f9ba2959809d6b740f8a18ff7828f8fb8bf1e55a125029d888bdd3b3f"},"properties":{"dependency":{"package":"System.Drawing.Common","version":"5.0.0","advisory":"[GHSA redacted]","reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"545ec352dd833d01b83eb1ad655fc194727c31bfff86b5cae45164f74c644888"},"properties":{"dependency":{"package":"System.Linq.Dynamic.Core","version":"1.2.9","advisory":"[GHSA redacted]","aliases":["[GHSA redacted]"],"reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"78ed4a94f7838667d047615990a0373ebc00d71c8f67fd72adc7dac2fef99d9b"},"properties":{"dependency":{"package":"Scriban","version":"3.6.0","advisory":"[GHSA redacted]","aliases":["[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]","[GHSA redacted]"],"reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"03b31df8570933308505a1624e4fd5ee0390537c65b94f5898a4ad85f2c0b177"},"properties":{"dependency":{"package":"System.Formats.Asn1","version":"5.0.0","advisory":"[GHSA redacted]","reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"7cf85abffe732f2645ef95a624d6badc26f0263616284d6a4cc46ca8e983031d"},"properties":{"dependency":{"package":"System.Net.Http","version":"4.3.0","advisory":"[GHSA redacted]","reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"b96b7173c4377d5bea4d6fd7b52323631c631c44172b743bec6f266c10a4e538"},"properties":{"dependency":{"package":"System.Text.RegularExpressions","version":"4.3.0","advisory":"[GHSA redacted]","reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"81d70374024ff22e11cf5598879a317ed70ee1bc2d998f8f8933659faa3ca8ec"},"properties":{"dependency":{"package":"AutoMapper","version":"10.1.1","advisory":"[GHSA redacted]","reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"53ac12a78ad0a5821206006a8a3ae6ed4b8df689d97ee6f166002a58f55acb06"},"properties":{"dependency":{"package":"Microsoft.IdentityModel.JsonWebTokens","version":"6.14.0","advisory":"[GHSA redacted]","reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"1b64b1a9ae35803f0bda185e2755dac4fcb0de2707a8c83832fac84091ef78fb"},"properties":{"dependency":{"package":"System.Security.Cryptography.Xml","version":"5.0.0","advisory":"[GHSA redacted]","reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"302585f5569c755b05ec019c495fad90da7acecd3608a1876f10165de8d80d39"},"properties":{"dependency":{"package":"System.IdentityModel.Tokens.Jwt","version":"6.14.0","advisory":"[GHSA redacted]","reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"b6a1910baf26ab7f13dbc3b5d211204572f5b65f0406ebcf935b6f8255e7e97d"},"properties":{"dependency":{"package":"Swashbuckle.AspNetCore.SwaggerUI","version":"6.1.3","advisory":"[GHSA redacted]","reachability":{"kind":"unknown"}}}},{"ruleId":"D30","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"666b5a44b71fd2be730e2d54f00fa36c52834c4dac4989245de2b352ca028b06"},"properties":{"dependency":{"package":"MySqlConnector","version":"1.3.7","advisory":"[GHSA redacted]","reachability":{"kind":"unknown"}}}},{"ruleId":"D31","level":"error","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"6f3eedc9ddf9607f6b5c18cbe741b3bfd07f1f79a5bd9ae624e90e06c64f656a"}},{"ruleId":"D31","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"56e86f75b1ebac5a885e110b30c1b13e15de0c5438e9aa269a13e47ac79a2a3e"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D31","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"f5f8358403cf42bada353707e5a83c3e7458931732772370b2e9a84144677b2a"},"taxa":[{"id":"CWE-1357","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-353","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A03:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D31","level":"warning","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"21553fd38d3ba2e153977df6ead53ce01cc429759ad3fa4b7de8adda628280d6"},"taxa":[{"id":"CWE-250","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"CWE-522","toolComponent":{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d"}},{"id":"A06:2025","toolComponent":{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61"}}]},{"ruleId":"D31","level":"note","message":{"text":"A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."},"partialFingerprints":{"codehealthFindingId/v1":"48a89fa08408a2f1259a84e33b28ca03d89f687e0e9b07534091083f2afcaeb1"}},{"ruleId":"D40","level":"note","message":{"text":"No network policy: No Kubernetes NetworkPolicy (or Cilium policy) found. Without one, every pod can talk to every other pod and reach out to the internet by default. Add a default-deny policy and open only the flows you need."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"295828650a2aaa1b03ae9b32ae6843a0c38011e5a70b1926442c4fa7187de5f0"}},{"ruleId":"D44","level":"warning","message":{"text":"End-of-life runtime: .NET net5.0: Ingos.Abp.Templates.csproj declares .NET net5.0 as this project\u0027s target framework, and .NET 5, support ended 2022-05-10. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-05-10 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"Ingos.Abp.Templates.csproj"},"region":{"startLine":12}}}],"partialFingerprints":{"codehealthFindingId/v1":"103abbb937161caf6d91efbe98b8152f2768c741bb494fac31f8d9e72003f9b2"}},{"ruleId":"D44","level":"warning","message":{"text":"End-of-life runtime: .NET net5.0: templates/src/IngosAbpTemplate.API/IngosAbpTemplate.API.csproj declares .NET net5.0 as this project\u0027s target framework, and .NET 5, support ended 2022-05-10. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-05-10 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.API/IngosAbpTemplate.API.csproj"},"region":{"startLine":4}}}],"partialFingerprints":{"codehealthFindingId/v1":"86a0c2df3a6ebb15b23a059c3f27d4cc1f0f110af305a7fdc5b54c3b7277da80"}},{"ruleId":"D44","level":"warning","message":{"text":"End-of-life runtime: .NET net5.0: templates/src/IngosAbpTemplate.Application.Contracts/IngosAbpTemplate.Application.Contracts.csproj declares .NET net5.0 as this project\u0027s target framework, and .NET 5, support ended 2022-05-10. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-05-10 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Application.Contracts/IngosAbpTemplate.Application.Contracts.csproj"},"region":{"startLine":4}}}],"partialFingerprints":{"codehealthFindingId/v1":"6a60c60075924b007f7ebd4bda5c05267dce7476052817d27db70ec807bd16f9"}},{"ruleId":"D44","level":"warning","message":{"text":"End-of-life runtime: .NET net5.0: templates/src/IngosAbpTemplate.Application/IngosAbpTemplate.Application.csproj declares .NET net5.0 as this project\u0027s target framework, and .NET 5, support ended 2022-05-10. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-05-10 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Application/IngosAbpTemplate.Application.csproj"},"region":{"startLine":4}}}],"partialFingerprints":{"codehealthFindingId/v1":"f094679fbf669e2eac8e85d66a0684aeeb75ebbc3568206891cfcd698dc9a8d8"}},{"ruleId":"D44","level":"warning","message":{"text":"End-of-life runtime: .NET net5.0: templates/src/IngosAbpTemplate.Domain.Shared/IngosAbpTemplate.Domain.Shared.csproj declares .NET net5.0 as this project\u0027s target framework, and .NET 5, support ended 2022-05-10. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-05-10 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Domain.Shared/IngosAbpTemplate.Domain.Shared.csproj"},"region":{"startLine":4}}}],"partialFingerprints":{"codehealthFindingId/v1":"3be1aa308ab2759b16d6f4c5ffdbfe5f6d9ed364e4b311dbdb420a5888775b88"}},{"ruleId":"D44","level":"warning","message":{"text":"End-of-life runtime: .NET net5.0: templates/src/IngosAbpTemplate.Domain/IngosAbpTemplate.Domain.csproj declares .NET net5.0 as this project\u0027s target framework, and .NET 5, support ended 2022-05-10. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-05-10 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Domain/IngosAbpTemplate.Domain.csproj"},"region":{"startLine":4}}}],"partialFingerprints":{"codehealthFindingId/v1":"bbc0989eec18eaf7378a380e76c09bc2d27d5a38e1e2762fd6186db165ec7f13"}},{"ruleId":"D44","level":"warning","message":{"text":"End-of-life runtime: .NET net5.0: templates/src/IngosAbpTemplate.Infrastructure/IngosAbpTemplate.Infrastructure.csproj declares .NET net5.0 as this project\u0027s target framework, and .NET 5, support ended 2022-05-10. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-05-10 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.Infrastructure/IngosAbpTemplate.Infrastructure.csproj"},"region":{"startLine":4}}}],"partialFingerprints":{"codehealthFindingId/v1":"0276e580a775b46e1544d331e0e26524d35b6193fb821d84dd2bcd87426b2d64"}},{"ruleId":"M2","level":"note","message":{"text":"No ADRs: No Architecture Decision Records found \u2014 no conventional ADR directory, no numbered \u0060NNNN-title\u0060 documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"670b3d6e36a756d63097d0dfbf90afd5fc761308800b9354894a07c3f4e4aa14"}},{"ruleId":"M3","level":"note","message":{"text":"No src/ separation: Production code isn\u0027t grouped under a src/ folder \u2014 it all sits under templates/ alongside the root build files, so the conventional src/ boundary between the product and its tooling isn\u0027t drawn."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"fdf7f5b24e313364d10170a5c2542959902fe0d26ed70edef3eaa10ec5bcdb1d"}},{"ruleId":"P10","level":"note","message":{"text":"No explicit versioning: No explicit version was found by any of the six routes this check reads: a \u0060\u003CVersion\u003E\u0060 or \u0060\u003CVersionPrefix\u003E\u0060 property; a \u0060GitVersion\u0060 or \u0060MinVer\u0060 reference; the split Arcade spelling (\u0060\u003CMajorVersion\u003E\u0060 AND \u0060\u003CMinorVersion\u003E\u0060 together); a hand-written \u0060[assembly: AssemblyVersion]\u0060 in source, with \u0060bin/\u0060 and \u0060obj/\u0060 excluded so the SDK\u0027s generated AssemblyInfo cannot satisfy it; or a version handed to MSBuild by the pipeline, as \u0060-p:Version=\u0060 / \u0060-p:PackageVersion=\u0060 on a \u0060dotnet build\u0060 or \u0060dotnet pack\u0060 line. Only project files, first-party source and CI files are read, so a version computed somewhere none of those can see is invisible here. A published library needs explicit semantic versioning so consumers can reason about breaking changes."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"f25ed74033b9d9b8444441f8dacb71f30e7bc88fc4c32bea7aeaebd4fda20968"}},{"ruleId":"P6","level":"note","message":{"text":"No changelog: No CHANGELOG/HISTORY/RELEASES file \u2014 what shipped when isn\u0027t easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)"},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"dda5aa5aed8cbb292c3ef2b733bc138f614293ae6426c85e98bf31ef330d9415"}},{"ruleId":"P7","level":"warning","message":{"text":"Outbound HTTP without resilience: \u0060context.Services.AddHttpClient()\u0060 registers an outbound HTTP client with no resilience handler, retry policy or timeout of its own in its builder chain. A slow or failing dependency will hold this service\u0027s request, thread or connection \u2014 and cascade \u2014 until the call gives up on its own (100 s for HttpClient\u0027s default)."},"locations":[{"physicalLocation":{"artifactLocation":{"uri":"templates/src/IngosAbpTemplate.API/IngosAbpTemplateApiModule.cs"},"region":{"startLine":82}}}],"partialFingerprints":{"codehealthFindingId/v1":"988dd3667931754d5e1ca768a5ecc67bcc16304dde45ffaf26eeb291c6c8a637"}},{"ruleId":"PF1","level":"note","message":{"text":"No performance benchmarks: No benchmark suite was found by the two searches this check runs. FIRST, a BenchmarkDotNet package reference in any project file \u2014 every project the workspace loaded, plus a walk of project files on disk that never loaded, because a benchmark suite is exactly the project a partial load drops. SECOND, a script harness: a file whose name contains \u0060benchmark\u0060 and ends \u0060.py\u0060, \u0060.sh\u0060, \u0060.ps1\u0060, \u0060.bash\u0060, \u0060.rb\u0060, \u0060.js\u0060 or \u0060.mjs\u0060, credited ONLY when this repository\u0027s CI text also mentions benchmarks \u2014 a harness no pipeline runs is read as a fixture, deliberately. Neither search can see a benchmark suite in another ecosystem\u0027s idiom (a Go \u0060testing.B\u0060 file, a JMH or criterion project, a pytest-benchmark run), so this is \u0027no benchmark found by those two searches\u0027, not a verdict that the repository has none. Where code is performance-sensitive, a benchmark guards against silent regressions \u2014 but it\u0027s a bonus here, not a deduction."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"fd90d18ee3bb127e8033d41e8efe4e131487a6d794a5730a72c56105ef7485ea"}},{"ruleId":"S1","level":"note","message":{"text":"No security response headers detected: None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, \u2026) is configured \u2014 defense in depth, even when a reverse proxy could set them. (\u22122.0 on this card.)"},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"bd19c680309417e132c0be93c2002123f0664b42afe6172b1319da65a6a57ba7"}},{"ruleId":"S1","level":"note","message":{"text":"No app-layer HTTPS enforcement detected: No UseHttpsRedirection/UseHsts and no reverse-proxy signal \u2014 transport security is unverified at the app layer. (\u22122.0 on this card.)"},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"8697c7a8b4c37084f15e81b8ec84d4cf62954730be74a0816d39b2127a21fd9b"}},{"ruleId":"S1","level":"note","message":{"text":"No inbound model validation detected: No ModelState/[ApiController]/FluentValidation signal \u2014 inbound payloads reach handlers unvalidated. (\u22122.0 on this card.)"},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"1e343a08f907541b5ab584e2be0bd232044d68d45290bf7644e4e17db640a994"}},{"ruleId":"SC1","level":"warning","message":{"text":"NuGet dependencies are not locked: No packages.lock.json and no central package management \u2014 restores aren\u0027t reproducible or pinned (SSDF PW.4.4). Enable \u003CRestorePackagesWithLockFile\u003Etrue\u003C/RestorePackagesWithLockFile\u003E (commit the lockfile) or adopt Directory.Packages.props. Advisory \u2014 never scored."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"0a97b4f69ccac509400ece7eedefb06d3ede0522cd4d8bcb5c068bea719545a6"}},{"ruleId":"X5","level":"note","message":{"text":"Nullable reference types not enabled everywhere: 0/7 NRT-eligible project(s) enable \u003CNullable\u003Eenable\u003C/Nullable\u003E (projects targeting a pre-C#-8 framework are excluded \u2014 NRTs aren\u0027t available there). NRTs catch a whole class of null-deref bugs at compile time."},"locations":[],"partialFingerprints":{"codehealthFindingId/v1":"80b24de9378624a0ce4846d60457395befcaec8e109ea81d289a370c9f7bfd5d"}}],"taxonomies":[{"name":"CWE","guid":"c3a2b1d0-7f3e-4b2a-9c1d-5e6f7a8b9c0d","organization":"MITRE","informationUri":"https://cwe.mitre.org/","isComprehensive":false,"shortDescription":{"text":"The MITRE Common Weakness Enumeration (CWE)."},"taxa":[{"id":"CWE-1032","guid":"5f21e517-68aa-a650-9a25-5771ef024637","name":"OWASP Top Ten \u2014 Security Misconfiguration category","shortDescription":{"text":"OWASP Top Ten \u2014 Security Misconfiguration category"},"helpUri":"https://cwe.mitre.org/data/definitions/1032.html"},{"id":"CWE-1104","guid":"4c918cb5-b2a6-6c55-9963-a44ee464305e","name":"Use of Unmaintained Third Party Components","shortDescription":{"text":"Use of Unmaintained Third Party Components"},"helpUri":"https://cwe.mitre.org/data/definitions/1104.html"},{"id":"CWE-1329","guid":"f70f1c3f-4ccf-cb5e-bdd3-03ba4868d36d","name":"Reliance on Component That is Not Updateable","shortDescription":{"text":"Reliance on Component That is Not Updateable"},"helpUri":"https://cwe.mitre.org/data/definitions/1329.html"},{"id":"CWE-1352","guid":"5257f322-5cfc-6b52-bedd-0b9a526b4c7d","name":"CWE-1352","shortDescription":{"text":"CWE-1352"},"helpUri":"https://cwe.mitre.org/data/definitions/1352.html"},{"id":"CWE-1357","guid":"e4d2e772-757e-0a5c-bd7d-77052949d866","name":"Reliance on Insufficiently Trustworthy Component","shortDescription":{"text":"Reliance on Insufficiently Trustworthy Component"},"helpUri":"https://cwe.mitre.org/data/definitions/1357.html"},{"id":"CWE-1395","guid":"800e09e7-c11a-8654-9fa6-86f398995fed","name":"Dependency on Vulnerable Third-Party Component","shortDescription":{"text":"Dependency on Vulnerable Third-Party Component"},"helpUri":"https://cwe.mitre.org/data/definitions/1395.html"},{"id":"CWE-16","guid":"659db3ea-affc-8453-8add-c1218fbfcb92","name":"Configuration","shortDescription":{"text":"Configuration"},"helpUri":"https://cwe.mitre.org/data/definitions/16.html"},{"id":"CWE-250","guid":"52ee12e8-390a-7351-b1e6-388afa694e54","name":"CWE-250","shortDescription":{"text":"CWE-250"},"helpUri":"https://cwe.mitre.org/data/definitions/250.html"},{"id":"CWE-259","guid":"ae9ad959-fbb6-9d5e-892d-3dca66da0b69","name":"Use of Hard-coded Password","shortDescription":{"text":"Use of Hard-coded Password"},"helpUri":"https://cwe.mitre.org/data/definitions/259.html"},{"id":"CWE-353","guid":"09d7e902-d4ee-f05d-ae6c-0a1554d0c18f","name":"Missing Support for Integrity Check","shortDescription":{"text":"Missing Support for Integrity Check"},"helpUri":"https://cwe.mitre.org/data/definitions/353.html"},{"id":"CWE-506","guid":"401d6455-56e3-0552-9a39-f77461673e3f","name":"Embedded Malicious Code","shortDescription":{"text":"Embedded Malicious Code"},"helpUri":"https://cwe.mitre.org/data/definitions/506.html"},{"id":"CWE-522","guid":"71fb233e-ce6a-ae57-9419-ef8373540b09","name":"Insufficiently Protected Credentials","shortDescription":{"text":"Insufficiently Protected Credentials"},"helpUri":"https://cwe.mitre.org/data/definitions/522.html"},{"id":"CWE-540","guid":"1a9db5db-e5bb-ae5d-935a-d1b4e9ee080b","name":"Inclusion of Sensitive Information in Source Code","shortDescription":{"text":"Inclusion of Sensitive Information in Source Code"},"helpUri":"https://cwe.mitre.org/data/definitions/540.html"},{"id":"CWE-732","guid":"1da27e8f-b330-7650-ab63-bd61953eae5d","name":"Incorrect Permission Assignment for Critical Resource","shortDescription":{"text":"Incorrect Permission Assignment for Critical Resource"},"helpUri":"https://cwe.mitre.org/data/definitions/732.html"},{"id":"CWE-77","guid":"332c8ade-6612-9f56-a06b-d8d90b1a8750","name":"Improper Neutralization of Special Elements used in a Command (\u0027Command Injection\u0027)","shortDescription":{"text":"Improper Neutralization of Special Elements used in a Command (\u0027Command Injection\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/77.html"},{"id":"CWE-78","guid":"2e31ceaf-c7ae-2e5e-9661-cfb1362789cf","name":"Improper Neutralization of Special Elements used in an OS Command (\u0027OS Command Injection\u0027)","shortDescription":{"text":"Improper Neutralization of Special Elements used in an OS Command (\u0027OS Command Injection\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/78.html"},{"id":"CWE-79","guid":"fd45580b-e8c4-fc5e-8c2f-aa8fab0b4dbf","name":"Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)","shortDescription":{"text":"Improper Neutralization of Input During Web Page Generation (\u0027Cross-site Scripting\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/79.html"},{"id":"CWE-798","guid":"5e8f057d-fee3-995a-a0cb-9fc5b0d174d1","name":"Use of Hard-coded Credentials","shortDescription":{"text":"Use of Hard-coded Credentials"},"helpUri":"https://cwe.mitre.org/data/definitions/798.html"},{"id":"CWE-89","guid":"6d08fdad-37eb-c150-bbf0-d7d946863407","name":"Improper Neutralization of Special Elements used in an SQL Command (\u0027SQL Injection\u0027)","shortDescription":{"text":"Improper Neutralization of Special Elements used in an SQL Command (\u0027SQL Injection\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/89.html"},{"id":"CWE-937","guid":"16f316ae-415c-b354-a59b-1f7905f756e9","name":"Using Components with Known Vulnerabilities","shortDescription":{"text":"Using Components with Known Vulnerabilities"},"helpUri":"https://cwe.mitre.org/data/definitions/937.html"},{"id":"CWE-94","guid":"75e7f50c-6c2f-dd52-bf40-bf6c52b861fd","name":"Improper Control of Generation of Code (\u0027Code Injection\u0027)","shortDescription":{"text":"Improper Control of Generation of Code (\u0027Code Injection\u0027)"},"helpUri":"https://cwe.mitre.org/data/definitions/94.html"}]},{"name":"OWASP Top 10","guid":"7d1f0c2e-4b6a-4e39-9a51-0b2e8c3d5f61","version":"2025","organization":"OWASP Foundation","informationUri":"https://top10.owasp.org/2025/","isComprehensive":false,"shortDescription":{"text":"The OWASP Top 10:2025 web application security risks."},"taxa":[{"id":"A01:2025","guid":"df693558-c822-0452-8f7b-4d53cb6bcc59","name":"Broken Access Control","shortDescription":{"text":"Broken Access Control"},"helpUri":"https://top10.owasp.org/2025/A01_2025-Broken_Access_Control/"},{"id":"A02:2025","guid":"668dee9e-41bc-6354-97d0-fdf8f40c50c1","name":"Security Misconfiguration","shortDescription":{"text":"Security Misconfiguration"},"helpUri":"https://top10.owasp.org/2025/A02_2025-Security_Misconfiguration/"},{"id":"A03:2025","guid":"168e227c-7735-2e57-bc6e-997affe644c5","name":"Software Supply Chain Failures","shortDescription":{"text":"Software Supply Chain Failures"},"helpUri":"https://top10.owasp.org/2025/A03_2025-Software_Supply_Chain_Failures/"},{"id":"A05:2025","guid":"87e86033-3231-8458-8e4a-5cb82743553a","name":"Injection","shortDescription":{"text":"Injection"},"helpUri":"https://top10.owasp.org/2025/A05_2025-Injection/"},{"id":"A06:2025","guid":"491554d7-b8e4-9652-91a9-53700dc92ece","name":"Insecure Design","shortDescription":{"text":"Insecure Design"},"helpUri":"https://top10.owasp.org/2025/A06_2025-Insecure_Design/"},{"id":"A07:2025","guid":"334ddd78-539d-d35c-83dd-253647eb7eaf","name":"Authentication Failures","shortDescription":{"text":"Authentication Failures"},"helpUri":"https://top10.owasp.org/2025/A07_2025-Authentication_Failures/"},{"id":"A08:2025","guid":"84b0c297-710e-9a5f-9335-936ecb260c36","name":"Software or Data Integrity Failures","shortDescription":{"text":"Software or Data Integrity Failures"},"helpUri":"https://top10.owasp.org/2025/A08_2025-Software_or_Data_Integrity_Failures/"}]},{"name":"OWASP Top 10 CI/CD Security Risks","guid":"3c9b2a6e-5d14-4f7b-8e02-6a1d9c4b7f35","organization":"OWASP Foundation","informationUri":"https://owasp.org/www-project-top-10-ci-cd-security-risks/","isComprehensive":false,"shortDescription":{"text":"The OWASP Top 10 CI/CD Security Risks."},"taxa":[{"id":"CICD-SEC-7","guid":"4c4af28d-49e3-2d51-b597-e1396c49658b","name":"Insecure System Configuration","shortDescription":{"text":"Insecure System Configuration"},"helpUri":"https://owasp.github.io/www-project-top-10-ci-cd-security-risks/CICD-SEC-07-Insecure-System-Configuration"},{"id":"CICD-SEC-8","guid":"b6b2dacf-a168-4957-876e-a8c73ee00eb0","name":"Ungoverned Usage of 3rd Party Services","shortDescription":{"text":"Ungoverned Usage of 3rd Party Services"},"helpUri":"https://owasp.github.io/www-project-top-10-ci-cd-security-risks/CICD-SEC-08-Ungoverned-Usage-of-3rd-Party-Services"}]}],"properties":{"codehealthPublication":{"public":true,"notice":"This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings \u2014 which rule fired, in which file, on which line, and how to fix it \u2014 are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.","securityFindingsRedacted":27,"secretScannerRunsExcluded":0}},"redactionTokens":["A security finding was recorded here. Its details are withheld on the public artifact \u2014 ask the repository owner for the full report."]}]}