priorart is a deterministic tool for package discovery and evaluation. It retrieves candidates from a local, sigstore-verified semantic index across PyPI, npm, crates.io, pkg.go.dev, Maven Central, and NuGet — no language model at query time — scores them on signals from GitHub, deps.dev, and OpenSSF Scorecard, and returns a weighted health score with a build-or-adopt recommendation. priorart inspect <package> scores a single named package.
Research inspiration
Noise-floor thresholds for registry metrics follow Koch et al. (MADWeb 2024) on the weak correlation between GitHub stars and downstream adoption. Abandonment detection follows Coelho & Valente (ESEC/FSE 2017). Adoption-saturation curves reference Borges & Valente (JSS 2018) and Zerouali et al. (ICSR 2018). Dimension taxonomy is aligned with the CHAOSS Project metrics framework.
Key properties
- Deterministic end-to-end. Discovery is a local HNSW query (
fastembed+usearch, int8-quantized); scoring is a closed-form weighted composite. No language model at any stage — same inputs, same output. - Private by default. The semantic index is a sigstore-signed artifact pinned to a specific GitHub Actions signer identity. No hosted retrieval endpoint; after first-use download, queries never leave the host.
- Reproducible. The index is rebuilt monthly via a public GitHub Actions workflow and versioned by tag; pin a version to stabilize results across runs.
- Calibrated scoring. Dimension weights (0.30 / 0.20 / 0.20 / 0.15 / 0.15) follow the conventions of OpenSSF Scorecard, npms.io, and SourceRank. Not empirically validated across ecosystems; override in
config.yaml. - Supply-chain signals. Identity verification, copyleft detection, dependency-vulnerability flags, and OpenSSF Scorecard checks feed the composite score.
Pipeline
- Semantic retrieval. Task description is embedded with
BAAI/bge-small-en-v1.5and queried against a per-ecosystem HNSW index. Falls back to live registry search when top similarity < 0.5. - Signal collection. Registry metadata, GitHub repository metrics, deps.dev graphs, and OpenSSF Scorecard results; cached in SQLite with per-signal-group freshness windows.
- Scoring. Weighted composite across reliability, adoption, versioning, activity regularity, and dependency health, with an age-based confidence multiplier for packages under three years.
- Recommendation.
use_existing(≥ 75),evaluate(50–74), orbuild(< 50).
Install
pip install priorart-agent
Documentation
- SETUP.md — installation, environment, and MCP server setup.
- API.md — CLI, Python API, and MCP tool reference.
- ARCHITECTURE.md — scoring algorithm, data flow, and cache design.
- STYLE.md — coding standards.
- TESTING.md — test organization and coverage.
- AGENT_CONFIG.md — guidance for AI agents invoking the MCP tools.
License
See LICENSE for details.
Package metadata in the distributed semantic index is sourced from ecosyste.ms and licensed under CC BY-SA 4.0. Redistributing the index shard preserves that license.
Metadata
Release files for priorart-agent 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 |
|---|---|---|---|---|
| priorart_agent-0.2.0.tar.gz | 95.7 kB | With provenance | Details for priorart_agent-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| priorart_agent-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for priorart_agent-0.2.0-py3-none-any.whl |
Total release size: 155.4 kB
Release files / priorart_agent-0.2.0.tar.gz
| Download URL | priorart_agent-0.2.0.tar.gz |
|---|---|
| Size | 95.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8d4f6ea12e806e836dab2cb97236c737070624ebd18ec7ef10881fb19062cff0
|
|
BLAKE2b-256 checksum How to use checksums |
aad35e7e6c0a4ca3d8e17a61d13673e4513fcaa190317a786950ca0a906ef77f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 1, 2026.
Transparency logRelease files / priorart_agent-0.2.0-py3-none-any.whl
| Download URL | priorart_agent-0.2.0-py3-none-any.whl |
|---|---|
| Size | 59.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9f687fd443f3a71a450810ec39c5559698606f123703bf91b2058c89a06eb78f
|
|
BLAKE2b-256 checksum How to use checksums |
b86fb5f122b96df703bd7746b6f8def12117b750a7df8bbe372f67e507917356
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 1, 2026.
Transparency logSecurity for priorart-agent 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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for priorart_agent-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 May 1, 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.