Turbovec

A vector index built on TurboQuant, written in Rust with Python bindings

Needs review Rust Grade C Listed MIT
58.0/100
Rank #654 of 1328
Compare Turbovec

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-21 · 20d ago
Recent change
Rank +6

Is Turbovec safe? Turbovec scores 58.0/100 (Grade C), ranked #654 of 1328 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.8/10; recent commits are unsigned; last pushed 2026-08-21. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Needs review

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-09
Rank Moved
Rank dropped 61 spots (#592 → #653)
2026-09-09
Activity Score Changed
Activity score down 5pts (79 → 74)
2026-09-07
Rank Moved
Rank dropped 51 spots (#532 → #583)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.8/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
73.5
Activity sub-score · out of 100
#6

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-10 13:33 UTC · Repo last pushed 20 days ago

Rank Trend

2026-08-11 2026-09-10

Activity & Reach

Stars
16.8k
Forks
1.4k
Last Push
2026-08-21
20 days ago
Commits (4 wk)
7
Downloads (7d)
HN mentions (30d)
Open Issues
16
Rank Change
▼1
was #653

Analysis

HVTrust Dimensions vs Needs review

58.0 / 100 · 100.0% confidence

Turbovec Needs review average (11 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.5 / 25
in line with avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 10.8
Transparency50% declared license · 50% OSSF Scorecard
14.3 / 17
1.9 above avg 12.4
Maintenance60% last-push freshness · 40% commit activity
14.3 / 20
0.9 below avg 15.2
AdoptionLog-scaled stars · package downloads
10.1 / 20
1.0 above avg 9.1

Activity Inputs

73.5 / 100
StarsRepository reach
25.3 / 30
FreshnessLast push recency
22.2 / 25
ActivityRecent commits
11.3 / 25
CommunityFork signal
14.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.8 / 10
OpenSSF Scorecard · scanned Sep 9, 2026
Signed Commits
0%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 4
CI-Tests -1
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 4
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 10
Vulnerabilities 9

Is Turbovec safe?

Turbovec 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 Turbovec publish package provenance?
No published build provenance is currently detected for Turbovec. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Turbovec have an OpenSSF Scorecard?
Turbovec has an OpenSSF Scorecard score of 6.8/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 Turbovec actively maintained?
Maintained. Last push was 20 days ago.
What license does Turbovec use?
Turbovec ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Turbovec's commits signed?
0% of the last 100 commits to Turbovec 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.

Compare Turbovec head-to-head

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

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.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
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

Maintain Turbovec?

For maintainers

HVTrust scores Turbovec 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.

Reputation Timeline

Signal history
Rank 35Score 6Grade 3HVTrust 1Scorecard 1
2026-09-09
Rank Moved
Rank dropped 61 spots (#592 → #653)
2026-09-09
Activity Score Changed
Activity score down 5pts (79 → 74)
2026-09-07
Rank Moved
Rank dropped 51 spots (#532 → #583)
2026-09-06
Rank Moved
Rank dropped 13 spots (#519 → #532)
2026-09-05
Rank Moved
Rank dropped 74 spots (#445 → #519)
2026-09-04
Rank Moved
Rank dropped 16 spots (#429 → #445)
2026-09-03
Rank Moved
Rank dropped 24 spots (#405 → #429)
2026-09-02
Rank Moved
Rank dropped 12 spots (#393 → #405)
2026-09-01
Rank Moved
Rank dropped 19 spots (#374 → #393)
2026-08-31
Rank Moved
Rank dropped 35 spots (#339 → #374)
2026-08-29
Rank Moved
Rank dropped 17 spots (#318 → #335)
2026-08-28
Rank Moved
Rank dropped 16 spots (#302 → #318)
2026-08-26
Rank Moved
Rank dropped 25 spots (#270 → #295)
2026-08-24
Rank Moved
Rank dropped 18 spots (#249 → #267)
2026-08-22
Rank Moved
Rank rose 13 spots (#265 → #252)
2026-08-20
Rank Moved
Rank dropped 32 spots (#235 → #267)
2026-08-19
Rank Moved
Rank dropped 14 spots (#221 → #235)
2026-08-18
Rank Moved
Rank rose 10 spots (#231 → #221)
2026-08-17
Rank Moved
Rank rose 12 spots (#243 → #231)
2026-08-13
Rank Moved
Rank dropped 17 spots (#226 → #243)
2026-08-12
Rank Moved
Rank rose 11 spots (#237 → #226)
2026-08-10
Rank Moved
Rank dropped 16 spots (#216 → #232)
2026-08-08
Rank Moved
Rank dropped 42 spots (#172 → #214)
2026-07-26
Rank Moved
Rank rose 16 spots (#235 → #219)
2026-07-25
Rank Moved
Rank rose 15 spots (#250 → #235)
2026-07-24
Rank Moved
Rank rose 20 spots (#270 → #250)
2026-07-24
Activity Score Changed
Activity score up 7pts (72 → 79)
2026-07-23
Rank Moved
Rank rose 19 spots (#289 → #270)
2026-07-23
Activity Score Changed
Activity score up 8pts (64 → 72)
2026-07-19
Grade Changed
Trust grade D → C
2026-07-19
Rank Moved
Rank rose 28 spots (#312 → #284)
2026-07-19
Activity Score Changed
Activity score up 5pts (59 → 64)
2026-07-15
Rank Moved
Rank dropped 23 spots (#284 → #307)
2026-07-14
Rank Moved
Rank dropped 13 spots (#271 → #284)
2026-07-13
Rank Moved
Rank dropped 32 spots (#239 → #271)
2026-07-10
Grade Changed
Trust grade C → D
2026-07-10
Rank Moved
Rank dropped 12 spots (#226 → #238)
2026-07-10
Activity Score Changed
Activity score down 6pts (66 → 60)
2026-07-09
Rank Moved
Rank dropped 11 spots (#215 → #226)
2026-07-09
Activity Score Changed
Activity score down 6pts (72 → 66)
2026-06-24
Rank Moved
Rank dropped 24 spots (#180 → #204)
2026-06-23
Rank Moved
Rank dropped 10 spots (#170 → #180)
2026-06-18
Scorecard Added
OSSF Scorecard: 4.8/10
2026-06-18
Grade Changed
Trust grade D → C
2026-06-18
Rank Moved
Rank rose 76 spots (#221 → #145)
2026-06-18
HVTrust Changed
HVTrust up 34.2pts (24.3 → 58.5)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 58.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/turbovec.svg)](https://hvtracker.net/agents/turbovec)
HTML:
<a href="https://hvtracker.net/agents/turbovec"><img src="https://hvtracker.net/badge/turbovec.svg" alt="HVTrust"></a>

Other agents in Needs review

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON