=========
`|Build Status| <https://travis-ci.org/jstutters/toolaudit>`_
Report on the tools used in your software pipeline.
Purpose
-------
``toolaudit`` provides a way of monitoring a collection of software
programs for version changes and is also able test functionality. It
written to assist with the auditing of software pipelines in
neuroscience research.
Usage
-----
``toolaudit`` uses `YAML <http://yaml.org/>`_ to describe software
collections. A simple example of one of these descriptions is:
::
---
tools:
- name: cat
path: /bin/cat
reader:
name: command_line
option: --version
regex: "^cat\\s\\(GNU\\scoreutils\\)\\s([0-9\\.]*)$"
test:
name: stdout
command: "{exe} {file1} {file2}"
inputs:
file1: foo.txt
file2: bar.txt
A simple invocation of toolaudit is: ``bash $ toolaudit example.yaml``
For the above example this would return:
::
---
tools:
- checksum: 9c3bb3efa8095f36aafd9bf3a698efe439505021
name: cat
output_checksum: 533fbb1dc1a426ecf19af2f8e4f01c59491e6f8f
path: /bin/cat
reader: {name: command_line, option: --version, regex: '^cat\s\(GNU\scoreutils\)\s([0-9\.]*)$'}
tester:
command: '{exe} {file1} {file2}'
inputs: {file1: foo.txt, file2: bar.txt}
name: stdout
version: '8.4'
The checksum is a SHA1 hash of the file identified at *path*. The output
checksum is a SHA1 hash of the what was printed to stdout.
Documentation
-------------
Full documentation is at:
`toolaudit.readthedocs.org <https://toolaudit.readthedocs.org/>`_.
Release History
---------------
0.0.5
~~~~~
- Allow user to choose to ignore non-zero return code when using the
fileout test
0.0.4
~~~~~
- Fixed crash when the line\_in\_file version reader was used with no
arguments
0.0.3
~~~~~
- Added support for Python 3
- Added the --onlytest option to run a specific test
0.0.2
~~~~~
- Initial public release
License
-------
``toolaudit`` is licensed under `The MIT
License <http://opensource.org/licenses/MIT>`_.
.. |Build
Status| image:: https://travis-ci.org/jstutters/toolaudit.svg?branch=master
Metadata
Release files for toolaudit 0.0.5
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 |
|---|---|---|---|---|
| toolaudit-0.0.5.tar.gz | 10.3 kB | Without provenance | Details for toolaudit-0.0.5.tar.gz |
Release files / toolaudit-0.0.5.tar.gz
| Download URL | toolaudit-0.0.5.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bb030883e60fd24cc9a2ad77ebe99df2ef5eaef063f09a38f8421f8b764c14dc
|
|
BLAKE2b-256 checksum How to use checksums |
c34a0e5288a7064bf520517138270cf5b0e68232189cf93bfbbb910f6a408e81
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for toolaudit 0.0.5
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.