Introduction
Eze example plugin, provides a starter project for extending the capabilities of Eze, by adding new security tools or report types.
Getting Started
- Eze Cli and it's sub-repos are powered by python and docker, make sure you have the latest versions installed
- Have you read the Contributing Guide?
- Have you read the Code Of Conduct?
- Check out the existing issues to see if any issues you're interested in have already been raised
Build and Test
Install Locally (via make)
make plugin-install
Install Locally (Manual via pip)
rm dist/eze-example-plugin-*.tar.gz
python setup.py sdist
pip install dist/eze-example-plugin-*.tar.gz
Test installed correctly
eze tools list
eze reporters list
Contribute
Metadata
Release files for eze-example-plugin 0.8.0
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 | |
|---|---|---|---|---|
| eze-example-plugin-0.8.0.tar.gz | 4.9 kB | Without provenance | Details |
Release files / eze-example-plugin-0.8.0.tar.gz
| Download URL | eze-example-plugin-0.8.0.tar.gz |
|---|---|
| Size | 4.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2eec4fade6692799549573ab477f370f1a1e2ba82e450c3352236fb988ca3352
|
|
BLAKE2b-256 checksum How to use checksums |
512f526b5f37e13b1670e8f0f6c94e752df4741305224821f707cc21e74996e9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.25.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.8.2
|
Security for eze-example-plugin 0.8.0
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.