Case file No.094 · pypi · stdio

OpenHire · 哨兵

io.github.gzchenhao/openhire · v0.8.25

Jobs with the employer's real posting date, from employers' own ATS. HR family. Résumé stays local.

Package ↗GitHub ↗

Security score

96/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 0 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption6/10

1178 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

v0.8.15 → v0.8.25Oct 21, 2026

version changed version bump
```
"0.8.15" → "0.8.25"
```

description changed description text edit

"Job postings with real posting dates, read from employers' Greenhouse/Lever/Ashby/Beisen/Moka ATS." → "Jobs with the employer's real posting date, from employers' own ATS. HR family. Résumé stays local."

packages.0.version changed package version bump
```
"0.8.15" → "0.8.25"
```

First snapshot (v0.8.15)Oct 20, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is OpenHire · 哨兵 safe?

MCPWatch gives OpenHire · 哨兵 a heuristic security score of 96/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does OpenHire · 哨兵 have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package openhire. That is not proof of safety.

When was OpenHire · 哨兵 last updated?

The latest registry version is 0.8.25, published Oct 21, 2026. The last push to gzchenhao/openhire was on Oct 21, 2026. MCPWatch last checked it on Oct 21, 2026.

What license does OpenHire · 哨兵 use?

GitHub reports the license of gzchenhao/openhire as MIT.

Related servers

same publisher / similar score