返回提示词目录第 1421 页

审查项目依赖许可证风险

梳理直接与间接依赖的许可证,输出清单、署名义务及潜在冲突,提示需法律专业确认。

完整提示词

<context>
Licence risk depends on three things together: the dependency's licence, how the project uses it (linked into what is shipped, a build tool, a test helper), and how the project is distributed (a hosted service, a library others ship, a binary given to customers). The same copyleft licence can be a non-issue for an internal service and a blocker for a distributed product, and the network clause of some licences reaches hosted services too. Inventories go wrong by reading only direct dependencies, trusting a package manifest that disagrees with the actual LICENSE file, missing licence changes between versions, and dropping attribution obligations that apply even under permissive licences.
</context>

<task>
Audit the dependency licences for the project at `{{repo_path}}`.

Project licence and distribution: {{project_license}}
<policy>
{{policy}}
</policy>

1. Identify every ecosystem and lockfile in the repository (including nested packages, containers and vendored code). Inventory from the resolved lockfile, not the manifest, so transitive dependencies and exact versions are included.
2. Use the licence tooling already present or the standard local tool for each ecosystem (for example license-checker or an npm query, pip-licenses, cargo-deny or cargo-license, go-licenses, the Maven or Gradle licence plugins, or a scanner such as ScanCode). Do not upload the dependency list to an online service without asking.
3. For each package record: name, version, direct or transitive, scope (runtime and shipped, build-only, dev or test), declared licence as an SPDX expression, and the licence found in its LICENSE or COPYING file when they differ.
4. Classify each package against the policy, or without one, into: permissive; weak copyleft (for example LGPL, MPL, EPL); strong copyleft (GPL); network copyleft (AGPL and similar); source-available or non-commercial terms; dual or multiple licences; unknown, missing or custom. Mark how the classification interacts with the stated distribution model and scope.
5. Flag: packages that conflict with the policy or plausibly with the distribution model; unknown and custom licences; manifest and LICENSE disagreements; licence changes between the locked version and newer versions; packages with notices that must be reproduced.
6. Write the full inventory to a file (CSV, or an SBOM format the project already uses) next to the report, and list the attribution and notice obligations for what is shipped.
</task>

<constraints>
- State once, at the start of the report, that this is an inventory to support a legal review, not legal advice, and that conclusions about compatibility and compliance belong to qualified counsel.
- Use "needs review" or "possible conflict", never "compliant", "safe" or "violation". Do not interpret licence terms beyond describing their well-known category.
- If the distribution model is unclear from the arguments, ask before classifying risk, because it changes the answer.
- Do not remove, replace or upgrade dependencies; recommend options for counsel and the team.
{{> guardrails/professional-limits}}
{{> guardrails/scope-discipline}}
{{> guardrails/verify-before-done}}
</constraints>

<output_format>
## Scope
Ecosystems, lockfiles, package counts (direct, transitive, by scope), tools used, what was not covered.

## Summary
Counts per licence category and per policy status.

## Needs review
Table: Package | Version | Scope | Licence | Why flagged | Questions it raises.

## Obligations
Attribution and notice obligations for shipped packages, and where a notice file would go.

## Unknown licences
Table: Package | Version | What was found | Suggested next step (contact the author, check the source repository).

## Questions for counsel
Numbered questions that a lawyer needs to answer, with the facts each one depends on.

## Verification
Commands run and real results, and where the inventory file is.
</output_format>

可替换内容

  • {{repo_path}}
  • {{project_license}}
  • {{policy}}
  • {{> guardrails/professional-limits}}
  • {{> guardrails/scope-discipline}}
  • {{> guardrails/verify-before-done}}

分类与标签

编程开发、依赖盘点、开源许可证、署名义务、法律复核

前往 AI 图片创作