updated 2026-10-21 20:07 UTC

Supervision

Repository Website

We write your reusable computer vision tools. 💜

Needs review Python Listed MIT

Is Supervision safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard No result
Provenance None
Signed commits 98%
Last push today
Compare Supervision

How does it stack up against its Needs review neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Supervision scores 26.8/100 (Grade D), ranked #1358 of 1378 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; 98% of recent commits are signed; last pushed 2026-10-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Supervision could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Supervision and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/roboflow/supervision, MIT, last pushed 2026-10-21. 98% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Not checked

    No OpenSSF Scorecard result yet, so branch protection, code review and release signing are unverified.

  3. Published packages None

    No registry package. Supervision is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Supervision.

Evidence behind this score

Coverage D: 1 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks (missing)
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Supervision’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Supervision compares in Needs review

  1. #7 Hivemind 53.7 +26.9
  2. #8 AI Town 44.8 +18.0
  3. #9 HyperAgent 38.3 +11.5
  4. #10 ClawWork 34.8 +8.0
  5. #11 Supervision 26.8 this agent

Bars show each HVTrust score; the tick marks Supervision’s 26.8.

Where the 26.8 comes from

HVTrust dimensions vs the Needs review average

26.8 / 100 · 50.0% confidence

Supervision Needs review average (11 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.9 / 25
3.9 below avg 8.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
in line with avg 10.8
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.9 below avg 12.4
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.8 above avg 14.2
AdoptionLog-scaled stars · package downloads
11.3 / 20
2.1 above avg 9.2

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-10-09
Rank Moved
Rank dropped 13 spots (#1328 → #1341)
2026-09-23
Rank Moved
Rank dropped 373 spots (#935 → #1308)
2026-09-22
Rank Moved
Rank dropped 507 spots (#428 → #935)
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.
Compare with another agent Get email alerts for Supervision View Needs review Report missing data
95.4
Activity sub-score · out of 100
#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 →

Signals refreshed 2026-10-21 20:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-21

Activity & Reach

Stars
51.3k
Forks
4.8k
Last Push
2026-10-21
today
Commits (4 wk)
127
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
42
Rank Change
=
was #1358

Analysis

Activity Inputs

95.4 / 100
StarsRepository reach
28.3 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
17.1 / 20

Common questions about Supervision

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.
Are Supervision's commits signed?
98% of the last 100 commits to Supervision 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

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
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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 Supervision?

For maintainers

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

Signal history
Rank 22
2026-10-09
Rank Moved
Rank dropped 13 spots (#1328 → #1341)
2026-09-23
Rank Moved
Rank dropped 373 spots (#935 → #1308)
2026-09-22
Rank Moved
Rank dropped 507 spots (#428 → #935)
2026-09-21
Rank Moved
Rank rose 879 spots (#1307 → #428)
2026-09-05
Rank Moved
Rank dropped 15 spots (#1259 → #1274)
2026-09-04
Rank Moved
Rank dropped 16 spots (#1243 → #1259)
2026-09-03
Rank Moved
Rank dropped 11 spots (#1232 → #1243)
2026-09-02
Rank Moved
Rank dropped 33 spots (#1199 → #1232)
2026-09-01
Rank Moved
Rank dropped 35 spots (#1164 → #1199)
2026-08-31
Rank Moved
Rank dropped 32 spots (#1132 → #1164)
2026-08-30
Rank Moved
Rank dropped 44 spots (#1088 → #1132)
2026-08-29
Rank Moved
Rank dropped 40 spots (#1048 → #1088)
2026-08-28
Rank Moved
Rank dropped 31 spots (#1017 → #1048)
2026-08-27
Rank Moved
Rank dropped 28 spots (#989 → #1017)
2026-08-26
Rank Moved
Rank dropped 101 spots (#888 → #989)
2026-08-17
Rank Moved
Rank rose 17 spots (#912 → #895)
2026-08-16
Rank Moved
Rank dropped 29 spots (#883 → #912)
2026-08-13
Rank Moved
Rank dropped 11 spots (#869 → #880)
2026-08-12
Rank Moved
Rank rose 13 spots (#882 → #869)
2026-08-10
Rank Moved
Rank dropped 55 spots (#824 → #879)
2026-08-08
Rank Moved
Rank dropped 365 spots (#455 → #820)
2026-07-28
Rank Moved
Rank dropped 13 spots (#411 → #424)
GitHub → Website →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 26.8 Grade D
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.4 · Raw JSON