This release is a pre-release and may not be stable for production use.
stix-shifter-builder
This repo exists to pull in the stix-shifter project from its public repo and build it to deploy it to our private artifactory
Every commit will cause a build in travis and deploy whatever VERSION is set to in scripts/travis-script.sh. So update VERSION environment variables there and commit it in order to deploy a new build.
PLEASE NOTE:
If you just want to test your commit version replace the TAG_VERSION variable value with "" and set the COMMIT_VERSION variable value with commit number.
3 maintainers
Metadata
3 maintainers
Release files for stix-shifter-modules-bigfix 6.1.0.dev102
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| stix_shifter_modules_bigfix-6.1.0.dev102-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Release files / stix_shifter_modules_bigfix-6.1.0.dev102-py2.py3-none-any.whl
| Download URL | stix_shifter_modules_bigfix-6.1.0.dev102-py2.py3-none-any.whl |
|---|---|
| Size | 39.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
913762bf5fc9c310146a2ccbfa875de6c3cebd4b688b413fed12779f7e2bc081
|
|
BLAKE2b-256 checksum How to use checksums |
1b06aa2d91cdff5f19131b4ccd4259a6a168ae5b3310bbff6865ca04aa93050b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.0
|
Security for stix-shifter-modules-bigfix 6.1.0.dev102
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.
