audit-deps
Skill1 starsChanged 3 days agoMITView on GitHub
Check the dependencies of a project (direct and transitive - CMake packages, pkg-config, FetchContent, submodules, vendored code, prebuilt binaries, includes, pip/npm/cargo) for their licenses - what must be credited, copyleft constraints, non-commercial / source-available / paid / proprietary terms, dependencies without license or of unknown origin - generate the third-party notices, and check their known vulnerabilities / compromised versions; result delivered as a PDF report. Use whenever the user asks what the dependencies allow, what to credit, if a dependency is legal/paid/restrictive, a THIRD_PARTY_NOTICES file, or a dependency security check.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- garfiec/Librechat-Mobiletheir own version, first seen Nov 11, 2026
- latuconsinafr/claude-code-configtheir own version, first seen Oct 13, 2026
- krixon/skillstheir own version, first seen Oct 11, 2026
- JoviDeCroock/prachttheir own version, first seen Oct 11, 2026
- me2resh/apexyardtheir own version, first seen Oct 8, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- me2resh/apexyard★ 542same name
- garfiec/Librechat-Mobile★ 160same name
- JoviDeCroock/pracht★ 113same name
- krixon/skills★ 1same name
- latuconsinafr/claude-code-config★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository70 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-at-endSkill
- clarifySkill
- continue-workSkill
- exportSkill
- full-permissionSkill
- ideationSkill
- interactive-questionsSkill
- onboardSkill
- pauseSkill
- presentationSkill
- rtkSkill
- setup-contextSkill
- write-like-meSkill
- audit-bugsSkill
- audit-qualitySkill
- audit-securitySkill
- benchmarkSkill
- cmake-styleSkill
- cpp-classSkill
- cpp-commentsSkill
- cpp-projectSkill
- cpp-styleSkill
- better-explain-docSkill
- better-html-docSkill
- better-html-styleSkill
- better-protocol-docSkill
- docs-updateSkill
- explain-docSkill
- html-docSkill
- html-styleSkill
- protocol-docSkill
- readme-styleSkill
- reportSkill
- wiki-styleSkill
- ci-cdSkill
- git-commitSkill
- git-conventionsSkill
- pre-commitSkill
- legal-checkSkill
- legal-setupSkill
- licenseSkill
- libutils-exceptionSkill
- libutils-installSkill
- libutils-setupSkill
- libutilsSkill
- python-classSkill
- python-commentsSkill
- python-projectSkill
- python-styleSkill
- auditSkill
- cppSkill
- devSkill
- docSkill
- gitSkill
- legalSkill
- pythonSkill
- setup-projectSkill
- styleSkill
- setup-studioSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Not legal advice: say it once in the report.
- Very specific: line 40
Check every unknown, proprietary, source-available, non-commercial, copyleft entry by hand: license file of the upstream repository (gh api …
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dependencies: licenses, obligations, vulnerabilities
SKILL_DIR = directory of this file. Never remove or replace a dependency by yourself: report and propose.
Not legal advice: say it once in the report.
1. Inventory + licenses
python3 SKILL_DIR/scripts/deps.py <root> --transitive --json /tmp/deps.json --md /tmp/deps.md- Finds the dependencies (CMake
find_package/pkg_check_modules/FetchContent/ExternalProject,.gitmodules, vendored foldersthird_party/ vendor/ external/ libs/ cmake/libs/, prebuilt.a/.so, non standard#include <...>,requirements*.txt,package.json+ lock,Cargo.toml+ lock) and resolves each one to the system package owning it (rpm -qf/dpkg -S) for its version + license, or reads itsLICENSEfile. --transitive: library packages required by the system ones (2 levels) and the lockfile entries; a transitive dependency inherits the scope of its parent (testwhen only used by the tests).- Category and obligation per dependency:
| Category | Means for the project |
public-domain | nothing required |
permissive | credit: copyright + license text with the distributed product |
permissive-notice | credit + the NOTICE (Apache-2.0), state the changes |
weak-copyleft | changes to the library stay open; LGPL: allow relinking (dynamic linking, or provide the objects when static) |
strong-copyleft | the distributed product must be GPL-compatible and ship its sources |
network-copyleft | AGPL: sources also owed to network users (SaaS) |
non-commercial | no commercial use |
source-available | not open source (BUSL, SSPL, Elastic, Commons Clause...): production / SaaS / competition limits |
proprietary | paid / EULA / redistribution limits: read the terms |
unknown | no license found = all rights reserved: not usable until clarified |
system-runtime | glibc / libgcc / libstdc++: runtime exceptions, nothing to do |
2. Review (the script is a first pass)
- Check every
unknown,proprietary,source-available,non-commercial, copyleft entry by hand: license file of the upstream repository (gh api repos/<o>/<r>/license), package metadata, headers of the sources. - Compound expressions (
A AND B,A OR B):AND= all apply,OR= choose one (prefer the most permissive). - Linking matters: static (the user's libraries are
.a) vs dynamic for LGPL; headers-only = the code is in the binary. Test-only dependencies are not distributed. - Compatibility with the project license (
licenseskill, its compatibility table): ex. GPL dependency in an MIT product that is distributed = conflict. - "Illegal" / risky: no license, unclear origin (copied code, prebuilt binary without source/license), cracked or pirated components, assets (fonts, images, models) without rights, export-controlled crypto when relevant, paid SDKs used without a license (CUDA/NVIDIA EULA, Qt commercial, FMOD...).
3. Credits
python3 SKILL_DIR/scripts/deps.py <root> --notices THIRD_PARTY_NOTICES.md writes the attributions (name,
version, license, home, license texts from /usr/share/licenses), to review and to ship with the product
(and mention in the README, readme-style). Only on request: it creates a file in the project.
4. Vulnerabilities (also used by the audits)
python3 SKILL_DIR/scripts/vulns.py <root> --json /tmp/vulns.json --md /tmp/vulns.md [--recent-days 90]OSV (PyPI / npm / crates.io / pinned git commits, malicious packages MAL-* included), pending Fedora security
advisories of the installed packages (dnf updateinfo), GitHub security advisories of the upstream repositories
compared with the installed version (gh). Advisories published in the last 90 days are flagged recent.
For each finding: affected version, fixed version, the project usage (is the vulnerable feature used? grep it),
action (update the package, bump the requirement, pin/replace). Debian/Ubuntu: also debsecan if installed.
5. Report
Through the report skill: ask the output format of report (Markdown + PDF recommended, PDF only, Markdown only), location audit/ at the root of the repository (or of the current folder outside a repository), never docs/ unless asked (audit/<YYYY-MM-DD>-dependencies.{md,pdf}), English unless
asked. Sections: Summary (counts per category, blocking points first), Method (commit, tools, date, limits),
Licenses (table per dependency: version, license, category, scope, obligation), Obligations (what to credit and
where), Blocking / to clarify, Vulnerabilities (table by severity, recent first, fixed version, action),
Sources. Then give the path(s).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

