RoboNodeJSScan
Robot Framework Library for the NodeJSScan SAST Tool
Supports Python 3.x only
Currently version 1.2
Install Instructions
- You need docker to run this program
- Install the RoboNodeJSScan Library with
pip install RoboNodeJSScan - Create a
.robotfile that includes the keywords used by RoboNodeJSScan Library
Keywords
run nodejsscan against source
| run nodejsscan against source | source code path | results path | controls (optional) |
- source code path: where your ruby source code is located currently
- results path: where your results will be stored. A
.jsonare generated as outputs
1 maintainer
Metadata
1 maintainer
Release files for RoboNodeJSScan 1.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 | Provenance | |
|---|---|---|---|---|
| RoboNodeJSScan-1.2.tar.gz | 1.8 kB | Without provenance | Details |
Release files / RoboNodeJSScan-1.2.tar.gz
| Download URL | RoboNodeJSScan-1.2.tar.gz |
|---|---|
| Size | 1.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d3f1dc8feee24d7b1e22503f74029dd4b1d475622a1adc6cadabd4804e293f30
|
|
BLAKE2b-256 checksum How to use checksums |
50874c44c0744a4feb784dc99135569f0427c7cb14fbe993b332acc1813b74b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.7.3
|
Security for RoboNodeJSScan 1.2
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.
