How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-15 10:03 UTC·Repo last pushed today
Activity & Reach
Stars
1.4k
Forks
171
Last Push
2026-06-15
today
Commits (4 wk)
53
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
47
Rank Change
NEW
Analysis
HVTrust Dimensions
42.7 / 100 · 67.0% confidence
Safety / IntegrityOSSF, provenance, signatures
11.1 / 25
Identity / ProvenanceListing and build link
18.0 / 18
TransparencyLicense and public checks
8.5 / 17
MaintenanceFreshness and commits
18.9 / 20
AdoptionStars and downloads
7.6 / 20
Activity Inputs
75.9 / 100
StarsRepository reach
18.9 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
21.6 / 25
CommunityFork signal
10.4 / 20
Supply Chain Trust
Package Provenance
Verified
pypi attestation
OSSF Scorecard
—
Not available
Signed Commits
71%
of last 100 commits verified
Is Omnigent safe?
Public trust evidence for Omnigent is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Omnigent publish package provenance?
Yes. Omnigent's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Omnigent have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Omnigent. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Omnigent actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Omnigent use?
Omnigent ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Omnigent's commits signed?
71% of the last 100 commits to Omnigent are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
Profile context only
HVTrust currently ranks supply-chain and project-integrity trust only. This public view shows a compact AI-agent surface snapshot from repo docs and manifests. These fields are descriptive context and do not affect the production HVTrust rank. An experimental local preview remains available in Score Lab →, and the policy boundary is tracked on the roadmap →
MCP Server Support
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Amazon Bedrock
Anthropic
OpenAI
Postgres
Credential signal:
API keys or service config markers documented.
Tool / Plugin Surface
high confidence
5 tags
Broad capability areas detected.
browser
code
database
search
shell
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
Maintain Omnigent?
HVTrust scores Omnigent from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
