Bycon

Latest version: v2.0.5

Safety actively analyzes 693883 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 7 of 15

1.2.1

* clean-up of info response m(all entryType schemas shown now)
* modification of entity_defaults format
* use of `beaconCollectionsResponse` for services & deprecation of `ProgenetixServiceResponse`
* `mongo_test_mode_query` (needs to be propagated more...)
* `beaconplus` domains support

1.2.0

* fix of `filterLogic` parameter for forced global `$or`
* more reshuffling of defaults and config parameters
- merged `beacon_mappings` intop `beacon_defaults`
- moved `config.yaml` to `bycon/config/`
- splitting of the `beacon_defaults` parameters into standard parameters, e.g.
for the main entry types, into the `beacon_defaults.yaml` file in
`bycon/config/`, and custom parameters (e.g. Progenetix' `phenopackets` entry
type definition or some aliases) into the `/local/` location
* streamlining of `__init__.py` and `read_specs.py` w/ respect to those changes
* concurrent `byconaut` update

1.1.7

This update continues with the disentangling of "package inherent" defaults and
definitions and "local" ones. Partcullarly:

* standard Beacon entity definitions arte now part of the package configuration,
_i.e._ `bycon/config/beacon_defaults.yaml` has now the entities, and additional
entities are then provided from `bycon/local/beacon_defaults.yaml` (which is copied
from the project root `/local/beacon_defaults.yaml`) during `updev.sh`)
- examples are the Progenetix specific data in the `info` entity or the non-standard
`phenopackets` entry type
* similar for `dataset_definitions` ...

1.1.6

* bugfix release for service items

1.1.5

* some changes to defaults & mappings parsing
- merging content of "beacon_defaults" & "service_defaults" (if existing) files
during init into "beacon_defaults"
- **new requirement**: `deepmerge` (removed `pydeepmerge)`)
* some reshuffling/fixes of entry type defaults
* refined `GeoLocation` schema - now in model...common and referenced there
* v1.1.5 was a bugfix immediately after the update ...

1.1.3

* move the new `histoheatplot` method code to use ImageDraw instead of SVG raw
for the heat strips (_i.e._ base64 encoded individual PNG strips)
- e.g. reduces size of 9.3MB example to 188kB
* 1.1.3 fixes a combination query bug

Page 7 of 15

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.