openscad_dependencies is a command-line tool designed to analyze call dependencies in OpenSCAD projects. Below is a guide on how to use it effectively.
Installation
You can install openscad_dependencies using pip, the Python package manager. Run the following command in your terminal:
python -m pip install openscad_dependencies
This will download and install the tool along with its dependencies. Ensure you have Python and pip installed on your system before running the command.
Usage
To use openscad_dependencies, open your terminal and run the following command:
openscad-dependencies [options] <input_file>
Here: - <input_file>: The path to the base .scad file whose dependencies you want to analyze. - [options]: Optional flags to customize the behavior of the tool.
Options
–help: Display help information about the tool.
Examples
Analyze dependencies of a file and the files it includes/uses, and print the result to the terminal:
openscad-dependencies my_model.scad
Help
For more information, run:
openscad-dependencies --help
Metadata
Release files for openscad-dependencies 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| openscad_dependencies-1.0.1.tar.gz | 14.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| openscad_dependencies-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.1 kB
Release files / openscad_dependencies-1.0.1.tar.gz
| Download URL | openscad_dependencies-1.0.1.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0b7559f717661693b904df79f500d8c4f17271f1854ff13ccecc863ccec8f184
|
|
BLAKE2b-256 checksum How to use checksums |
db4fcbfe4ff37ee1779fd50b0fdc942235bc47e02cd79ff4b58f81f6abc59add
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 23, 2026.
Transparency logRelease files / openscad_dependencies-1.0.1-py3-none-any.whl
| Download URL | openscad_dependencies-1.0.1-py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a5be7050f1df1b1daa5559f30e3171d37a94e65979f52895a7e4ea393b3f5c2a
|
|
BLAKE2b-256 checksum How to use checksums |
86d72a87e740508b6a9bd9c0fbc8420304cf8d2e1319691383b8ecec1cbd14ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 23, 2026.
Transparency logSecurity for openscad-dependencies 1.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for openscad_dependencies-1.0.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.