Vendored and Copied Code Audit
Track code copied into the repository.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Audit code that has been copied into my repository from elsewhere. Repository structure and suspect directories: [STRUCTURE]. Languages: [LANGUAGES]. What I know about where the code came from: [PROVENANCE_NOTES]. Business model and distribution: [DISTRIBUTION]. Work through this checklist and mark Done, Partly, or Missing: [ ] Find vendored directories, minified bundles, copied snippets with license headers, and files with foreign copyright notices (describe commands to search for them) [ ] Record the source, version or commit, license, date copied, and local modifications for each [ ] Confirm the license allows this use and that notices and license texts are preserved [ ] Check for known vulnerabilities in the copied versions [ ] Decide whether to replace with a managed dependency, keep vendored with a documented update process, or remove [ ] Mark local patches clearly and consider upstreaming them [ ] Add a manifest file (VENDORED.md or equivalent) listing everything [ ] Add a continuous integration check that fails when unlisted vendored code appears [ ] Review AI-generated or copied snippets from forums for license or provenance concerns Deliver a register template, example entries, an update procedure, and a risk-ranked action list. This is an engineering aid; have a lawyer who knows [JURISDICTION] review license questions.
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.