Is Supervision safe to use?

Supervision has an HVTrust score of 23.2/100 (Grade D), ranked #411 of 418 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Supervision?

Supervision scores 23.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 48.4k GitHub stars and is categorized under Needs review.

Supervision

roboflow/supervision

We write your reusable computer vision tools. 💜

Needs review Python Grade D Listed MIT

Compare → Suggest correction

Listing state

Listed

HVTrust

23.2/100 · Grade D

Evidence coverage

Grade D · 1/5 signals

Last push

2026-07-25 · 1d ago

Recent change

No recent signal change

Is Supervision safe? Supervision scores 23.2/100 (Grade D), ranked #411 of 418 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; recent commits are unsigned; last pushed 2026-07-25. Every point is earned from checkable signals — never paid placement. How scoring works →

Quick Trust Read

Verdict

Thin or incomplete trust evidence. Review carefully before production use.

23.2/100 · Grade D

Strongest Signal

Maintenance

19.7/20

Weakest Signal

Safety / Integrity

0/25

What Would Improve It

Add or improve OSSF Scorecard coverage so safety checks are easier to verify.

Recent Changes

2026-07-15

Rank Moved

Rank dropped 13 spots (#398 → #411)

2026-07-14

Rank Moved

Rank dropped 34 spots (#364 → #398)

2026-07-13

Rank Moved

Rank dropped 40 spots (#324 → #364)

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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.

Compare with another agent Get email alerts for Supervision View Needs review Report missing data

94.2

Activity sub-score · out of 100

23.2

HVTrust Score · out of 100

#411

Global Rank · of 418

#11

In Needs review

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

Rank Trend

2026-07-05 2026-07-26

Activity & Reach

Stars

48.4k

Forks

4.5k

Last Push

2026-07-25

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #411

Analysis

HVTrust Dimensions

23.2 / 100 · 50.0% confidence

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

0.0 / 25

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

Transparency50% declared license · 50% OSSF Scorecard

8.5 / 17

Maintenance60% last-push freshness · 40% commit activity

19.7 / 20

Adoption60% stars · 40% downloads, log-scaled

11.2 / 20

Activity Inputs

94.2 / 100

StarsRepository reach

28.1 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

24.2 / 25

CommunityFork signal

17.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

—

Not available

Signed Commits

—

Unable to query

Is Supervision safe?

Public trust evidence for Supervision 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 Supervision publish package provenance?

No published build provenance is currently detected for Supervision. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Supervision have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for Supervision. 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 Supervision actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Supervision use?

Supervision ships under MIT. 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.

Ranked neighbours in Needs review

#7 TencentDB Agent Memory — 54.3 (C) → #8 AI Town — 44.4 (D) → #9 HyperAgent — 43.1 (D) → #10 ClawWork — 35.0 (D) →

AI agent 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

medium confidence

1 detected

Public provider/service dependencies detected.

Postgres

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

code
database

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 Supervision?

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

Submit a correction → Add the trust badge

Reputation Timeline

2026-07-15

Rank Moved

Rank dropped 13 spots (#398 → #411)

2026-07-14

Rank Moved

Rank dropped 34 spots (#364 → #398)

2026-07-13

Rank Moved

Rank dropped 40 spots (#324 → #364)

2026-06-24

Rank Moved

Rank dropped 30 spots (#284 → #314)

2026-06-23

Rank Moved

Rank dropped 19 spots (#265 → #284)

2026-06-21

Rank Moved

Rank dropped 15 spots (#246 → #261)

2026-06-20

Rank Moved

Rank dropped 21 spots (#225 → #246)

2026-06-11

Newly Listed

First tracked at rank #209

GitHub →

Embed Badge Badge guide for maintainers →

Markdown:
            [![HVTrust](https://hvtracker.net/badge/supervision.svg)](https://hvtracker.net/agents/supervision)
            
HTML:
            <a href="https://hvtracker.net/agents/supervision"><img src="https://hvtracker.net/badge/supervision.svg" alt="HVTrust"></a>

Other agents in Needs review

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