RoboNpmAudit
Robot Framework Library for NPM Audit Source Composition Analysis
Supports Python 2.7.x for now
Install Instructions
- You need docker to run this program
- Pull the brakeman docker image:
docker pull abhaybhargav/npmaudit - Install the RoboNpmAudit Library with
pip install RoboNpmAudit - Create a
.robotfile that includes the keywords used by RoboNpmAudit Library
Keywords
run npmaudit against source
| run npmaudit against source | source code path | results path
- source code path: where your ruby source code is located currently
- Your nodejs Source code needs to have a package.json file for
npm auditto scan - results path: where your results will be stored. An
.jsonis generated as outputs
Metadata
Release files for RoboNpmAudit 1.0.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 | Actions |
|---|---|---|---|---|
| RoboNpmAudit-1.0.1.tar.gz | 2.2 kB | Without provenance | Details for RoboNpmAudit-1.0.1.tar.gz |
Release files / RoboNpmAudit-1.0.1.tar.gz
| Download URL | RoboNpmAudit-1.0.1.tar.gz |
|---|---|
| Size | 2.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
64491dafe9d13f142398a1e43ac67cf04123340ab61c408cd90a7db2fe11ddd7
|
|
BLAKE2b-256 checksum How to use checksums |
547f0aee8546c84db8a275cd6fd3221c5301a02b9c7888689f7e38a0c4e5248f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/39.2.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/2.7.13
|
Security for RoboNpmAudit 1.0.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.