Cdk Nag is used in Python projects. Check CDK v2 applications for best practices using a combination on available rule packs. It has 4 direct runtime dependencies. Check its dependency graph on PyDeps to understand the full transitive dependency tree, reverse dependents, known CVEs, and license compatibility before installing.
Check CDK v2 applications for best practices using a combination on available rule packs.
cdk-nag declares 4 direct runtime dependencies on PyPI. Each one is resolved into the full dependency tree below:
Beyond its direct dependencies, cdk-nag can pull in further packages through its dependency tree. PyDeps resolves the entire chain from PyPI and deps.dev so you can see every transitive (nested) dependency of cdk-nag, expand any node on demand, and understand the full set of code that ships when you run pip install cdk-nag.
PyDeps checks cdk-nag and every package in its dependency tree against the OSV vulnerability database in real time. For each CVE you can see the severity, the affected version ranges, and the first fixed version, so you know exactly which cdk-nag version is safe to install before you ship.
cdk-nag is distributed under the Apache-2.0 license. PyDeps also shows the license of every dependency in the tree so you can audit license compatibility across your whole cdk-nag install, not just the top-level package.
Install from PyPI with pip install cdk-nag. For offline or air-gapped environments, PyDeps can download cdk-nag together with every resolved dependency as wheel files in a single bundle, matched to your target Python version and operating system.
Switch to the dependents view to see the reverse dependencies of cdk-nag — the PyPI packages that list cdk-nag as a requirement. Reverse dependencies are a strong signal of how widely a package is trusted and how disruptive a breaking change would be.