GitHub Dependency and Licence Compliance Check (Education Only)
Review dependency health and licence information.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Review dependencies. List of direct dependencies with versions, last release dates, licences and known security alerts: [DEPENDENCY_LIST]. Our project licence and policy on licences: [LICENCE_POLICY]. Group dependencies as critical, important or routine by how central they are. Identify outdated or unmaintained packages, major version gaps, open security alerts, single-maintainer packages, and licence types that may conflict with ours. Show counts and percentages for each category. Make a plain-language table of each licence type found and what it generally asks of users, flagging any combination to raise with a qualified person and any package with no licence stated. Return a table and an update plan sorted by risk, critical first: one group at a time, run tests, read release notes, keep a way to roll back. Say what you could not check; transitive dependencies need a tool to inspect them [VERIFY]. This is educational; licence compatibility is a legal question for a qualified adviser, and nothing here should be called compliant [VERIFY].
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.