How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Full methodology →
Signals refreshed2026-06-04 00:07 UTC·Repo last pushed 16 days ago
Rank Trend
2026-06-012026-06-03
Activity & Reach
Stars
9.9k
Forks
1.5k
Last Push
2026-05-19
16 days ago
Commits (4 wk)
38
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
230
Rank Change
▼2
was #120
Analysis
HVTrust Dimensions
57.6 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
7.2 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.7 / 17
MaintenanceFreshness and commits
17.3 / 20
AdoptionStars and downloads
9.6 / 20
Activity Inputs
81.6 / 100
StarsRepository reach
24.0 / 30
FreshnessLast push recency
22.8 / 25
ActivityRecent commits
19.8 / 25
CommunityFork signal
14.7 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.9 / 10
via deps.dev · OpenSSF
Signed Commits
21%
of last 100 commits verified
Code-Review5
Dangerous-Workflow10
Packaging-1
Maintained10
Token-Permissions0
CII-Best-Practices0
Binary-Artifacts10
Pinned-Dependencies0
Fuzzing0
License10
Signed-Releases-1
Branch-Protection0
Security-Policy0
SAST9
Is Pyod safe?
Pyod has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Pyod publish package provenance?
No published build provenance is currently detected for Pyod. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Pyod have an OpenSSF Scorecard?
Pyod has an OpenSSF Scorecard score of 4.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Pyod actively maintained?
Maintained. Last push was 16 days ago.
What license does Pyod use?
Pyod ships under BSD-2-Clause. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Pyod's commits signed?
21% of the last 100 commits to Pyod 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.
Runtime trust — coming soon
HVTrust currently scores supply-chain signals. We're adding runtime trust next: what an agent actually does when it runs — what it can reach, which tools it carries, what external services it depends on. Track progress on the roadmap →
MCP support
Tool / plugin surface
External service deps
Package provenance drift
Maintain Pyod?
HVTrust scores Pyod 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.
Data sources
GitHub REST API (repo, commits, stars, forks, license) · OSSF Scorecard via deps.dev
Each agent's signals refresh once daily across 6 staggered batches. Methodology v3.1 · Raw JSON
