updated 2026-10-10 20:07 UTC

Openmed

Repository Website

Local-first healthcare AI: clinical NER and HIPAA PII de-identification on hardware you control. 2,200+ medical models, 35 model-backed PII languages, and Python, MLX, Android and browser runtimes. Apache-2.0 SDK.

Agent Skills Python Listed Apache-2.0

Is Openmed safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.2 / 10
Provenance None
Signed commits 96%
Last push today
Advisories None known
Compare Openmed

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Openmed scores 74.8/100 (Grade B), ranked #25 of 371 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 6.2/10; 96% of recent commits are signed; no published advisory affects its latest release (openmed); last pushed 2026-10-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Openmed 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 Openmed and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Signed

    github.com/maziyarpanahi/openmed, Apache-2.0, last pushed 2026-10-10. 96% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.2/10 (scanned Sep 24, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review3
    • Branch Protection0
    • Signed Releases8
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies6
    All 18 Scorecard checks
    Binary-Artifacts 9
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 3
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 10
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 6
    SAST 0
    Security-Policy 10
    Signed-Releases 8
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Not linked

    • PyPI openmed Source link isn't a GitHub repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: openmed 3.0.0. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

  • 2026-09-01 OSSF Scorecard: 5.8/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Openmed’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 the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Openmed compares in Agent Skills

  1. #23 Claude Mem 76.4 +1.6
  2. #24 Code Review Graph 76.0 +1.2
  3. #25 Openmed 74.8 this agent
  4. #26 Memsearch 74.5 −0.3
  5. #27 Computer Use Linux 73.0 −1.8

Bars show each HVTrust score; the tick marks Openmed’s 74.8.

Where the 74.8 comes from

HVTrust dimensions vs the Agent Skills average

74.8 / 100 · 100.0% confidence

Openmed Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.6 / 25
4.8 above avg 7.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
13.8 / 17
1.8 above avg 12.0
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.9 above avg 14.1
AdoptionLog-scaled stars · package downloads
16.5 / 20
7.5 above avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.2/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.
Compare with another agent Get email alerts for Openmed View Agent Skills Report missing data
85.6
Activity sub-score · out of 100
#25
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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 refreshed 2026-10-10 20:07 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars
5.5k
Forks
704
Last Push
2026-10-10
today
Commits (4 wk)
678
Downloads (7d)
462,605
pypi
HN mentions (30d)
—
Open Issues
491
Rank Change
=
was #25

Analysis

Activity Inputs

85.6 / 100
StarsRepository reach
22.4 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
13.2 / 20

Common questions about Openmed

Openmed 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 Openmed publish package provenance?
No published build provenance is currently detected for Openmed. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Openmed have an OpenSSF Scorecard?
Openmed has an OpenSSF Scorecard score of 6.2/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 Openmed actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Openmed use?
Openmed ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Openmed's commits signed?
96% of the last 100 commits to Openmed 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
high confidence
Implemented
Openmed appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
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
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Openmed'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.

2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Openmed?

For maintainers

HVTrust scores Openmed 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 7Listed 2HVTrust 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1Surface 1
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Postgres
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 174 spots (#199 → #25)
2026-09-23
HVTrust Changed
HVTrust up 39.8pts (35.2 → 75.0)
2026-09-22
Newly Listed
First tracked at rank #199
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-01
Scorecard Added
OSSF Scorecard: 5.8/10
2026-09-01
Grade Changed
Trust grade D → B
2026-09-01
Rank Moved
Rank rose 174 spots (#188 → #14)
2026-09-01
HVTrust Changed
HVTrust up 32.3pts (41.5 → 73.8)
2026-08-31
Rank Moved
Rank dropped 17 spots (#171 → #188)
2026-08-30
Rank Moved
Rank dropped 30 spots (#141 → #171)
2026-08-29
Rank Moved
Rank dropped 35 spots (#106 → #141)
2026-08-28
Rank Moved
Rank dropped 21 spots (#85 → #106)
2026-08-27
Rank Moved
Rank dropped 21 spots (#64 → #85)
2026-08-26
Newly Listed
First tracked at rank #64
GitHub → Website → PyPI: openmed

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Skills

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