A previous release had provenance metadata, but this release does not. View details.
hugpy-curation
hugpy_curation — discovery dossiers and the search / screen / download /
smoke / judge review pipeline, extracted from abstract_hugpy_dev as part of
the Hugpy partition. Ownership and allowed dependencies are declared in
py/partition.toml; see PARTITION.md at the workspace root.
Allowed Python dependencies inside the ecosystem: hugpy_platform, hugpy_control, hugpy_storage, hugpy_engine, hugpy_oracle.
Layout
| Module | What |
|---|---|
review/ |
criteria, screen (HF metadata), download (through hugpy_storage), smoke (llama_cpp subprocess), judge, pipeline, store (sqlite record), push (worker -> central) |
dossier/ |
the per-model dossier: cards, weights, research, community, radar, trial, verdicts, build, store; oracle_source is the store as the oracle's DossierSource |
config.py |
every state root (REVIEW_DB, DOSSIER_DIR, DOSSIER_TRIAL_ROOT, REVIEW_CRITERIA_DIR, DOSSIER_CACHE_DIR, then HUGPY_CURATION_ROOT, then hugpy_platform.app_dirs) |
providers.py |
DoctrineSource seam (fleet doctrine read by the dossier judge; null default) |
cli.py |
hugpy-curation review ... / dossier list / install-providers |
deploy/ |
hugpy-review@.service + .timer (system and user/ variants) |
Wiring
hugpy_curation.install_providers(doctrine_source=None) registers the dossier
store with hugpy_oracle.providers.set_dossier_source and, when given, a
fleet doctrine adapter with hugpy_curation.providers.set_doctrine_source.
hugpy_server calls it at startup; hugpy-curation install-providers does
the same in a standalone process.
Downloads never run from curation's own code: with a live hugpy-downloader
daemon the review enqueues on hugpy_storage.downloader.queue; without one
it calls hugpy_storage.download_models.download_one in-process.
Metadata
Release files for hugpy-curation 0.2.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hugpy_curation-0.2.7.tar.gz | 196.7 kB | Without provenance | Details for hugpy_curation-0.2.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hugpy_curation-0.2.7-py3-none-any.whl | Python 3 | none | any | Details for hugpy_curation-0.2.7-py3-none-any.whl |
Total release size: 377.0 kB
Release files / hugpy_curation-0.2.7.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | hugpy_curation-0.2.7.tar.gz |
|---|---|
| Size | 196.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
12af8fe2e088419bad00c7d30ba167ab4dc3c7c58063081be51a692c2b0bc0df
|
|
BLAKE2b-256 checksum How to use checksums |
296e3abb3f91ffccce2880b2e8a9789060f46695ab279a787dde06ae94d218e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / hugpy_curation-0.2.7-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | hugpy_curation-0.2.7-py3-none-any.whl |
|---|---|
| Size | 180.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7bf6bbce74a3d4b88622f60beea03ac1e889d5b0b80cfae18879e82a57dc0dd4
|
|
BLAKE2b-256 checksum How to use checksums |
d40dd56979b573d8aad60642c690db22ad97cd908b8062ea9696ce88eba35bb3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for hugpy-curation 0.2.7
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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.2.4 2 files Partial provenance
- Added 0.2.7 2 files Without provenance
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.