rust-inspector
rust-inspector is a utility to extract dependencies and symbols from Rust binaries. It is designed to work as a ScanCode Toolkit plugin and integrated in ScanCode.io pipelines.
To install and use:
Run pip install rust-inspector
Use with scancode --json-pp - --rust-symbol --verbose <PATH to a tree or file with Rust binaries>
The JSON output will contain binary symbols found in Rust binaries if any.
A Go compiler is required to build go-inspector. Install Go from https://go.dev/doc/install or from a package manager.
License: Apache-2.0 AND MIT
Copyright (c) nexB Inc., AboutCode, OWASP Foundation and others.
Development
Install requirements and dependencies using ./configure --clean && ./configure --dev
Then source venv/bin/activate
Testing:
To run tests: pytest -vvs
To regen test fixtures: SCANCODE_REGEN_TEST_FIXTURES=yes pytest -vvs
Acknowledgements, Funding, Support and Sponsoring
This project is funded, supported and sponsored by:
Generous support and contributions from users like you!
the European Commission NGI programme
the NLnet Foundation
the Swiss State Secretariat for Education, Research and Innovation (SERI)
Google, including the Google Summer of Code and the Google Seasons of Doc programmes
Mercedes-Benz Group
Microsoft and Microsoft Azure
AboutCode ASBL
nexB Inc.
This project also uses some functions from other packages:
symbolic (https://pypi.org/project/symbolic/)
This project was funded through the NGI0 Entrust Fund, a fund established by NLnet with financial support from the European Commission’s Next Generation Internet programme, under the aegis of DG Communications Networks, Content and Technology under grant agreement No 101069594.
This project was funded through the NGI0 Core Fund, a fund established by NLnet with financial support from the European Commission’s Next Generation Internet programme, under the aegis of DG Communications Networks, Content and Technology under grant agreement No 101092990.
This project was funded through the NGI0 Entrust Fund, a fund established by NLnet with financial support from the European Commission’s Next Generation Internet programme, under the aegis of DG Communications Networks, Content and Technology under grant agreement No 101069594.
2 maintainers
Metadata
2 maintainers
Release files for rust-inspector 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| rust_inspector-0.2.2.tar.gz | 73.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rust_inspector-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 96.4 kB
Release files / rust_inspector-0.2.2.tar.gz
| Download URL | rust_inspector-0.2.2.tar.gz |
|---|---|
| Size | 73.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5cd30ce0942b4484e3248ef8950edadc1ffb38ca38a3bae034b2aeecf4577318
|
|
BLAKE2b-256 checksum How to use checksums |
f9790383c60f6f2b2196b648c54376ee3b62b70360fa93e26be7d3439dfbb2b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jul 14, 2026.
Transparency logRelease files / rust_inspector-0.2.2-py3-none-any.whl
| Download URL | rust_inspector-0.2.2-py3-none-any.whl |
|---|---|
| Size | 23.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
da78a3b5a60c4e2b97b08a6de7bb3eed91e532683a9ae7978600f01cd7338982
|
|
BLAKE2b-256 checksum How to use checksums |
15feaf076d92768ccf80a3f7a55f82d2155ad3a9aac88364b2b5ee2923493897
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 Jul 14, 2026.
Transparency log
