RoboTestSSL
Robot Framework Library for TestSSL
Supports Python 2.7.x for now
Install Instructions
- You need docker to run this program
- Pull the TestSSL docker image:
docker pull we45/testssl
Keywords
run testssl against target
| run testssl against target | target | results path
- target: Domain or IP of the Target.
- results path: where your results will be stored. A
.jsonfile is generated as output
Metadata
Release files for RoboTestSSL 1.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 | |
|---|---|---|---|---|
| RoboTestSSL-1.1.tar.gz | 1.7 kB | Without provenance | Details |
Release files / RoboTestSSL-1.1.tar.gz
| Download URL | RoboTestSSL-1.1.tar.gz |
|---|---|
| Size | 1.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
957ad3c44067d4a886edadc1cf76c01d5310e6f176b6a06decba8a11db6ffa02
|
|
BLAKE2b-256 checksum How to use checksums |
ae41f31b1b05604e1b9084e293ef1b711e197b18d8135ccf70410c62baa8b315
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for RoboTestSSL 1.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.
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.