HAROS is a framework for quality assurance of ROS-based code, mostly based on static analysis - which consists on extracting information from the source code without executing it (and, sometimes, even without compiling it). Its main goal is the early detection of problems in the software development life cycle, which would otherwise go unnoticed into later stages or even into production.
Try it yourself: there is a demo page of the HAROS visualizer available on GitHub.
Tutorials: on GitHub and on YouTube.
More info: short video presentation on YouTube.
Current Status
HAROS is still being developed, as of August 2021. Help improve HAROS by participating in a short user survey.
Installing
See INSTALL for installation methods and instructions.
How to Use
See USAGE for basic commands and usage instructions.
Bugs, Questions and Support
Check whether your question has an answer in the FAQ.
Please use the issue tracker for issues or feature requests directly related to HAROS.
For issues related to plugins, please use the respective plugin repository.
If you run into errors, or feel that something is not working, run HAROS in debug mode, so the log files do not miss any information, e.g.,
haros --debug analyse ...
Then, you can share the log file, found by default within ~/.haros/log.txt.
Citing
See CITING.
Contributing
See CONTRIBUTING.
Acknowledgment
Until March 2021, this work was financed by the ERDF – European Regional Development Fund through the Operational Programme for Competitiveness and Internationalisation - COMPETE 2020 Programme and by National Funds through the Portuguese funding agency, FCT - Fundação para a Ciência e a Tecnologia within project PTDC/CCI-INF/29583/2017 (POCI-01-0145-FEDER-029583).
1 maintainer
Metadata
1 maintainer
Release files for haros 3.10.20
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 | Actions |
|---|---|---|---|---|
| haros-3.10.20.tar.gz | 323.8 kB | Without provenance | Details for haros-3.10.20.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| haros-3.10.20-py2-none-any.whl | Python 2 | none | any | Details for haros-3.10.20-py2-none-any.whl |
Total release size: 686.9 kB
Release files / haros-3.10.20.tar.gz
| Download URL | haros-3.10.20.tar.gz |
|---|---|
| Size | 323.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5f03e8e6f51ca7999f7602329eadc181a933cb63ad32420ab639a433befabdbc
|
|
BLAKE2b-256 checksum How to use checksums |
16f81141b384f6eea2edb0d67880cd86f1f71a0f8e2c682f6f4d704ce69d0066
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.0 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/2.7.15rc1
|
Release files / haros-3.10.20-py2-none-any.whl
| Download URL | haros-3.10.20-py2-none-any.whl |
|---|---|
| Size | 363.1 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
b401aa733e967980934d8f04f3f8e5db2cfb4b98710f0d1511711aee0a8cd1c1
|
|
BLAKE2b-256 checksum How to use checksums |
7bb9a52aa1684a9a040a21c98d3ca17f273c4e95c1d5c5935d8d28f288e9de17
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.0 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/2.7.15rc1
|
Security for haros 3.10.20
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
