Is pgvector safe?
pgvector scores 56.6/100 (Grade C), ranked #196 of 328 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types).
The public evidence: no package-provenance attestation found;
OSSF Scorecard rates its supply-chain practices 4.6/10;
recent commits are unsigned;
last pushed 2026-07-11. Every point is earned from checkable signals — never paid placement. How scoring works →
Quick Trust Read
Verdict
Promising trust profile, but some evidence still deserves review.
56.6/100 · Grade C
Strongest Signal
Maintenance
19.2/20
Weakest Signal
Safety / Integrity
5.8/25
What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-06-24
Rank Moved
Rank dropped 17 spots (#172 → #189)
2026-06-18
Rank Moved
Rank dropped 11 spots (#137 → #148)
2026-06-16
Rank Moved
Rank rose 16 spots (#154 → #138)
Maintainer Checklist
Raise Scorecard signalsCurrent OSSF Scorecard is 4.6/10. Tighten the weakest checks to improve public safety evidence.
Publish provenanceAdd package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commitsRaise the share of verified-signed commits to make maintainer identity and release history easier to trust.
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. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Signals refreshed2026-07-11 04:00 UTC·Repo last pushed today
Rank Trend
2026-07-052026-07-11
Activity & Reach
Stars
22.1k
Forks
1.2k
Last Push
2026-07-11
today
Commits (4 wk)
63
Downloads (7d)
—
HN mentions (30d)
11
Open Issues
8
Rank Change
=
was #196
Analysis
HVTrust Dimensions
56.6 / 100 · 100.0% confidence
Safety / IntegrityOSSF, provenance, signatures
5.8 / 25
Identity / ProvenanceListing and build link
10.8 / 18
TransparencyLicense and public checks
12.4 / 17
MaintenanceFreshness and commits
19.2 / 20
AdoptionStars and downloads
10.4 / 20
Activity Inputs
88.0 / 100
StarsRepository reach
26.1 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
22.5 / 25
CommunityFork signal
14.4 / 20
Supply Chain Trust
Package Provenance
None
No package attestations found
OSSF Scorecard
4.6 / 10
OpenSSF Scorecard · scanned Jul 10, 2026
Signed Commits
—
Unable to query
Binary-Artifacts10
Branch-Protection0
CI-Tests-1
CII-Best-Practices0
Code-Review0
Contributors10
Dangerous-Workflow10
Dependency-Update-Tool0
Fuzzing0
License9
Maintained10
Packaging-1
Pinned-Dependencies0
SAST0
Security-Policy9
Signed-Releases-1
Token-Permissions0
Vulnerabilities10
Is pgvector safe?
pgvector 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 pgvector publish package provenance?
No published build provenance is currently detected for pgvector. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does pgvector have an OpenSSF Scorecard?
pgvector has an OpenSSF Scorecard score of 4.6/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 pgvector actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does pgvector use?
pgvector ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
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.
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
Credential signal:
No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
code
database
search
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live
How this surface has changed
Detected changes to pgvector's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Runtime surface grew — new detected provider dependencies: OpenAI, Postgres
Maintain pgvector?
HVTrust scores pgvector 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) · OpenSSF Scorecard CLI · Algolia HN Search API
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.2 · Raw JSON
