Project Inventory: Technical Analysis and Mapping for Software Projects

Do you need to take over, audit, or simply understand an existing software project without knowing exactly what it contains or how its components are organized?

Project Inventory analyzes the project and automatically builds a technical map of what it observes: dependencies, subprojects, infrastructure, external services, imports, and relationships between components.

Understand a project before you start modifying it

Instead of manually going through the entire directory structure, manifests, and configuration files, you simply provide Project Inventory with the path to the project you want to analyze.

The tool recursively scans the project and gathers the technical information it detects to provide a structured view of its organization and dependencies.

Static analysis directly from your files

Project Inventory analyzes project files without executing the application or modifying its contents. The analysis can be performed locally or directly on a server with access to the project files.

No source code or secrets need to be sent to an external service to perform the analysis. Environment variable values are not exposed.

Reports ready to review and use

Once the analysis is complete, Project Inventory automatically generates a structured HTML report along with JSON and CSV exports, allowing you to review, retain, or process the collected technical information.

Project Inventory performs static analysis directly from the project files. It identifies observable technical elements and builds a structured technical map without executing the application or modifying its files.

The analysis covers:

• dependencies from manifests and lock files across 10 ecosystems
• subprojects and different technologies present within the same directory structure
• Docker Compose services and Dockerfile configurations
• infrastructure components detected within the project
• external services identified from observed elements
• Python imports classified as standard library, external dependencies, or internal modules
• observable relationships between subprojects, dependencies, services, and other components
• environment variable names without exposing their values

Project Inventory distinguishes between elements that are discovered, declared, locked, referenced, or interpreted from signatures. The absence of a static reference is therefore not treated as a conclusion about the software's actual runtime behavior.

Understanding an existing project involves more than simply browsing its directory structure or opening a few files. The most time-consuming part is often identifying its dependencies, subprojects, infrastructure, and the relationships between its different components.

Project Inventory automates this initial exploration phase by bringing together observable technical information into a structured and directly usable technical map.

This makes it easier to approach an existing, inherited, or unfamiliar project with an overview of its structure before you start working on its code.

Terms of use

This product is provided with complete technical documentation. It does not include installation services, personalized analysis, ongoing maintenance, or personalized support.

Installation, use, and interpretation of the results remain the user's responsibility, while the user retains full control over their technical environment. If required, additional services can be provided by Palks Studio as a separate engagement.