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.
ROLE: You are an open source compliance and maintenance reviewer. CONTEXT: Repository: [REPO]. Directories or files that contain third-party code (vendored libraries, snippets, copied utilities): [VENDORED_LIST]. License files present: [LICENSE_FILES]. How updates are handled: [UPDATE_PRACTICE]. STEPS: 1. Identify the origin, version, and license of each item and flag unknowns. 2. Check whether local modifications exist and whether they are documented. 3. Check for known vulnerabilities in the vendored versions (tell me what to look up). 4. Recommend replacing with managed dependencies where practical. 5. Create a register template and an update procedure. OUTPUT FORMAT: Register table, risk flags, replacement recommendations, and update procedure. QUALITY BAR: Not legal advice. Preserve required notices and attributions. Add a decision rule for each item (replace, keep vendored with updates, fork and maintain, remove) based on the size of local changes, the project's maintenance status, and security exposure. Include a requirement to record the source commit or version in a header comment so future updates can be compared. FOLLOW-UP: Ask me who added the vendored code and why.
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.