opendsec-harbor
A Harbor environment provider for opendsec: each Harbor trial runs as one opendsec World, and each service in the task's compose file as one Sandbox in it.
pip install opendsec-harbor
export OPENDSEC_URL=https://your-apiserver OPENDSEC_TOKEN=...
harbor run -p path/to/task -a oracle -e opendsec_harbor:OpenDSecEnvironment
The agent and the task stay the same; only the environment flag changes. The platform builds each task's image from its Dockerfile, so the machine running Harbor needs no Docker: the provider uploads the build context, and a task whose files haven't changed is a lookup, not a rebuild. A service that names an image runs it as is, so it must be public.
Option (--ek key=value) |
Variable | Default |
|---|---|---|
url |
OPENDSEC_URL |
http://localhost:7700 |
token |
OPENDSEC_TOKEN |
none |
ttl |
3h |
Tasks may use only the compose keys image, build, command, environment, volumes, expose, networks, healthcheck and depends_on; anything else fails the trial before it starts rather than running it wrong.
Run it on the hosted test bed: https://opendsec.vibrantlabs.com
Licensed under Apache-2.0.
Metadata
Release files for opendsec-harbor 0.2.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 | Actions |
|---|---|---|---|---|
| opendsec_harbor-0.2.0.tar.gz | 13.5 kB | With provenance | Details for opendsec_harbor-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| opendsec_harbor-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for opendsec_harbor-0.2.0-py3-none-any.whl |
Total release size: 29.0 kB
Release files / opendsec_harbor-0.2.0.tar.gz
| Download URL | opendsec_harbor-0.2.0.tar.gz |
|---|---|
| Size | 13.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e58ef98aee1ed1e1f372cee00e8a539c472d728cb408895e0e46e1e8b018270
|
|
BLAKE2b-256 checksum How to use checksums |
35eb74fb468c703e4d3495b2cc931d4bc1b7650590a0f07798eb2654bc27d5ed
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logRelease files / opendsec_harbor-0.2.0-py3-none-any.whl
| Download URL | opendsec_harbor-0.2.0-py3-none-any.whl |
|---|---|
| Size | 15.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3fcdb50b682f2b07cae6ca6de271f557592a8ae0d2d19c381f967541f2e68704
|
|
BLAKE2b-256 checksum How to use checksums |
9a90e6268c7dda736a0f297a4429f487907fe776286b6e68026bc06956a0b305
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logSecurity for opendsec-harbor 0.2.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for opendsec_harbor-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 4, 2026.
Transparency logA 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.