RobotFramework for ThreatPlaybook
Installation
pip install Playbot
Initialize
| Playbot | test-project | target-name | threatplaybook-host |
Keywords
Login
| login | email | password |
Create Project
| create project |
create target
| create target | url |
Bandit Results
| manage bandit results | resultsfile |
NodeJSScan Results
| manage nodejsscan results | resultsfile |
NPMAudit Results
| manage npmaudit results | resultsfile |
OWASP ZAP Results
| manage zap results | resultsfile |
Create New Scan
| create new scan | tool-name |
Create New Vulnerability
| create new vulnerability | vul-dictionary |
Vulnerability Dictionary should have: * name * cwe * description * scan-name * target * severity (integer, 3,2,1) * evidences (array): * name * url * param
Metadata
Release files for Playbot 3.2.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 | |
|---|---|---|---|---|
| Playbot-3.2.1.tar.gz | 4.7 kB | Without provenance | Details |
Release files / Playbot-3.2.1.tar.gz
| Download URL | Playbot-3.2.1.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9d730564be8c7542361dd5f46dbe26badd78df1e0be07dbd37f0c2c37dfb212e
|
|
BLAKE2b-256 checksum How to use checksums |
3fb184c3d065858bedd1d3767a7208350dc82f462ab1c6be4e19ed3f2a452cab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.7.3
|
Security for Playbot 3.2.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.